Templating & Values

Files under crds/ are plain YAML rather than templates, so the rendering engine never touches them and helm template leaves them out of its output by default. Pass --include-crds to have them emitted alongside the rendered manifests.

YAML checks that a document's layout is consistent, not that keys landed where you meant. A block emitted a couple of columns too shallow can still parse — it simply attaches to an ancestor map instead of the key above it, so the object is well-formed and the setting silently never takes effect.

Helm keeps DNS resolution switched off during rendering, so sprig's getHostByName returns an empty string unless the rendering command is given --enable-dns. Even then the lookup runs on the machine running helm, not inside the cluster.

Named templates are global to the release, not scoped per chart: the parent and every subchart load into one namespace. Two definitions of the same name do not conflict loudly — whichever loads last wins, and both charts silently render it.

Set the key to null in your override - key: null in a -f file, or --set key=null. Helm's merge drops a key whose override value is null, so it never reaches .Values. An empty string, {} or [] does not remove it.