DevOps · Flashcard
A Flux-managed Deployment is deleted with kubectl. What happens?
- AIt comes back at the next reconcile — Git is the desired state
- BIt stays deleted — until someone re-runs flux bootstrap
- CIt stays deleted — Flux opens a PR proposing the change
- DIt comes back — but only with drift detection switched on
Why this is the answer
Flux runs controllers inside the cluster that continuously compare the cluster with the manifests in Git and re-apply what differs, so an out-of-band deletion is undone on the next interval — that convergence is the whole point of GitOps. Nothing needs re-bootstrapping, Flux never writes changes back as a proposal, and reconciliation is on by default rather than an extra feature.
Official docs