Kubernetes - Persistent Storage
In a multi-zone Kubernetes cluster, why can a StorageClass with
volumeBindingMode: Immediate cause pod scheduling failures?In a multi-zone Kubernetes cluster, why can a StorageClass with volumeBindingMode: Immediate cause pod scheduling failures?
hard📝 Conceptual Q10 of 15
Step-by-Step Solution
Solution:
Step 1: Understand Immediate binding
Immediate provisioning creates volumes before pod scheduling.Step 2: Consider multi-zone constraints
Volume may be provisioned in a zone different from where pod is scheduled, causing scheduling failure.Step 3: Eliminate other options
Options B, C, and D do not explain scheduling failures related to volume binding mode.Final Answer:
Volumes are provisioned before pod scheduling, possibly in a different zone than the pod -> Option AQuick Check:
Immediate binding can cause cross-zone volume mismatch [OK]
Quick Trick: Immediate binding provisions volumes before pod scheduling [OK]
Common Mistakes:
- Confusing Immediate with WaitForFirstConsumer binding mode
- Assuming reclaimPolicy affects scheduling
- Thinking provisioning happens after pod scheduling
Master "Persistent Storage" in Kubernetes
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Kubernetes Quizzes