How do you make Helm drop a key the chart's values.yaml sets, not just override it?

Most values work is overriding: the chart says one thing, you say another, yours wins. Occasionally you need something the override model does not obviously provide - for the key to stop existing. Helm has exactly one way to express that, and every intuitive alternative fails in a different way. ## The mechanism When Helm combines a lower-precedence map with a higher-precedence one, a key whose higher-precedence value is `null` is removed from the merged result rather than carried through as an empty value. So `billingCron: {nodeSelector: null}` in a `-f` file, or `--set billingCron.nodeSelector=null` on the command line, produces merged values in which `nodeSelector` is simply absent. A template that guards the field - emitting it only when the value is present and non-empty - then emits nothing at all, which is the outcome you wanted. ## Why the intuitive alternatives fail Consider a monitoring-stack chart whose `values.yaml` gives its subscription-billing cron a `nodeSelector` of `{disktype: ssd}`, and a new cluster with no such nodes: the CronJob is admitted, never schedules, and about seven minutes into the upgrade window someone notices no billing run has fired. Here is what each thing you might reach for actually does. | What you write in the override | What the merge does with it | Result | | --- | --- | --- | | `nodeSelector: {}` | An empty map contributes no keys to a deep merge | Nothing at all - the chart's `disktype: ssd` coalesces straight back in and the rendered CronJob is byte-identical | | `nodeSelector: ""` | Changes the value, but to an empty string | The API expects a map, so the upgrade fails on a validation error | | Delete the block from your override file | You are simply no longer overriding the key | The most misleading of the three - the chart default applies untouched | | `nodeSelector: null` | Removes the key from the merged values | The field is gone, which is what you wanted | Only `nodeSelector: null` deletes. ## What null does and does not reach The deletion is a property of the merge, so it works against any lower layer: a `null` in the last `-f` file removes a key an earlier `-f` file set, and a `--set key=null` removes one a file set, just as it removes a chart default. What it cannot do is change the template. If the chart writes the field unconditionally, an absent value renders as an empty field rather than as no field, and no combination of values will remove it; the chart itself has to guard that block, and if it does not, the fix is a chart change rather than a values change. Similarly, a chart that demands a value and fails the render when it is missing will now fail - which is arguably the chart telling you the key is not optional. ## Verification Because two of the three wrong answers produce a successful render, reading the rendered output is not optional. Render the chart with exactly the flags and files you intend to apply, find the object in question, and confirm the field is gone rather than empty. Then apply. On a release that is already live, compare the rendered candidate against the stored manifest for the current revision; a field disappearing is a visible line in that diff, and a field that stubbornly refuses to disappear is equally visible. ## `[]` versus null for lists The same distinction applies to sequences. `[]` gives an empty list, so the key exists and renders as an empty sequence; `null` removes the key entirely. Both look false to a simple truthiness check, so charts that only ever do a plain conditional will behave identically either way, and charts that check for the presence of the key will not. When you cannot tell which the chart does, prefer `null` - absent is the state that means "the chart author's default does not apply here", and empty is a value in its own right. ## Why this is worth knowing It is not a screening question, and a strong candidate can have a productive Helm career without meeting it. But it is the difference between a five-minute fix and an afternoon spent adding fields to a values file that changes nothing, and it is a small window onto how the merge actually works: the merge does not overwrite values, it constructs a new map, and `null` is the one instruction that tells it to leave a key out.