You are running multiple VPC-native Google Kubernetes Engine clusters in the same subnet. The IPs available for the nodes are exhausted, and you want to ensure that the clusters can grow in nodes when

The correct answer is D. Expand the CIDR range of the relevant subnet for the cluster.. Every subnet must have a primary IP address range. You can expand the primary IP address range at any time, even when Google Cloud resources use the subnet; however, you cannot shrink or change a subnet's primary IP address scheme after the subnet has been created. The first two

Submitted by javi_es· Mar 30, 2026Planning and configuring a cloud solution

Question

You are running multiple VPC-native Google Kubernetes Engine clusters in the same subnet. The IPs available for the nodes are exhausted, and you want to ensure that the clusters can grow in nodes when needed. What should you do?

Options

ACreate a new subnet in the same region as the subnet being used.
BAdd an alias IP range to the subnet used by the GKE clusters.
CCreate a new VPC, and set up VPC peering with the existing VPC.
DExpand the CIDR range of the relevant subnet for the cluster.

How the community answered

(32 responses)

A
3% (1)
B
9% (3)
C
16% (5)
D
72% (23)

Explanation

Every subnet must have a primary IP address range. You can expand the primary IP address range at any time, even when Google Cloud resources use the subnet; however, you cannot shrink or change a subnet's primary IP address scheme after the subnet has been created. The first two and last two IP addresses of a primary IP address range are reserved by Google Cloud. https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips

Topics

#GKE#VPC subnets#CIDR expansion#IP address management

Community Discussion

No community discussion yet for this question.

Full ASSOCIATE-CLOUD-ENGINEER Practice