Professional Cloud Network EngineerDemo

Question

Your organization must address a shortage of private IP addresses. You need to create new GKE clusters and restrict the Pods secondary range size to no larger than /22.

What should you do?

A Create a secondary range for pods with a size of /22. Create a secondary range for services manually. Reference these ranges during the GKE cluster creation.
B Specify a new /22 IP range for pods during the GKE cluster creation. Let GKE automatically create the secondary range in your existing primary subnet range.
C Deploy GKE Autopilot instead of GKE Standard.
D Configure the pods per node value to the minimum to automatically use smaller subnet ranges for pods during the GKE cluster creation.

Explanation

VPC-native GKE clusters allocate Pod and Service addresses from separate subnet secondary ranges. Creating a /22 secondary range for Pods and a separate secondary range for Services, then specifying those ranges when the cluster is created, directly controls the Pod CIDR size. A secondary range must not overlap the subnet’s primary IP range.

Learn more

Professional Cloud Network EngineerDemo

AstroTutor

Notes

Readiness

QuestionQ217

Community Discussion