←back to thread

213 points mmoogle | 5 comments | | HN request time: 0.833s | source
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 #
skissane ◴[] No.44610954[source]
I’ve never used Helm charts. I learned K8S in a shop in which kustomize is the standard and helm is a permitted exception to the standard, but I just never felt any reason to learn helm. Am I missing out?

Sometimes the limitations of kustomize annoy me, but we find ways to live with them

replies(7): >>44611081 #>>44611452 #>>44611555 #>>44611784 #>>44612267 #>>44612326 #>>44614078 #
letmeinhere ◴[] No.44611555[source]
Would you like to count the number of spaces that various items in your manifests are indented and then pass that as an argument to a structure-unaware text file templating engine? Would you like to discover your inevitable yaml file templating errors after submitting those manifests to the cluster? Then yes, you are really missing out!
replies(2): >>44612348 #>>44614093 #
1. thayne ◴[] No.44612348[source]
I really, really, wish we could move away from yaml for tools like this.
replies(2): >>44613816 #>>44618642 #
2. IshKebab ◴[] No.44613816[source]
If YAML is a foot-gun, templated YAML is a face-cannon.
replies(1): >>44614338 #
3. 9dev ◴[] No.44614338[source]
I never understood why people didn’t serialize from JSON if they run a transformation step on the YAML anyway. Read JSON, alter in your favorite language, dump YAML as the last step, deploy. Instant prevention of a lot of sadness.

Yet somehow, all we have is YAML templating?

replies(1): >>44615844 #
4. stackskipton ◴[] No.44615844{3}[source]
Kubectl will handle JSON without converting it to YAML. So if you are doing this, then just do kubectl apply -f deployment.json
5. shepherdjerred ◴[] No.44618642[source]
CDK8s works really well. I'm sad it hasn't really taken off.

https://cdk8s.io/