From 2cdf96e165eb1ec632d39725f0d1288fa79f9db9 Mon Sep 17 00:00:00 2001 From: John Gardiner Myers Date: Tue, 20 Apr 2021 17:22:46 -0700 Subject: [PATCH] Remove obsolete caution about cordoning As of Kubernetes 1.19, unschedulable nodes are no longer removed from load balancers --- content/en/docs/concepts/architecture/nodes.md | 7 ------- 1 file changed, 7 deletions(-) diff --git a/content/en/docs/concepts/architecture/nodes.md b/content/en/docs/concepts/architecture/nodes.md index 30dc0d4af9..c583098693 100644 --- a/content/en/docs/concepts/architecture/nodes.md +++ b/content/en/docs/concepts/architecture/nodes.md @@ -309,13 +309,6 @@ The node controller also adds {{< glossary_tooltip text="taints" term_id="taint" corresponding to node problems like node unreachable or not ready. This means that the scheduler won't place Pods onto unhealthy nodes. - -{{< caution >}} -`kubectl cordon` marks a node as 'unschedulable', which has the side effect of the service -controller removing the node from any LoadBalancer node target lists it was previously -eligible for, effectively removing incoming load balancer traffic from the cordoned node(s). -{{< /caution >}} - ### Node capacity Node objects track information about the Node's resource capacity: for example, the amount