
Google Associate Cloud Engineer
Get started today
Ultimate access to all questions.
As a cloud engineer in an app development startup using Kubernetes on GKE, you're faced with a challenge. Several applications are deployed on separate VPC-native Google Kubernetes Engine clusters within the same subnet, which has no more available IPs. What solution ensures these clusters can expand their nodes when necessary?
As a cloud engineer in an app development startup using Kubernetes on GKE, you're faced with a challenge. Several applications are deployed on separate VPC-native Google Kubernetes Engine clusters within the same subnet, which has no more available IPs. What solution ensures these clusters can expand their nodes when necessary?
Explanation:
Expanding the CIDR range of the relevant subnet is the correct solution because it allows for more IP addresses to become available within the subnet, enabling the clusters to grow by adding more nodes as needed. This approach directly addresses the issue of IP address exhaustion without the need for creating new subnets or VPCs, which would not inherently solve the IP availability problem in the existing subnet. The first two and last two IP addresses of a primary IP address range are reserved by Google Cloud, but expanding the range ensures scalability. Other options like adding an alias IP range or creating new subnets or VPCs do not effectively expand the available IP space for the existing clusters' growth.