←back to thread

210 points mmoogle | 2 comments | | HN request time: 0s | 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 #
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 #
NewJazz ◴[] No.44610658[source]
Consuming one that is well written isn't too much pain, IME. But writing or modifying one can be really annoying. Aiui the values.yaml has no type schema, just vibes. The whole thing is powered off using text templating with yaml (a whitespace sensitive language), which is error prone and often hard to read. That's basically the main issues in a nutshell, it may not sound like much, but helm doesn't exactly do a whole lot and it does that limited set of stuff poorly.
replies(1): >>44610785 #
1. remram ◴[] No.44610785[source]
I share your dislike of Helm, but FYI there are schemas for values, see for example https://github.com/bitnami/charts/blob/main/bitnami/postgres... and docs https://helm.sh/docs/topics/charts/#schema-files
replies(1): >>44611394 #
2. NewJazz ◴[] No.44611394[source]
Ah, I must have met some lazy charts then. Thanks for the correction. Still, it seems like that schema would end up a little inconvenient to integrate into your editor for writing the templates...