Back to all scenarios
Scenario #347
Storage
Kubernetes v1.25, dynamic provisioning

VolumeBindingBlocked Condition Causes Pod Scheduling Delay

Scheduler skipped over pods with pending PVCs due to VolumeBindingBlocked status, even though volumes were eventually created.

Find this helpful?
What Happened

PVC triggered provisioning, but until PV was available, pod scheduling was deferred.

Diagnosis Steps
  • 1Pod condition: PodScheduled: False, reason VolumeBindingBlocked.
  • 2StorageClass had delayed provisioning.
  • 3PVC was Pending for ~60s.
Root Cause

Volume provisioning time exceeded scheduling delay threshold.

Fix/Workaround
• Increased controller timeout thresholds.
• Optimized provisioning backend latency.
Lessons Learned

Storage latency can delay workloads unexpectedly.

How to Avoid
  • 1Monitor PVC creation latency in Prometheus.
  • 2Use pre-created PVCs for latency-sensitive apps.
Previous ScenarioNext Scenario