Google Professional Cloud Network Engineer Question 334
Select 2Google Cloud PlatformYou are managing a GKE cluster in a VPC-native mode with alias IPs enabled. The cluster has reached its maximum Pod IP range due to the large number of Pods deployed. You need to configure and deploy additional Pod ranges while ensuring minimal disruption to the cluster's operation. What steps should you take?
- A
Use the gcloud container clusters update command to add a new Pod range to the cluster.
- B
Allocate a new secondary IP range in the VPC and associate it with the cluster.
- C
Recreate the cluster with an updated Pod range configuration to support additional Pods.
- D
Update the existing secondary IP range to expand its size.
- E
Deploy the additional Pod range to a new node pool within the cluster.
Show answer and explanation
Correct answers: B, E
Explanation
In a VPC-native GKE cluster, adding additional Pod ranges involves allocating a new secondary IP range in the VPC and associating it with the cluster. To utilize this new range, you must create a new node pool that uses the additional Pod range for assigning IPs to Pods. This approach ensures scalability without requiring cluster recreation or downtime.
- A. Incorrect.
Incorrect: The gcloud container clusters update command does not support adding new Pod ranges directly. This command is used for updates like enabling or disabling features, not for IP range modifications.
- B. Correct.
Correct: A new secondary IP range must be allocated in the VPC to provide additional IP addresses for Pods. This is a required step when expanding Pod ranges in a VPC-native GKE cluster.
- C. Incorrect.
Incorrect: Recreating the cluster is not necessary. GKE allows adding additional Pod ranges without recreating the cluster, which would cause downtime.
- D. Incorrect.
Incorrect: Updating an existing secondary IP range for size is not supported. GKE uses distinct secondary ranges for Pod IPs, and resizing an existing range is not a valid approach.
- E. Correct.
Correct: Deploying an additional Pod range to a new node pool allows the cluster to utilize the new IP range for Pods without impacting existing workloads.