volume binding mode
A StorageClass setting that decides whether a volume is created as soon as a claim exists or only once a pod that uses it is scheduled.
In more detail
WaitForFirstConsumer delays creation until the scheduler has picked a node, so the disk is made in a zone where the pod can run. Until then the claim is Pending on purpose. Immediate creates the volume straight away, which can strand it in the wrong zone.
Related terms
- StorageClass — A cluster-wide policy that tells Kubernetes how to create new volumes on demand: which driver, which settings, and what happens on delete.
- topology domain — A group of nodes that tend to fail together, such as one zone or one machine, identified by a shared node label.
- PersistentVolumeClaim — A namespaced request for storage of a given size and access mode, which Kubernetes binds to a matching PersistentVolume.
Taught in
- Persistent And Ephemeral Volumes — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Design And Build: Timed Drill And Checkpoint — Certified Kubernetes Application Developer (CKAD) Exam Prep
- Bookings That Survive The Pod: Volumes And Claims — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- Forty Four Of Sixty: The Full Mock, And How To Read It — Kubernetes and Cloud Native Associate (KCNA) Exam Prep
- StorageClasses, CSI And Dynamic Provisioning — Kubernetes: Production-Grade Container Orchestration
- Troubleshooting: Pending Claims And Failed Mounts — Kubernetes: Production-Grade Container Orchestration