Flux CD
Hard
Troubleshooting
A ConfigMap applied by a Flux Kustomization holds a shell script using ${HOME}, and postBuild substitution blanks it out. What stops that?
Select your answer:
Show answer and explanation
Answer: Annotating it with kustomize.toolkit.fluxcd.io/substitute: disabled
Explanation
postBuild substitution replaces every ${var} in the built manifests, and an undefined variable without a default becomes an empty string. The substitute: disabled annotation skips the object. You can also write $HOME without braces, or $${HOME}, which comes out as ${HOME}.
More hard Flux CD questions
- A HelmRelease in flux-system sets targetNamespace: apps and no storageNamespace. Where does Helm keep the release's storage Secrets?
- How can an OCIRepository authenticate to Amazon ECR without a static registry password?
- You need to add a label to a Deployment that a third-party chart renders, and the chart has no value for it. What does a HelmRelease offer?
- What permissions does the deploy key created by 'flux bootstrap github' have by default?
- What does the annotation kustomize.toolkit.fluxcd.io/ssa: IfNotPresent do on an object in a Flux source?
- A change to an immutable field makes Flux's apply of a Job fail. Which annotation on the Job tells Flux to delete and recreate it?