Persistent Disk is the default block choice; Hyperdisk adds tunable performance

Both integrate through CSI and usually serve one writer. Persistent Disk balances familiarity and durability; Hyperdisk targets workloads that need independent IOPS or throughput control.

Choice	Use it for	Watch
Balanced Persistent Disk	Most enterprise applications and general stateful services	Zonal scope by default
Regional Persistent Disk	Higher availability across two zones in one region	Write latency and cost trade-off
Hyperdisk Balanced	Modern line-of-business and database workloads needing tunable performance	Machine and regional support
Hyperdisk Throughput / Extreme / ML	Throughput, IOPS or model-loading specialization	Exact mode and access support

Use WaitForFirstConsumer for topology-aware provisioning when the volume is zone-scoped.

GKE block storage is easiest to understand by separating the Kubernetes contract from the Google Cloud implementation. The Persistent Disk CSI driver is the primary GKE integration, and balanced Persistent Disk is the default dynamic storage type on modern clusters. Hyperdisk provides newer tunable performance profiles. The Kubernetes objects stay familiar, but GKE supplies controllers, infrastructure and safe defaults around them. This is why a team can move from an on-premises cluster without rewriting every workload, while still needing to redesign networking, identity and operational ownership for the cloud environment.

A useful inspection step is `kubectl get sc -o wide`. Read the output as evidence, not as a ritual: first confirm the desired object exists, then look at status conditions, events and the Google Cloud resource it represents. In production, capture the expected result in a runbook or automated check so an operator can distinguish slow reconciliation from a configuration error.

Production gotcha: A zonal disk provisioned before scheduling can strand a Pod in another zone; topology-aware binding prevents that mismatch. The safe habit is to verify quotas, regional availability and feature support against current Google Cloud documentation before rollout. Shared-file and object access need different services.