Your company is planning a migration to Google Kubernetes Engine. Your application team informed you that they require a minimum of 60 Pods per node and a maximum of 100 Pods per node. Which Pod per…

The correct answer is A. /24. In GKE VPC-native clusters, the per-node pod CIDR size is automatically determined by the --max-pods-per-node setting. GKE allocates pod IP ranges per node as follows: 1–8 pods → /28, 9–16 → /27, 17–32 → /26, 33–64 → /25, 65–110 → /24. Since the requirement is a maximum of 100…

Submitted by weili_xi· Apr 18, 2026Designing, planning, and prototyping a Google Cloud network

Question

Your company is planning a migration to Google Kubernetes Engine. Your application team informed you that they require a minimum of 60 Pods per node and a maximum of 100 Pods per node. Which Pod per node CIDR range should you use?

Options

A/24
B/25
C/26
D/28

How the community answered

(64 responses)

A
75% (48)
B
14% (9)
C
3% (2)
D
8% (5)

Explanation

In GKE VPC-native clusters, the per-node pod CIDR size is automatically determined by the --max-pods-per-node setting. GKE allocates pod IP ranges per node as follows: 1–8 pods → /28, 9–16 → /27, 17–32 → /26, 33–64 → /25, 65–110 → /24. Since the requirement is a maximum of 100 pods per node (which falls in the 65–110 range), GKE requires a /24 CIDR block per node. A /24 provides 256 addresses, enough to accommodate up to 110 pods after reservations. A /25 (128 addresses) only supports up to 64 maximum pods per node, which cannot meet the 100-pod maximum. A /26 (64 addresses) only supports up to 32, and /28 (16 addresses) only supports up to 8 - both far too small.

Topics

#GKE networking#IP addressing#Subnetting#Pod CIDR

Community Discussion

No community discussion yet for this question.

Full PROFESSIONAL-CLOUD-NETWORK-ENGINEER Practice