Q: What is the difference between a PersistentVolume (PV) and a PersistentVolumeClaim (PVC)?
PV (PersistentVolume) — the actual storage resource. Could be an AWS EBS volume, NFS share, local disk. Created by a cluster admin or dynamically provisioned.
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: "Kubernetes is a declarative desired state system; understanding the reconciliation loop is how you diagnose this quickly. 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."
Initial Diagnostics & Root Cause Analysis
Think of PV as the actual parking spot and PVC as the parking ticket that reserves it.
- PV (PersistentVolume) — the actual storage resource. Could be an AWS EBS volume, NFS share, local disk. Created by a cluster admin or dynamically provisioned.
- PVC (PersistentVolumeClaim) — a request for storage by a pod. The pod says "I need 10GB of ReadWriteOnce storage" — the PVC finds a matching PV and binds to it.
Remediation & Permanent Safeguards
- PV (PersistentVolume) — the actual storage resource. Could be an AWS EBS volume, NFS share, local...
- PVC (PersistentVolumeClaim) — a request for storage by a pod. The pod says "I need 10GB of ReadWr...
Senior hiring managers and bar raisers evaluate how you prioritize during outages. Avoid these common anti-patterns:
- Over-granting cluster-admin permissions to pod ServiceAccounts instead of scoping namespace Roles when configuring difference PersistentVolume (PV) Over-granting cluster-wide permissions violates least-privilege principles and allows compromised pods to escalate privileges across namespaces.
-
Referencing mutable latest container tags across production Kubernetes Deployment specs when configuring difference PersistentVolume (PV)
Deployments referencing
:latestrisk inconsistent versions across replica pods and break deterministic rollback capabilities. - Omitting pod readiness probes, causing traffic to hit uninitialized application containers when configuring difference PersistentVolume (PV) Readiness probes gate traffic delivery; missing probes cause Kubernetes to route user requests to pods before dependencies or caches are loaded.
- Executing diagnostic triage without analyzing chronological cluster events and describe outputs when configuring difference PersistentVolume (PV) Cluster events provide sequential timestamps of scheduler decisions, probe failures, and image pull timeouts essential for rapid root-cause isolation.