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. |
||
|---|---|---|
| .. | ||
| dhclient-hooks-undo.yml | ||
| dhclient-hooks.yml | ||
| etchosts.yml | ||
| growpart-azure-centos-7.yml | ||
| main.yml | ||
| pre_upgrade.yml | ||
| resolvconf.yml | ||
| set_facts.yml | ||
| set_resolv_facts.yml | ||
| verify-settings.yml | ||