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

Merge pull request #40996 from matheusjunior/update-node-drain-doc 

Add note about `nodeName` ignoring a drained node
pull/41133/head
Kubernetes Prow Robot 2023-05-14 05:39:26 -07:00 committed by GitHub
parent 538669aa8e b230abcfb2
commit 0c835d843e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 10 additions and 0 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

@ -60,6 +60,16 @@ and respecting the PodDisruptionBudget you have defined). It is then safe to
bring down the node by powering down its physical machine or, if running on a
cloud platform, deleting its virtual machine.
{{< note >}}
If any new Pods tolerate the `node.kubernetes.io/unschedulable` taint, then those Pods
might be scheduled to the node you have drained. Avoid tolerating that taint other than
for DaemonSets.
If you or another API user directly set the [`nodeName`](/docs/concepts/scheduling-eviction/assign-pod-node/#nodename)
field for a Pod (bypassing the scheduler), then the Pod is bound to the specified node
and will run there, even though you have drained that node and marked it unschedulable.
{{< /note >}}
First, identify the name of the node you wish to drain. You can list all of the nodes in your cluster with
```shell