Getting tired of Helm – any better way to handle deployments in Kubernetes?
21–24 of 24 posts
Re: Getting tired of Helm – any better way to handle deployments in Kubernetes?
#22IMHO at scale (both in terms of complexity and org level) having something consistent helps more than trying to fight the de-facto standard. Since most upstream projects are mainly distributed as Helm charts, going with anything else will require more effort eventually.
Re: Getting tired of Helm – any better way to handle deployments in Kubernetes?
#23ArgoCD for relatively simple stuff. For complex stuff I write Python or Go programs to build manifests, then shell out to kubectl apply. An old example - deploying a multi-instance modded Arma 3 server on k3s: https://github.com/dharmab/homelab-k3s/tree/main/lab
Why just simple?
T.b.h. if I were to write a manifest generator, I would still probably commit the thing into a repo and let argo do the rest. Maybe even fiddled around to make the generator into a config-management-plugin ... but that feels like over-doing it.
Re: Getting tired of Helm – any better way to handle deployments in Kubernetes?
#24Recently I have been writing more stings in jsonnet. If I were with more haskell-friendly team, might even try dhall. In general, I feel like writing the yaml in something else than yaml is the way to go, and as long as you get imports and way to do templating that is not just string interpolation, you are good.