Kubernetes - Advanced Deployment Patterns
A FluxCD Kustomization resource has 'prune: false' but you notice old resources are deleted. What might be wrong?
A FluxCD Kustomization resource has 'prune: false' but you notice old resources are deleted. What might be wrong?
medium📝 Troubleshoot Q7 of 15
Step-by-Step Solution
Solution:
Step 1: Understand prune behavior
Prune removes resources not in manifests. If prune is false but resources are deleted, another Kustomization with prune true might manage those resources.Step 2: Evaluate other options
FluxCD respects prune setting, invalid GitRepository causes sync failure but not pruning, and prune applies to Kustomizations as well as HelmReleases.Final Answer:
Another Kustomization with prune enabled manages same resources -> Option BQuick Check:
Conflicting prune settings cause unexpected deletes [OK]
Quick Trick: Check for overlapping Kustomizations with prune enabled [OK]
Common Mistakes:
- Assuming FluxCD ignores prune setting
- Not checking for multiple Kustomizations managing same resources
- Confusing prune behavior between resource types
Master "Advanced Deployment Patterns" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes