whentimeslows/website
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Remove obsolete caution about cordoning

Browse Source 
As of Kubernetes 1.19, unschedulable nodes are no longer removed from load balancers
This commit is contained in:
John Gardiner Myers
2021-04-20 17:22:46 -07:00
parent baff0490a3
commit 2cdf96e165
1 changed files with 0 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/en/docs/concepts/architecture/nodes.md
-7
View File
@@ -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 corresponding to node problems like node unreachable or not ready. This means
that the scheduler won't place Pods onto unhealthy nodes. 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 capacity
Node objects track information about the Node's resource capacity: for example, the amount Node objects track information about the Node's resource capacity: for example, the amount