A Pod is configured to use a Persistent Volume Claim, but it remains in a Pending state and never starts. What is the most probable reason?

medium📝 Troubleshoot Q6 of 15

Kubernetes - Persistent Storage

AThe Persistent Volume is using a different storage class than the PVC requests.

BThe Pod spec is missing the volumeMounts section.

CThe Persistent Volume Claim has not been bound to any Persistent Volume.

DThe Pod's container image is not accessible.

Step-by-Step Solution

Solution:

Step 1: Check PVC status
Verify if the Persistent Volume Claim is bound to a Persistent Volume using kubectl get pvc.
Step 2: Understand binding
If the PVC is not bound, the Pod will remain Pending because it cannot mount the volume.
Step 3: Confirm storage class compatibility
While storage class mismatch can cause binding failure, the primary cause is unbound PVC.
Final Answer:
The Persistent Volume Claim has not been bound to any Persistent Volume. -> Option C
Quick Check:
Check PVC binding status with kubectl get pvc [OK]

Quick Trick: Pod stays Pending if PVC is unbound [OK]

Common Mistakes:

Master "Persistent Storage" in Kubernetes

9 interactive learning modes - each teaches the same concept differently

Want More Practice?

15+ quiz questions · All difficulty levels · Free

More Kubernetes Quizzes