VPC-native GKE gives nodes and Pods routable VPC identities

The subnet primary range addresses nodes and internal load balancers. A secondary range supplies Pod IPs; Services use a separate or GKE-managed range depending on version and configuration.

Primary range

Node interfaces and some internal load-balancer addresses.

Pod secondary range

Alias IP blocks assigned per node, then consumed by Pods.

Service range

Virtual ClusterIP addresses translated to backend Pod IPs.

Control-plane path

Separately secured API endpoint, not part of normal Pod addressing.

Address planning is capacity planning: every future node needs both a node IP and a Pod block.

VPC-native GKE gives nodes and Pods routable VPC identities

Alias IPs is easiest to understand by separating the Kubernetes contract from the Google Cloud implementation. All new GKE clusters are VPC-native. Nodes use the subnet primary range and Pods use secondary ranges through alias IPs, so Pod addresses participate in VPC routing without an overlay. 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(ipAllocationPolicy.clusterIpv4CidrBlock,ipAllocationPolicy.servicesIpv4CidrBlock)'`. 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: The Service range behavior differs by cluster version; newer clusters can use the GKE-managed 34.118.224.0/20 range. The safe habit is to verify quotas, regional availability and feature support against current Google Cloud documentation before rollout. The next slide turns this into sizing arithmetic.