Compare two Helm values files leaf by leaf, or merge them with Helm's own coalescing rules — arrays replace wholesale and an explicit null deletes the key.
Waiting for two values files
Helm merges maps and replaces arrays. Both are shown.
Override values
Paste both files
Leaf by leaf, with arrays compared whole because that is how Helm treats them.
The merge follows Helm’s own coalescing rules, including the two that catch people: an array in the override replaces the base array outright rather than merging into it, and an explicit null deletes the key rather than setting it to null. Both are reported as notes, because the merged YAML alone does not show what was discarded. Credential-shaped values are masked on both sides — a changed password still reads as changed, and neither value is looked at.
Helm Values Comparison runs entirely on your device — credential-shaped values are masked rather than read, and no Helm command is run.
You’re on the Free plan. Compare plans
The merge implements Helm's coalescing rules exactly, including the two that surprise people every time. Maps merge recursively, so a key the override does not mention survives. Arrays do not: an override's list replaces the base's outright.
That second rule is the one that costs an afternoon. Override one element of a list of environment variables and every other element is gone — no error, no warning, and the release comes up missing configuration that nobody removed.
The third rule is stranger still. An explicit `null` in an override deletes the key rather than setting it to null. Helm documents this and almost nobody discovers it before it bites. Every one of the three is reported as a note beside the merged output, because the merged YAML on its own does not show you what was lost.
Arrays are compared as single leaves for the same reason. Reporting "element 2 changed" would describe a merge Helm is not going to perform — it is going to replace the whole list, and the comparison says so rather than implying otherwise.
Credentials are masked on both sides. A changed password still reads as changed; neither value is looked at.
Because Helm replaces arrays rather than merging them. An override that supplies one element supplies the whole list, and everything only in the base is gone. This reports each replaced list with both lengths so you can see what was lost.
It deletes the key. Not sets it to null — removes it, so a template checking for its presence sees nothing. That is documented Helm behaviour and it surprises nearly everyone the first time. The merge reports every key a null removed.
No. It performs the same coalescing Helm does on the values themselves, which is pure data merging, and then stops. Nothing is rendered, nothing is installed and no cluster is contacted.