richard/kubespray - kubespray - Gitea: RS Source Repository

k8s-sig-cluster-lifecycle aws kubespray high-availability ansible kubernetes-cluster gce kubernetes bare-metal

History

Christopher J. Ruwe c1bc4615fe 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.		7 years ago
..
defaults	assert that number of pods on node does not exceed CIDR address range	7 years ago
handlers	Drop non systemd OS types support	8 years ago
meta	Refactor downloads to use download role directly (#1824)	7 years ago
tasks	sysctl file should be in defaults so that it can be overriden (#2475)	7 years ago
templates	assert that number of pods on node does not exceed CIDR address range	7 years ago