From ce87af7f3bfbd994e68ac708495f2d909e651e5b Mon Sep 17 00:00:00 2001 From: Guangya Liu Date: Sun, 12 Mar 2017 12:51:51 +0800 Subject: [PATCH] Updated node controller for taints and tolerations. --- docs/admin/node.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/admin/node.md b/docs/admin/node.md index 5e591ea99a..16b02a35c8 100644 --- a/docs/admin/node.md +++ b/docs/admin/node.md @@ -165,6 +165,13 @@ completely unhealthy (i.e. there are no healthy nodes in the cluster). In such case, the node controller assumes that there's some problem with master connectivity and stops all evictions until some connectivity is restored. +Starting in Kubernetes 1.6, the NodeController is also responsible for evicting +pods that are running on nodes with `NoExecute` taints, when the pods do not tolerate +the taints. Additionally, as an alpha feature that is disabled by default, the +NodeController is responsible for adding taints corresponding to node problems like +node unreachable or not ready. See [this documentation](/docs/user-guide/node-selection/index.md#taints-and-tolerations-beta-feature) +for details about `NoExecute` taints and the alpha feature. + ### Self-Registration of Nodes When the kubelet flag `--register-node` is true (the default), the kubelet will attempt to