kubernetes
/
website
mirror of https://github.com/kubernetes/website.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #36523 from aim-for-better/patch-2 

Update nodes.md
pull/36547/head
Kubernetes Prow Robot 2022-09-02 23:22:27 -07:00 committed by GitHub
parent 1259fa43ec 1eb37961bb
commit d82392e7af
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
content/en/docs/concepts/architecture/nodes.md
View File

@ -476,9 +476,8 @@ shutdown node comes up, the pods will be deleted by kubelet and new pods will be
created on a different running node. If the original shutdown node does not come up, created on a different running node. If the original shutdown node does not come up,
these pods will be stuck in terminating status on the shutdown node forever. these pods will be stuck in terminating status on the shutdown node forever.
To mitigate the above situation, a user can manually add the taint `node To mitigate the above situation, a user can manually add the taint `node.kubernetes.io/out-of-service` with either `NoExecute`
kubernetes.io/out-of-service` with either `NoExecute` or `NoSchedule` effect to or `NoSchedule` effect to a Node marking it out-of-service.
a Node marking it out-of-service.
If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/) If the `NodeOutOfServiceVolumeDetach`[feature gate](/docs/reference/command-line-tools-reference/feature-gates/)
is enabled on `kube-controller-manager`, and a Node is marked out-of-service with this taint, the is enabled on `kube-controller-manager`, and a Node is marked out-of-service with this taint, the
pods on the node will be forcefully deleted if there are no matching tolerations on it and volume pods on the node will be forcefully deleted if there are no matching tolerations on it and volume