Bird
0
0

You created a StatefulSet but notice pods are stuck in Pending state. Which of these is the most likely cause?

medium📝 Troubleshoot Q14 of 15
Kubernetes - Persistent Storage
You created a StatefulSet but notice pods are stuck in Pending state. Which of these is the most likely cause?
AThe volumeClaimTemplates request more storage than available in the cluster
BThe StatefulSet spec is missing the container image field
CThe StatefulSet replicas count is set to zero
DThe pod labels do not match the StatefulSet selector
Step-by-Step Solution
Solution:

  1. Step 1: Analyze Pending pod reason

    Pods stuck in Pending often mean resources like storage or compute are unavailable.

  2. Step 2: Check volumeClaimTemplates impact

    If requested storage exceeds cluster capacity, PersistentVolumeClaims remain unbound, blocking pod start.

  3. Final Answer:

    VolumeClaimTemplates request more storage than cluster can provide -> Option A

  4. Quick Check:

    Pending pods often mean storage or resource shortage [OK]
Quick Trick: Pending pods often mean storage or resource shortage [OK]
Common Mistakes:
  • Assuming missing image causes Pending (it causes CrashLoopBackOff)
  • Thinking zero replicas create Pending pods (no pods created)
  • Ignoring label-selector mismatch effects

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