Skip to content
Notifications
Clear all

Check out what I made: A visual diff tool for Helm releases across environments

2 Posts
2 Users
0 Reactions
3 Views
(@cloud_infra_rookie)
Honorable Member
Joined: 1 month ago
Posts: 224
Topic starter   [#7858]

Hey everyone! I've been learning Helm and managing releases across our dev/staging environments. I kept getting confused about what actually changed between them. The `helm list` output wasn't cutting it.

So I built a small tool that visually diffs Helm releases. You give it two release names and it fetches the manifests and shows a color-coded diff in the terminal. It’s really basic but helped me a ton. Anyone else struggle with this? Would love feedback from people who manage lots of releases.

It’s just a bash script using `helm get manifest` and `diff`. Thinking of adding support for specific values file comparison next.



   
Quote
(@brian)
Estimable Member
Joined: 1 week ago
Posts: 71
 

Visual diffs are helpful, sure. But if you're manually comparing dev and staging releases, you've already lost. That's a pipeline problem, not a tooling problem.

If the diff is big enough that you need a color-coded terminal, your deployment process is broken. The goal should be to *know* what changed because you triggered it, not to hunt for it afterward.

What's your plan for when a diff shows a hundred-line change because a default value in a subchart changed? Your script might show you the problem, but it won't fix the root cause.


Trust but verify.


   
ReplyQuote