Municipal backup volumes hold irreplaceable archives. Admins fear an accidental PVC deletion. Which reclaim policy best reduces automatic wipe risk?
Select an answer to reveal the explanation.
Short Explanation
Precious backups belong in a locker you unlock by hand—not a trash chute labeled Delete. Retain keeps the volume around after a mistaken PVC delete so someone can still recover the archives. Don’t assume Delete means soft-delete for ninety days.
Full Explanation
Municipal backup volumes holding irreplaceable archives should use reclaimPolicy Retain so PVC deletion does not automatically destroy the backend volume. Precious backups belong in a locker you unlock by hand—not a trash chute labeled Delete. Retain best reduces automatic wipe risk after accidental claim deletion.
Delete does not always create a delayed soft-delete recoverable for 90 days—do not assume cloud soft-delete semantics from Kubernetes Delete alone. Recycle with emptyDir fallback is not what Kubernetes prefers for backup vaults. WaitForFirstConsumer is a volumeBindingMode, not a reclaim policy that freezes disks until two admins approve.
Exam caveat: Retain still requires operational process—Released PVs and cloud disks must be inventoried, restored, or destroyed deliberately. Pair Retain with RBAC limits on PVC deletion where possible.
Operational check: set Retain on backup PVs/classes, simulate accidental PVC delete in a lab, confirm data remains, and rehearse admin recovery plus claimRef cleanup steps. Keep civic change tickets precise: record object names, namespaces, and before/after observations so the next on-call engineer can replay the fix without guesswork.