Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add note for LB behaviour for cordoned nodes. #18784

Merged
merged 2 commits into from
Feb 5, 2020
Merged

Add note for LB behaviour for cordoned nodes. #18784

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
8216d35
Add note for LB behaviour for cordoned nodes.
MMeent Jan 20, 2020
e8d1753
Update with feedback
MMeent Feb 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions content/en/docs/concepts/architecture/nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -275,6 +275,12 @@ and do not respect the unschedulable attribute on a node. This assumes that daem
the machine even if it is being drained of applications while it prepares for a reboot.
{{< /note >}}

{{< 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

The capacity of the node (number of cpus and amount of memory) is part of the node object.
Expand Down