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 documentation for TaintNodesByCondition #5352

Merged
merged 7 commits into from
Sep 12, 2017
Merged

Add documentation for TaintNodesByCondition #5352

Changes from 1 commit
Commits
Show all changes
7 commits
Select commit Hold shift + click to select a range
268411f
Add documentation for TaintNodesByCondition
Sep 8, 2017
7e150d6
Update nodes.md
steveperry-53 Sep 11, 2017
9e97bea
Update taint-and-toleration.md
steveperry-53 Sep 11, 2017
eeafda3
Update daemonset.md
steveperry-53 Sep 11, 2017
670944e
Update nodes.md
steveperry-53 Sep 12, 2017
1a28e20
Update taint-and-toleration.md
steveperry-53 Sep 12, 2017
ac03dd9
Update daemonset.md
steveperry-53 Sep 12, 2017
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
Prev Previous commit
Next Next commit
Update nodes.md
  • Loading branch information
@steveperry-53
steveperry-53 authored Sep 12, 2017
commit 670944ed1de777283c82be0030594f8ba3d6568e
4 changes: 2 additions & 2 deletions docs/concepts/architecture/nodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,10 +72,10 @@ the "Terminating" or "Unknown" states. In cases where Kubernetes cannot deduce f
permanently left a cluster, the cluster administrator may need to delete the node object by hand. Deleting the node object from
Kubernetes causes all the Pod objects running on it to be deleted from the apiserver, freeing up their names.

Version 1.8 introduces an aplpha feature that automatically creates
Version 1.8 introduces an alpha feature that automatically creates
[taints](/docs/concepts/configuration/taint-and-toleration) that represent conditions.
To enable this behavior, pass an additional feature gate flag `--feature-gates=...,TaintNodesByCondition=true`
the API server, controller manager, and scheduler.
to the API server, controller manager, and scheduler.
When `TaintNodesByCondition` is enabled, the scheduler ignores conditions when considering a Node; instead
it looks at the Node's taints and a Pod's tolerations.

Expand Down