Back to all scenarios
Scenario #394
Storage
GKE Autopilot, dynamic PVC provisioning

GKE Autopilot PVCs Stuck Due to Resource Class Conflict

PVCs remained in Pending state due to missing resource class binding.

Find this helpful?
What Happened

GKE Autopilot required both PVC and pod to define compatible resourceClassName.

Diagnosis Steps
  • 1Events: No matching ResourceClass.
  • 2Pod log: PVC resource class mismatch.
Root Cause

Autopilot restrictions on dynamic provisioning.

Fix/Workaround
• Updated PVCs and workload definitions to specify supported resource classes.
Lessons Learned

GKE Autopilot enforces stricter policies on storage.

How to Avoid
  • 1Follow GKE Autopilot documentation carefully.
  • 2Avoid implicit defaults in manifests.
Previous ScenarioNext Scenario