Helm in production: hard-won lessons and gotchas

What started the discussion

This r/kubernetes thread focused on Helm in production: hard-won lessons and gotchas. The original post pointed readers to blog.sneakybugs.com, and the comments quickly turned into a practical discussion about the tradeoffs, surprises, and production realities behind the topic.

What stood out in the comments

Discussion point 1

Hi everyone! Hope you find this post useful. I think even experienced Helm users can learn something from it. The best tip is to use values schema files with yaml-language-server for better development experience. It's a huge productivity boost and even helps LLMs write values better.

Discussion point 2

What if I told you could use just regular Go and have all the types from the k8s.io/api project?

Discussion point 3

Oci registry is great. Bit odd with fluxcd though where gitrepo and oci registry need different secrets on GitHub. But that's githubs fault really. There's not a very natural progression from yaml to kustomize to helm, I'm not sure where you go after helm either.

Discussion point 4

That's what we've been doing. Anything k8s related and we just go golang for the native bindings.

Discussion point 5

Awesome post, care to elaborate on the CRD installation? How would you describe the process of first time installation of a chart that needs CRDs?

Thread snapshot

• Original subreddit: r/kubernetes
• Original author: u/LKummer
• Reddit score: 117
• Comment count: 19
• Original thread: https://blog.sneakybugs.com/helm-production-lessons/