-
- Downloads
assert that number of pods on node does not exceed CIDR address range
The number of pods on a given node is determined by the --max-pods=k directive. When the address space is exhausted, no more pods can be scheduled even if from the --max-pods-perspective, the node still has capacity. The special case that a pod is scheduled and uses the node IP in the host network namespace is too "soft" to derive a guarantee. Comparing kubelet_max_pods with kube_network_node_prefix when given allows to assert that pod limits match the CIDR address space.
Showing
- roles/kubernetes/node/defaults/main.yml 4 additions, 0 deletionsroles/kubernetes/node/defaults/main.yml
- roles/kubernetes/node/templates/kubelet.kubeadm.env.j2 1 addition, 0 deletionsroles/kubernetes/node/templates/kubelet.kubeadm.env.j2
- roles/kubernetes/node/templates/kubelet.standard.env.j2 1 addition, 0 deletionsroles/kubernetes/node/templates/kubelet.standard.env.j2
- roles/kubernetes/preinstall/tasks/verify-settings.yml 14 additions, 0 deletionsroles/kubernetes/preinstall/tasks/verify-settings.yml
Please register or sign in to comment