Merge pull request #2777 from gyliu513/node-controller
Updated node controller for taints and tolerations.
This commit is contained in:
@@ -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
|
case, the node controller assumes that there's some problem with master
|
||||||
connectivity and stops all evictions until some connectivity is restored.
|
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
|
### Self-Registration of Nodes
|
||||||
|
|
||||||
When the kubelet flag `--register-node` is true (the default), the kubelet will attempt to
|
When the kubelet flag `--register-node` is true (the default), the kubelet will attempt to
|
||||||
|
|||||||
Reference in New Issue
Block a user