Bird
0
0

A pod in a StatefulSet is stuck in Pending state and cannot attach its PersistentVolumeClaim. What is the most probable cause?

medium📝 Troubleshoot Q7 of 15
Kubernetes - Persistent Storage
A pod in a StatefulSet is stuck in Pending state and cannot attach its PersistentVolumeClaim. What is the most probable cause?
AThe StatefulSet has no replicas defined
BThe pod's container image is missing
CNo available PersistentVolumes matching the PVC's storage class and size
DThe pod's readiness probe is failing
Step-by-Step Solution
Solution:

  1. Step 1: Analyze Pending state with PVC

    If a pod cannot attach its PVC, it usually means no suitable PersistentVolume is available.

  2. Step 2: Exclude other options

    Missing container image or readiness probe failures do not cause Pending state related to volume attachment.

  3. Final Answer:

    No available PersistentVolumes matching the PVC's storage class and size -> Option C

  4. Quick Check:

    Pending + PVC attach failure = no matching PV [OK]
Quick Trick: Pending + PVC attach failure = no matching PV [OK]
Common Mistakes:
  • Assuming container image issues cause Pending state
  • Confusing readiness probe failures with volume attachment
  • Ignoring storage class and size requirements

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Using ConfigMaps as mounted volumes - Quiz 5medium Health Checks and Probes - Liveness probe concept - Quiz 7medium Health Checks and Probes - Liveness probe concept - Quiz 1easy Ingress - Ingress resource definition - Quiz 13medium Ingress - Path-based routing - Quiz 3easy Persistent Storage - PersistentVolume (PV) definition - Quiz 15hard Scheduling - Node selectors for simple scheduling - Quiz 5medium Scheduling - Resource requests and limits - Quiz 3easy Secrets - Creating Secrets - Quiz 15hard Secrets - Secrets are not encrypted by default - Quiz 10hard