⚡ ~/naveed Interview Prep
⚡ Portfolio Home 👤 About Naveed Bio & Credentials 📫 Contact Naveed Get In Touch ✍️ Engineering Blog Deep Dives 🎯 Interview Hub 1,000+ Scenarios ☸️ Kubernetes Mastery Hub 24 Modules 🎮 DevOps Arcade & Quizzes Subnet Blitz ⚡ 🗺️ DevOps Roadmaps PDFs & Guides 🤖 Morpheus Analysis AI Quant ↗ 🛠️ Developer Tools Utilities 🧪 Labs & Experiments 📄 Interactive CV & Certs 🔗 All Links & Socials ⚡ Join The Dispatch (Weekly SRE Newsletter) →
← Back to All Kubernetes Interview Questions Scenario 42 of 207 in Kubernetes
Senior DevOps / SRE [L2] Kubernetes Storage Production Scenario [L2]
🎯 Target Role / Context: Kubernetes Scenario #29 (L2) · Storage

Q: A PVC is stuck in `Pending` state. What do you check?

1. No matching PV — check if a PV exists with matching storageClassName, accessMode, and enough capacity: kubectl get pv.

#Kubernetes #Storage #L2 #Container Orchestration #K8s #Terraform State
🎙️ Candidate Opening & Architectural Context
""In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix.""
Advertisement
⚡ Recommended Practice Lab

Want to master this scenario in a live sandbox? KodeKloud's CKA & CKAD Hands-On Certification Track covers this exact problem with hands-on terminal drills.

🛠️ Production Runbook & Step-by-Step Resolution

Direct Answer: "In our production Kubernetes clusters running microservices on EKS/AKS, this was a classic operational challenge. When addressing this question, I walk the interviewer through our production incident runbook: isolating the blast radius, checking diagnostic logs and metrics, and applying a safe fix."

1️⃣

Initial Diagnostics & Root Cause Analysis

  • No matching PV — check if a PV exists with matching storageClassName, accessMode, and enough capacity: kubectl get pv.
  • StorageClass doesn't exist — kubectl get storageclass. If the PVC references a storage class that doesn't exist, it stays Pending.
  • Dynamic provisioner not working — if using dynamic provisioning (like AWS EBS CSI driver), check if the CSI driver pods are running: kubectl get pods -n kube-system | grep csi.
2️⃣

Remediation & Permanent Safeguards

Execute the resolution runbook and verify workload health:

  • Volume binding mode — if the StorageClass has volumeBindingMode: WaitForFirstConsumer, the PVC stays Pending until a pod that uses it is scheduled. That's normal behavior.
💡 The Senior SRE Gold Nugget (Key Architectural Takeaway)
"Pro-Tip: No matching PV — check if a PV exists with matching storageClassName, accessMode, and enough capacity: kubectl get pv.."
⚡ 60-Second Elevator Pitch Talking Points
  • No matching PV — check if a PV exists with matching storageClassName, accessMode, and enough capa...
  • StorageClass doesn't exist — kubectl get storageclass. If the PVC references a storage class that...
  • Dynamic provisioner not working — if using dynamic provisioning (like AWS EBS CSI driver), check ...
⛔ Critical Candidate Mistakes to Avoid in This Scenario

Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:

  1. Restarting a crashing container without examining preceding termination logs via kubectl logs --previous when configuring stuck Pending state Restarting the pod flushes ephemeral container runtime state, destroying vital panic stack traces and fatal initialization logs.
  2. Misdiagnosing an application boot crash as a failure of aggressive liveness probes when configuring stuck Pending state Liveness probes with short timeouts or high failure thresholds kill slow-starting applications repeatedly, causing false CrashLoopBackOff loops.
  3. Neglecting node taints, tolerations, and resource quotas when diagnosing pods stuck in Pending when configuring stuck Pending state Pods remain Pending when scheduler predicates fail; kubectl describe pod reveals whether CPU/memory exhaustion or taints prevent placement.
  4. Invoking kubectl delete pod --force --grace-period=0 indiscriminately on unready pods when configuring stuck Pending state Forced deletion bypasses kubelet cleanup and can cause multi-attach errors on PersistentVolumes (PVs) or split-brain on stateful workloads.
Advertisement
📥 FREE DOWNLOAD · 101-PAGE COMPANION HANDBOOK
Studying for Kubernetes & SRE Technical Rounds?
Download the complete 100-question PDF field guide covering all 11 core modules with offline diagnostic runbooks.
📥 Download PDF (Free) Read Online Guide →
Want more Kubernetes scenarios?
Explore our complete collection of scenario-based Kubernetes interview runbooks.
Browse All Kubernetes Questions →