Helm vs Kustomize
The cluster centers on strong criticism of Helm for overcomplicating Kubernetes YAML manifests and strong advocacy for Kustomize as a simpler, more elegant alternative, with mentions of other tools like ArgoCD and isopod.
Activity Over Time
Top Contributors
Keywords
Sample Comments
Helm is horrible, it makes simple elegant yaml files complex and makes the changes you actually need harder. Kustomize is the correct way to do things.
If you don't like Helm, there is Kustomize.
Helm is horrible. Please use Kustomize. Life will get better, it did for me. I also use Sops (with goabout/kustomize-sopssecretgenerator) and ArgoCD for a very slick well integrated system. The CRDs in ArgoCD are so well done that it feels like native K8s CD.
Shameless plug - I’ve worked on a dsl tool [0] at my previous gig that addresses these because I was similarly unimpressed with helm[0] - https://github.com/cruise-automation/isopod
what about Helm for Kubernetes?
Helm is the necessary evil for Kubernetes chose YAML
Helm is so bad it raises my blood pressure just hearing the name. Helm tries to apply the old way of doing things (like as you said Puppet) and makes it worse than ever. K8s yaml config is simple and elegant, don't try hiding it under templates. Kustomize is the proper way of working with K8s yaml. Helm fights against it.
is there anything working with helm in the similar way ?
Can you explain the advantage of this tool vs. helm?
Thank you for writing this article. I'm a DevOps Engineer and spend most of my time with Terraform and Kubernetes. K8s yaml is simple clean config, and Helm turns it into an obfuscated monkey pile. If I need to use a Helm chart, I use helm template which outputs the yaml to a file. Typically I do this in a Makefile. Then I use Kustomize to modify it for my application. Kustomize has lowered my stress level from when I used Helm substantially. Helm might be fine if you don't know [and d