Back to all scenarios
Scenario #395
Storage
Kubernetes v1.24, GKE regional cluster

Cross-Zone Volume Scheduling Failed in Regional Cluster

Pods failed to schedule because volumes were provisioned in a different zone than the node.

Find this helpful?
What Happened

Regional cluster scheduling pods to one zone while PVCs were created in another.

Diagnosis Steps
  • 1Events: FailedScheduling: volume not attachable.
Root Cause

Storage class used zonal disks instead of regional.

Fix/Workaround
• Updated storage class to use regional persistent disks.
Lessons Learned

Volume zone affinity must match cluster layout.

How to Avoid
  • 1Use regional disks in regional clusters.
  • 2Always define zone spreading policy explicitly.
Previous ScenarioNext Scenario