You set a PersistentVolume reclaim policy to Delete but after deleting the PersistentVolumeClaim, the volume still exists. What is the most likely cause?

medium📝 Troubleshoot Q14 of 15

Kubernetes - Persistent Storage

You set a PersistentVolume reclaim policy to Delete but after deleting the PersistentVolumeClaim, the volume still exists. What is the most likely cause?

AThe reclaim policy was misspelled in the YAML and ignored.

BThe volume was manually retained by an admin.

CThe PersistentVolumeClaim was not actually deleted.

DThe storage class does not support automatic deletion.

Step-by-Step Solution

Solution:

Step 1: Understand Delete reclaim policy
Delete policy should remove the volume automatically after claim deletion.
Step 2: Check storage class support
If the storage class does not support dynamic deletion, volume remains despite policy.
Final Answer:
The storage class does not support automatic deletion. -> Option D
Quick Check:
Storage class support needed for Delete policy [OK]

Quick Trick: Delete needs storage class support to remove volume [OK]

Common Mistakes:

Assuming reclaim policy misspelling always causes failure
Ignoring storage class role in deletion
Not verifying claim deletion status

Master "Persistent Storage" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Learn Why Deep Visual Try Challenge Project Recall Time

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions

More Kubernetes Quizzes

You set a PersistentVolume reclaim policy to Delete but after deleting the PersistentVolumeClaim, the volume still exists. What is the most likely cause?

Step 1: Understand Delete reclaim policy

Step 2: Check storage class support

Final Answer:

Quick Check:

Want More Practice?