Getting tired of Helm – any better way to handle deployments in Kubernetes?

10 DeborahEmeni_ 9 5/6/2025, 3:12:58 PM
I’ve been deep in Helm templates lately and it’s starting to feel like YAML hell. It was fine when we had a few services, but now it’s just hard to manage. Anyone found a workflow that avoids Helm altogether? Or made Helm manageable at scale?

Comments (9)

Vespasian · 2m ago
My recommendation is fluxcd for a great gitops based workflow (incorporates soap for secrets)
b11484 · 27m ago
I've been working on improving a tool called kr8+, which uses jsonnet to combine cluster config and apply it to components: https://github.com/ice-bergtech/kr8
haiku2077 · 47m ago
ArgoCD 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

Nerudite · 37m ago
dvektor · 1h ago
Yeah the whole 'git repo = helm chart' just does not feel great at all. As we all know, the only thing worse is not using helm and having to deal with writing all those service, pv, pvc, ingress yaml files individually :)
natbennett · 1h ago
I prefer ytt for templating and kapp for deployments.

https://github.com/carvel-dev/carvel

LarsLarson · 2h ago
We are using kustomize to create the yaml and argocd for deployment. All via ci and git-ops.

works really well

GauntletWizard · 1h ago
I'm a huge fan of Kustomize. I'm ambivalent towards argocd, but Kustomize is as close to a DWIM tooling as it's possible to get for Kubernetes.
johnjungles · 1h ago
ArgoCD