Kubernetes / Storage, Configuration & Data Protection
Plan PVC expansion as a storage and filesystem operation
A larger requested claim can still need driver support, backend capacity or filesystem completion. Inspect expansion capability and claim status.
Environment and inputs: Kubernetes · kubectl with supported client/server versions and delegated RBAC. Examples use namespace app unless noted. Check context, namespace, APIs and provider support first.
Start with this check
Confirm the environment and replace sample objects, namespaces, images, paths and hosts with approved targets. Share only relevant, sanitized output. Follow the workload owner’s process for changes.
kubectl get storageclass fast -o jsonpath='{.allowVolumeExpansion}'
kubectl -n app describe pvc app-dataRead the result
Class permission is only one prerequisite. Claim conditions and the CSI provider's support determine the actual workflow and whether restart is required.
Resolve and verify
Verify backend headroom and the driver's documented expansion path, then perform the approved growth change and confirm filesystem capacity in the application.
Before changing production
Do not edit the PV capacity to fake expansion or assume shrinking a claim is a supported reversal.