After setting a PersistentVolume's reclaim policy to Delete, you notice the volume remains after deleting its PersistentVolumeClaim. What could be the reason?
medium📝 Troubleshoot Q6 of 15
Kubernetes - Persistent Storage
After setting a PersistentVolume's reclaim policy to Delete, you notice the volume remains after deleting its PersistentVolumeClaim. What could be the reason?
AThe volume's storage class does not support deletion on reclaim.
BThe reclaim policy <code>Delete</code> only applies to dynamically provisioned volumes.
CThe PersistentVolume is still bound to a PersistentVolumeClaim and not yet released.
DThe PersistentVolumeClaim was deleted before the PersistentVolume was created.
Step-by-Step Solution
Solution:
Step 1: Check PersistentVolume Binding Status
Verify if the PersistentVolume is still bound to a PersistentVolumeClaim. If it is, the volume will not be deleted yet.
Step 2: Understand Reclaim Policy Behavior
The Delete reclaim policy deletes the volume only after the claim is fully released (unbound).
Final Answer:
The PersistentVolume is still bound to a PersistentVolumeClaim and not yet released. -> Option C
Quick Check:
Volume must be released before deletion [OK]
Quick Trick:Volume must be released before deletion happens [OK]
Common Mistakes:
Assuming Delete policy deletes volume immediately after claim deletion
Confusing storage class capabilities with reclaim policy
