c1bc4615fe
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. |
||
|---|---|---|
| .. | ||
| manifests | ||
| azure-cloud-config.j2 | ||
| http-proxy.conf.j2 | ||
| kube-proxy-kubeconfig.yaml.j2 | ||
| kubelet-container.j2 | ||
| kubelet.docker.service.j2 | ||
| kubelet.host.service.j2 | ||
| kubelet.kubeadm.env.j2 | ||
| kubelet.rkt.service.j2 | ||
| kubelet.standard.env.j2 | ||
| nginx.conf.j2 | ||
| node-kubeconfig.yaml.j2 | ||
| openstack-cloud-config.j2 | ||
| vsphere-cloud-config.j2 | ||