An open-data team uses cloud disks that must land in the same zone…

Question

An open-data team uses cloud disks that must land in the same zone as the scheduled Pod. Which StorageClass volumeBindingMode delays binding until a consumer Pod is scheduled?

Accepted Answer

WaitForFirstConsumer, so the provisioner can honor the Pod’s topology when creating the volume — Immediate binding is like assigning a locker before you know which gym floor the athlete uses—easy to pick the wrong building. WaitForFirstConsumer holds off until the Pod has a seating chart (node/zone), then provisions the disk where it can actually attach. That’s the topology-aware cloud-disk pattern.

Answer

Immediate, which always waits for the Pod’s nodeName before calling CSI

Answer

Recreate, a binding mode that rebuilds PVs on every kubelet restart

Answer

Manual, which requires kubectl bind before any Pod may mount storage

An open-data team uses cloud disks that must land in the same zone as the scheduled Pod. Which StorageClass volumeBindingMode delays binding until a consumer Pod is scheduled?

Short Explanation

Full Explanation