Google Professional Cloud Network Engineer Question 166
Select 3Google Cloud PlatformYou are tasked with designing an IP addressing plan for a Google Kubernetes Engine (GKE) cluster that will host workloads requiring extensive horizontal scaling. The workloads will also interact with on-premises systems over a VPN connection. Which considerations should you take into account when designing the IP addressing plan?
- A
Ensure that the cluster's Pod CIDR range does not overlap with on-premises networks.
- B
Use a small Pod CIDR range to minimize IP address consumption on the VPC network.
- C
Allocate a large enough Pod CIDR range to support future scaling of workloads.
- D
Configure separate IP ranges for Pods and Services to reduce IP address conflicts.
- E
Use non-RFC 1918 IP ranges for the Pod CIDR to avoid conflicts with private on-premises IPs.
Show answer and explanation
Correct answers: A, C, D
Explanation
When designing an IP addressing plan for GKE, it is crucial to avoid IP range overlaps with on-premises networks to ensure seamless connectivity, especially over a VPN. A sufficiently large Pod CIDR range should be planned to accommodate future scaling needs. Additionally, separating IP ranges for Pods and Services reduces the likelihood of IP conflicts, simplifying network management. Small Pod CIDR ranges or non-RFC 1918 IP ranges are not suitable choices for this scenario due to scaling and compatibility concerns.
- A. Correct.
Ensuring that the Pod CIDR range does not overlap with on-premises networks is critical to avoid routing conflicts, especially when the cluster interacts with on-prem systems over a VPN.
- B. Incorrect.
Using a small Pod CIDR range is not recommended for workloads requiring horizontal scaling, as it may lead to IP exhaustion as the cluster scales.
- C. Correct.
Allocating a large enough Pod CIDR range is necessary to ensure the cluster can scale horizontally without running out of IP addresses for Pods.
- D. Correct.
Configuring separate IP ranges for Pods and Services helps prevent IP conflicts and ensures clean network segmentation within the cluster.
- E. Incorrect.
Using non-RFC 1918 IP ranges is generally discouraged in GKE IP planning. RFC 1918 ranges are standard for private networks and well-supported for integration with other systems, including on-premises networks.