Google operates the control plane; Shopwave operates the service

The same Kubernetes object crosses two operating domains. Managed means fewer infrastructure duties, not fewer application duties.

Layer	GKE Autopilot	GKE Standard	RKE2 on-prem
API server, etcd, controllers	Google	Google	Shopwave
Node creation, repair, OS	Google	Shopwave with GKE automation	Shopwave
CNI, CSI, load-balancer integration	Google defaults	Configured with GKE features	Shopwave selects and runs
Workloads, RBAC, data, SLOs	Shopwave	Shopwave	Shopwave

The provider can own a component while you still own how your application depends on it.

Shared responsibility is easiest to understand by separating the Kubernetes contract from the Google Cloud implementation. GKE's control plane is Google-operated in both modes. Autopilot additionally manages node infrastructure and applies constraints that protect that operating model. 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 --format='yaml(autopilot,location)'`. 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: Teams often assume managed control plane means managed workloads; it does not cover bad readiness probes, unsafe RBAC or missing backups. The safe habit is to verify quotas, regional availability and feature support against current Google Cloud documentation before rollout. Next, topology shows why regional is the production default.