存储架构

Helm vs Kapitan vs Kustomize

微信扫一扫,分享到朋友圈

Helm vs Kapitan vs Kustomize
0

TLDR;

  • Kapitan (and presumably Ksonnet) is the more flexible and customizable (json and jsonnet)
  • Kustomize if the more straightforward, just released so we’ll need a bit more documentation on built-in functions (yaml only)
  • Helm combines a package approach and releases management that is powerful, with the caveats of Tiller for the release management part (additional source of truth)

During the implementation of https://www.weyv.com
environments in Kubernetes, we went through various stages. From plain yaml files, to Helm charts releases and finally helm charts but with helm template output. Now with the announcement of Kustomize, I take the opportunity to re-evaluate our choice of tool vs our requirements with 3 contenders: Helm, Kapitan, Kustomize. I left out Ksonnet ( https://github.com/ksonnet/ksonnet
) it seems very close to Kapitan.

Helm: https://github.com/kubernetes/helm

Kapitan: https://github.com/deepmind/kapitan

Kustomize: https://github.com/kubernetes-sigs/kustomize

Read more at Medium

阅读原文...


微信扫一扫,分享到朋友圈

Helm vs Kapitan vs Kustomize
0

Linux

JB的Python之旅-爬虫篇-图形验证码(2)-- 收费OCR了解下

上一篇

宁德时代IPO:创始人身价超200亿、市值近800亿,背后37家VC/PE支持

下一篇

评论已经被关闭。

插入图片

热门分类

往期推荐

Helm vs Kapitan vs Kustomize

长按储存图像,分享给朋友