Question

You are provisioning a new VPC-native GKE cluster in a subnet named 'prod-subnet' that currently has only a primary IP range of 10.0.0.0/24. The platform team requires that Pods and Services each use dedicated, non-overlapping alias IP ranges so that Pod IPs are individually routable within the VPC. What must you configure on the subnet before or during cluster creation to satisfy this requirement?

Accepted Answer

Add two secondary IP ranges to 'prod-subnet' and reference them as the Pod and Service ranges when creating the VPC-native cluster.

Answer

Enlarge the primary range of 'prod-subnet' to a /16 so that Pods and Services can allocate addresses from the same range.

Answer

Enable a routes-based cluster and let GKE create static routes for each node's Pod CIDR block automatically.

Answer

Create a separate subnet in a peered VPC and assign the Pod and Service ranges from that subnet using VPC Network Peering.