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?
To determine the Pod per node CIDR range, you need to calculate how many IP addresses are required for each node, and then choose the smallest CIDR range that can accommodate that number. A CIDR range of /n means that there are 2^(32-n) IP addresses available in that range. For example, a /24 range has 2^(32-24) = 256 IP addresses.
According to the question, the application team requires a minimum of 60 Pods per node and a maximum of 100 Pods per node. Therefore, you need to choose a CIDR range that can provide at least 100 IP addresses per node, but not more than necessary. A /25 range has 2^(32-25) = 128 IP addresses, which is enough for 100 Pods per node. A /26 range has 2^(32-26) = 64 IP addresses, which is not enough for 60 Pods per node. A /24 range has 256 IP addresses, which is more than needed and wastes IP address space. A /28 range has 2^(32-28) = 16 IP addresses, which is far too small for any node.
1:Configure maximum Pods per node | Google Kubernetes Engine (GKE) | Google Cloud
Vanda
11 months agoJaime
11 months agoAleshia
10 months agoLavonna
10 months agoLatanya
10 months agoFlo
10 months agoNieves
11 months agoBuddy
11 months agoKristeen
10 months agoCordelia
10 months agoAngelo
10 months agoNina
11 months agoErnie
11 months agoBritt
11 months agoBeth
11 months agoRenea
11 months agoSharen
12 months agoMike
12 months agoArlie
12 months ago