Back to all scenarios
Scenario #310
Storage
Kubernetes v1.25, GKE
StorageClass Misconfiguration Blocks Dynamic Provisioning
New PVCs failed to bind due to a broken default StorageClass with incorrect parameters.
Find this helpful?
What Happened
A recent update modified the default StorageClass to use a non-existent disk type. All PVCs created with default settings failed provisioning.
Diagnosis Steps
- 1PVCs in Pending state.
- 2Checked events: “failed to provision volume with StorageClass”.
- 3Described StorageClass: invalid parameter type: ssd2.
Root Cause
Mistyped disk type in StorageClass definition.
Fix/Workaround
• Corrected StorageClass parameters.
• Manually bound PVCs with valid classes.Lessons Learned
Default StorageClass affects many workloads.
How to Avoid
- 1Validate StorageClass on cluster upgrades.
- 2Use automated tests for provisioning paths.