Back to all scenarios
Scenario #343
Storage
Kubernetes v1.24, CSI VolumeExpansion enabled
Failed Volume Resize Blocks Rollout
Deployment rollout got stuck because one of the pods couldn’t start due to a failed volume expansion.
Find this helpful?
What Happened
Admin updated PVC to request more storage. Resize failed due to volume driver limitation. New pods remained in Pending.
Diagnosis Steps
- 1PVC events: resize not supported for current volume type.
- 2Pod events: volume resize pending.
Root Cause
Underlying CSI driver didn't support in-use resize.
Fix/Workaround
• Deleted affected pods, allowed volume to unmount.
• Resize succeeded offline.Lessons Learned
Not all CSI drivers handle online expansion.
How to Avoid
- 1Check CSI driver support for in-use expansion.
- 2Add pre-checks before resizing PVCs.