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

Update content/en/docs/tasks/administer-cluster/safely-drain-node.md 

Co-authored-by: Tim Bannister <tim@scalefactory.com>
pull/38917/head
Thomas Güttler 2023-01-13 11:39:39 +01:00 committed by GitHub
parent 27ab5439c8
commit 2e3da350b4
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
content/en/docs/tasks/administer-cluster/safely-drain-node.md
View File

@ -69,10 +69,12 @@ Next, tell Kubernetes to drain the node:
kubectl drain --ignore-daemonsets <node name> kubectl drain --ignore-daemonsets <node name>
``` ```
If there are daemon set managed pods, drain will not proceed without `--ignore-daemonsets`, If there are DaemonSet managed pods, drain will usually not succeed unless you specify
and regardless it will not delete any daemon set managed pods, `--ignore-daemonsets`. The `kubectl drain` subcommand on its own does not actually drain
because those pods would be immediately replaced by the daemon set controller, a node of its DaemonSet pods:
which ignores unschedulable markings. the DaemonSet controller (part of the control plane) immediately replaces missing Pods with
new equivalent Pods. The DaemonSet controller also creates Pods that ignore unschedulable
taints, which allows the new Pods to launch onto a node that you are draining.
Once it returns (without giving an error), you can power down the node Once it returns (without giving an error), you can power down the node
(or equivalently, if on a cloud platform, delete the virtual machine backing the node). (or equivalently, if on a cloud platform, delete the virtual machine backing the node).