Regional clusters keep the API available through a zonal failure

Autopilot clusters are always regional. Standard can be regional or zonal, and Google recommends regional clusters for production availability.

Regional control plane

Replicas run across zones in one region; Autopilot always uses this shape.

Multi-zone workloads

Replicas and topology spread are still required; a regional control plane does not duplicate your Pods automatically.

Zonal Standard

Lower-complexity development shape with one control-plane zone and a lower control-plane SLA.

Irreversible topology

A cluster cannot be converted between zonal and regional after creation.

Regional protects the Kubernetes API; replicas, disruption budgets and data replication protect the application.

Regional clusters keep the API available through a zonal failure

Regional topology is easiest to understand by separating the Kubernetes contract from the Google Cloud implementation. A regional GKE control plane has replicas across zones. Autopilot is always regional, while Standard gives you the location choice and node-location controls. 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 `gcloud container clusters describe shopwave-prod --region europe-west1 --format='value(locations)'`. 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: Do not confuse a regional cluster with a multi-region application; a regional outage still requires another cluster or recovery plan. The safe habit is to verify quotas, regional availability and feature support against current Google Cloud documentation before rollout. The operating mode decision comes next.