Q: You deleted a PVC but the data is gone. How could you have protected it?
By setting the Reclaim Policy on the PV or StorageClass:
Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.
🛠️ Production Runbook & Step-by-Step Resolution
Direct Answer: "When troubleshooting Kubernetes, I always follow a structured layered model: Pod status -> Events -> Logs -> Network. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."
Initial Diagnostics & Root Cause Analysis
By setting the Reclaim Policy on the PV or StorageClass:
Delete(default for dynamic provisioning) — deletes the underlying volume when PVC is deleted. Data is gone.Retain— PV stays after PVC deletion. Data is preserved. Admin must manually reclaim.Recycle— deprecated, performed basic cleanup.
Remediation & Permanent Safeguards
Also: use VolumeSnapshot to take backups before deleting. Or enable backup tools like Velero that snapshot PVC data. Lesson: Always check the StorageClass reclaim policy in production. Default Delete on cloud providers will wipe your data.
- Delete (default for dynamic provisioning) — deletes the underlying volume when PVC is deleted. Da...
- Retain — PV stays after PVC deletion. Data is preserved. Admin must manually reclaim.
- Recycle — deprecated, performed basic cleanup.
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring deleted data gone Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring deleted data gone
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring deleted data gone Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring deleted data gone Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.