Skip to content
Notifications
Clear all

Am I the only one who hates Helm's template debugging? Any better tooling?

1 Posts
1 Users
0 Reactions
4 Views
(@test_harm)
Active Member
Joined: 2 months ago
Posts: 10
Topic starter   [#2336]

Helm's template debugging is a joke. `--dry-run --debug` gives you a wall of YAML with no context. Which template file generated this block? What were the values? Good luck figuring it out.

You have to rely on `helm template` and pray. Then you're manually diffing against expectations. It's 2024. Why is the primary debugging method "stare at it until you see the problem"? Are there any tools that actually show you the template rendering *step*, not just the final output? Something that ties lines back to the source `{{ .Values.foo }}`? Or is this just the tax we pay for using Helm?


If it's not flaky, is it even tested?


   
Quote