Flux CD
Hard
Concepts
You want to delete a Flux Kustomization but keep the workloads it created running. Which field do you set first?
Select your answer:
Show answer and explanation
Answer: spec.deletionPolicy: Orphan
Explanation
Orphan leaves the managed objects in place when the Kustomization is deleted. The default, MirrorPrune, deletes them when prune is true. Delete always deletes them, and WaitForTermination also waits for them to be gone. If a parent Kustomization still has this one in Git, it is recreated on the next reconciliation.
More hard Flux CD questions
- In a CI job, 'flux diff kustomization' exits with status 1. What does that mean?
- A chart ships CRDs in its crds/ directory, and the HelmRelease has no crds settings. What happens to those CRDs on upgrade?
- How many Helm release revisions does helm-controller keep for a HelmRelease that doesn't set maxHistory?
- A HelmRelease sets upgrade.remediation.retries: 3 and nothing else under remediation. What happens between failed upgrade attempts?
- How does notification-controller build the webhook URL path for a Receiver?
- A HelmRelease's chartRef points at an OCIRepository holding a Helm chart. How should the OCIRepository's layerSelector handle the chart layer?