Bird
0
0

You created a PersistentVolumeClaim but it stays in Pending state. What is a likely cause?

medium📝 Troubleshoot Q6 of 15
Kubernetes - Persistent Storage
You created a PersistentVolumeClaim but it stays in Pending state. What is a likely cause?
AThe PVC YAML is missing metadata.name
BThe pod using the PVC is not running
CThe Kubernetes API server is down
DNo PersistentVolume matches the requested size or access mode
Step-by-Step Solution
Solution:

  1. Step 1: Analyze PVC Pending state reasons

    Pending usually means no suitable PersistentVolume matches the PVC's requested size or access mode.

  2. Step 2: Exclude unrelated causes

    Pod status or missing metadata.name would cause different errors; API server down affects all commands, not just PVC.

  3. Final Answer:

    No PersistentVolume matches the requested size or access mode -> Option D

  4. Quick Check:

    PVC Pending = No matching PV available [OK]
Quick Trick: PVC Pending means no matching PV found yet [OK]
Common Mistakes:
  • Blaming pod status for PVC Pending
  • Ignoring PV size and access mode requirements
  • Assuming API server issues cause PVC Pending

Want More Practice?

15+ quiz questions · All difficulty levels · Free

Free Signup - Practice All Questions
More Kubernetes Quizzes
ConfigMaps - Immutable ConfigMaps - Quiz 15hard Ingress - Why Ingress manages external access - Quiz 9hard Ingress - Why Ingress manages external access - Quiz 12easy Networking - Container Network Interface (CNI) - Quiz 3easy Persistent Storage - StatefulSets for stateful applications - Quiz 11easy Resource Management - CPU requests and limits - Quiz 1easy Scheduling - DaemonSets for per-node workloads - Quiz 8hard Scheduling - DaemonSets for per-node workloads - Quiz 15hard Secrets - Secret types (Opaque, docker-registry, TLS) - Quiz 12easy Secrets - Base64 encoding in Secrets - Quiz 10hard