When using Helm with both a values file and --set, the set will always have precedence over the values.yaml. This allows specifying the normal config inside a yaml file and specifying a secret outside that yaml via --set. When using flux, this normally works too (using inline values to specify most of the config and a reference with targetPath to get a secret), but if you want to overwrite a secret key inside an array the inline values will always overwrite the whole array and the referenced secret key will not appear at all. By making sure that when you specify a targetPath it has precedence over inline values it will be merged properly. Signed-off-by: Ströger Florian <florian@florianstroeger.com> |
||
|---|---|---|
| .. | ||
| README.md | ||
| helmreleases.md | ||
README.md
helm.toolkit.fluxcd.io/v2beta2
This is the v2beta2 API specification for declaratively managing Helm chart releases with Kubernetes manifests.