←back to thread

210 points mmoogle | 6 comments | | HN request time: 0s | source | bottom
Show context
dpkirchner ◴[] No.44610377[source]
Maybe this will finally break me of my habit of using helm charts, period.
replies(4): >>44610605 #>>44610877 #>>44610954 #>>44612370 #
cheshire_cat ◴[] No.44610605[source]
Why do you want to stop using helm charts? Genuine question, as I'm new to Kubernetes and helm.
replies(4): >>44610615 #>>44610658 #>>44610858 #>>44611287 #
chuckadams ◴[] No.44610615[source]
Write a few Helm charts and you'll understand why people want to stop using it. `nindent` will become a curse word in your vocabulary. It's a fine tool at the user level, but the DX is an atrocity.
replies(2): >>44610629 #>>44610659 #
1. cbzbc ◴[] No.44610659[source]
What are you planning on moving to ?
replies(2): >>44611445 #>>44611736 #
2. chuckadams ◴[] No.44611445[source]
Probably kustomize, as my needs are simple. If I care to get fancy, I’m pondering giving Yoke a try.
replies(2): >>44611556 #>>44615448 #
3. theteapot ◴[] No.44611556[source]
What's wrong with `kubectl apply -f xxx.yaml`?
replies(1): >>44611973 #
4. dpkirchner ◴[] No.44611736[source]
I'm using either opentofu(terraform) or plain yaml. I'm not a huge fan of HCL but at least it is structured and easily manipulated without worrying about whitespace.
5. physicles ◴[] No.44611973{3}[source]
We use kustomize because we have four environments that run basically the same stuff (dev with k3s, test, and two cloud regions). If we didn’t use kustomize, we’d be forced to reinvent it to avoid duplicating so much yaml.
6. davidham ◴[] No.44615448[source]
I used kustomize to build an ArgoCD install at a previous company, and I was impressed at how powerful it was. Our setup was pretty involved, and kustomize was able to handle all the per-environment differences easily, and the code was easy to work with.