DCA · Question #140
A persistentVolumeClaim (PVC) is created with the specification storageClass: "", and size requirements that cannot be satisfied by any existing persistentVolume. Is this an action Kubernetes takes…
The correct answer is A. Yes. When a PVC's requirements, including its StorageClass (or lack thereof), cannot be matched by any existing PersistentVolume, Kubernetes keeps the PVC in an unbound state.
Question
A persistentVolumeClaim (PVC) is created with the specification storageClass: "", and size requirements that cannot be satisfied by any existing persistentVolume. Is this an action Kubernetes takes in this situation? Solution: The PVC remains unbound until a persistentVolume that matches all requirements of the PVC becomes available.
Options
- AYes
- BNo
How the community answered
(39 responses)- A95% (37)
- B5% (2)
Why each option
When a PVC's requirements, including its StorageClass (or lack thereof), cannot be matched by any existing PersistentVolume, Kubernetes keeps the PVC in an unbound state.
If a `PersistentVolumeClaim` (PVC) specifies `storageClass: ""` (requesting a PV with no specific StorageClass or the cluster's default one) and no existing `PersistentVolume` (PV) meets all of its criteria (size, access modes), Kubernetes will leave the PVC in a 'Pending' state. It will continuously attempt to bind the PVC as soon as a suitable PV becomes available that satisfies all specified requirements.
Kubernetes' design for unmet PVC requirements dictates that the PVC will remain in a pending state, actively waiting for a matching PV to provision or become available, rather than failing the claim immediately.
Concept tested: Kubernetes PersistentVolumeClaim binding
Source: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#persistentvolumeclaims
Topics
Community Discussion
No community discussion yet for this question.