QuestionQ14

VerifiedDesigning and planning a Google Cloud Virtual Private Cloud (VPC) network

You are designing a Google Kubernetes Engine (GKE) cluster for a rapidly growing microservices application. The application will contain thousands of pods and hundreds of services. It requires internal pod-to-pod communication and internal service exposure. You want to follow Google’s recommended approach to ensure efficient IP address use in your existing Virtual Private Cloud (VPC) subnet while using Google Cloud’s native networking capabilities.

What should you do?

Explanation

VPC-native GKE uses the subnet’s primary IPv4 range for node addresses and secondary IP ranges for Pod addresses and, when using user-managed Service ranges, Service ClusterIP addresses. This provides native VPC routing for Pods and independently planned address capacity for the large Pod and Service populations.

Learn more

Community Discussion

No comments yet. Be the first to start the discussion!