A library StorageClass has allowVolumeExpansion enabled. How does an administrator expand a Bound PVC’s capacity?
Select an answer to reveal the explanation.
Short Explanation
With expansion allowed, you bump the claim’s requested size—like asking the landlord for a bigger closet without tearing up the lease and losing your stuff.
Full Explanation
With a library StorageClass that has allowVolumeExpansion enabled, an administrator expands a Bound PVC by increasing the PVC’s storage request upward; the provisioner expands the volume when expansion is supported. You bump the claim’s requested size like asking for a bigger closet without tearing up the lease and losing your stuff. The CSI driver then grows the backend and typically the filesystem.
Deleting the PVC and recreating it larger is disruptive and may lose data under Delete reclaim—pods do not keep old data automatically that way. Editing only the PersistentVolume capacity while ignoring the PVC request is not the supported expansion workflow. Patching StorageClass reclaimPolicy to Expand is invalid; reclaimPolicy is unrelated to expansion.
Exam caveat: allowVolumeExpansion must be true on the class, and the driver must support online/offline expansion as documented. Some expansions leave FileSystemResizePending until the Pod remounts.
Operational check: edit PVC requests.storage upward, watch PVC conditions and PV capacity, confirm filesystem size inside the library Pod, and document any required restart/remount. Keep civic change tickets precise: record object names, namespaces, and before/after observations so the next on-call engineer can replay the fix without guesswork.