Google Professional Cloud Network Engineer Question 168
Select 3Google Cloud PlatformYou are designing an IP addressing plan for a Google Kubernetes Engine (GKE) cluster that will host multiple applications across namespaces. The cluster will scale to handle thousands of pods, and you must ensure there are no IP address conflicts with existing networks in your organization. Which of the following considerations should you account for when designing the IP addressing plan?
- A
Ensure that the Pod IP range does not overlap with any existing VPC subnets or on-premises networks.
- B
Use a /32 CIDR range for the Pod IP range to maximize the number of available IPs for your cluster.
- C
Enable VPC-native (alias IP) for the cluster to allow better IP address management.
- D
Account for the maximum number of Pods per node and nodes in the cluster when determining the Pod IP range size.
- E
Use overlapping IP ranges for services and Pods since Kubernetes handles internal routing.
Show answer and explanation
Correct answers: A, C, D
Explanation
When designing an IP addressing plan for a GKE cluster, you must ensure there are no IP conflicts with existing networks by setting a unique Pod IP range. Enabling VPC-native (alias IP) mode is a best practice for efficient IP management, and the size of the Pod IP range must account for the cluster's scalability in terms of Pods per node and total nodes. Using a /32 CIDR range or overlapping IPs is not feasible and can lead to routing problems.
- A. Correct.
Correct. Ensuring that the Pod IP range does not overlap with other networks is critical to avoid routing conflicts, especially in hybrid or multi-cloud environments.
- B. Incorrect.
Incorrect. A /32 CIDR range allows only one address, which is insufficient for a cluster that needs to scale to thousands of Pods.
- C. Correct.
Correct. Enabling VPC-native (alias IP) mode helps with efficient IP allocation and routing by integrating with the Google Cloud VPC network.
- D. Correct.
Correct. The number of Pods per node and the total number of nodes in the cluster directly influence the size of the IP range required for Pods.
- E. Incorrect.
Incorrect. Overlapping IP ranges can cause routing issues and are not recommended, even though Kubernetes handles some internal routing.