Back to all scenarios
Scenario #382
Storage
Kubernetes v1.24, GKE with dynamic provisioning

Unexpected Volume Type Defaults to HDD Instead of SSD

Volumes defaulted to HDD even though workloads needed SSD.

Find this helpful?
What Happened

StorageClass used default pd-standard instead of pd-ssd.

Diagnosis Steps
  • 1IOPS metrics showed high latency.
  • 2Checked StorageClass: wrong type.
Root Cause

Implicit default used in dynamic provisioning.

Fix/Workaround
• Updated manifests to explicitly reference pd-ssd.
Lessons Learned

Defaults may not match workload expectations.

How to Avoid
  • 1Always define storage class with performance explicitly.
  • 2Audit default class across environments.
Previous ScenarioNext Scenario