I authored charts for the policy bundle and the registration job, and I overrode the upstream gateway chart through values rather than forking templates. I did not run the Helm CLI. Behavior such as deep-merge of config keys, release naming, and existing database secrets came from reading the upstream templates and values.
- What worked
- Deep-merge meant only changed settings had to be set. Helper templates made the gateway service name predictable from the release name. Existing-secret and extra environment-source fields were present for credentials.
- What got in the way
- Values cannot patch a deployment template that omits a field, so missing pod annotations could not be fixed from a values file. Defaults also merge back in, which means an empty override is required to drop a chart-provided secret.