Google Professional Cloud Network Engineer Question 330
Select 2Google Cloud PlatformA team is deploying a GKE cluster and wants to ensure there are sufficient IP ranges for both Pods and Services within the VPC network. After initial deployment, they realize that the existing Pod IP range is nearing exhaustion due to scaling. Which steps should you take to add an additional Pod range to the cluster?
- A
Create a new secondary IP range in the VPC and update the cluster to use it using the gcloud CLI.
- B
Use the gcloud container clusters update command to add a new Pod range directly to the cluster without updating the VPC.
- C
Ensure the cluster is using VPC-native routing to allow additional Pod ranges to be added.
- D
Recreate the entire GKE cluster with a larger Pod IP range as additional Pod ranges cannot be added to an existing cluster.
- E
Update the kube-proxy configuration to reflect the new Pod range after adding it to the cluster.
Show answer and explanation
Correct answers: A, C
Explanation
To add an additional Pod range to an existing GKE cluster, the cluster must be using VPC-native routing, and a new secondary IP range must be created within the same VPC. Once the new range is created, it can be associated with the cluster using the gcloud CLI. This process allows the cluster to scale without IP exhaustion, avoiding the need to recreate the cluster or perform manual configurations.
- A. Correct.
Correct: To add an additional Pod range, you must first create a new secondary IP range in the VPC and then update the cluster to use it. This ensures there is sufficient IP space for the Pods.
- B. Incorrect.
Incorrect: You cannot directly add a new Pod range to the cluster without first creating a secondary IP range in the VPC. The VPC must be updated to accommodate the new range.
- C. Correct.
Correct: VPC-native routing is required for GKE clusters to handle multiple Pod IP ranges. This ensures that the new secondary ranges can be properly used by the cluster.
- D. Incorrect.
Incorrect: It is not necessary to recreate the cluster. GKE supports adding additional Pod ranges to existing clusters as long as the cluster is configured for VPC-native routing.
- E. Incorrect.
Incorrect: Updating kube-proxy configurations is not required when adding new Pod ranges. This process is managed automatically by GKE when the new range is added.