Skip to content

Commit 08075dc

Browse files
Add note about nodeName ignoring a drained node
Clarify that `nodeName` still places Pods on nodes with `SchedulingDisabled` status. Please check issue [117843](kubernetes/kubernetes#117843) for more info.
1 parent 9197607 commit 08075dc

File tree

1 file changed

+5
-0
lines changed

1 file changed

+5
-0
lines changed

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

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -62,6 +62,11 @@ and respecting the PodDisruptionBudget you have defined). It is then safe to
6262
bring down the node by powering down its physical machine or, if running on a
6363
cloud platform, deleting its virtual machine.
6464

65+
{{< note >}}
66+
[nodeName](/docs/concepts/scheduling-eviction/assign-pod-node/#nodename) bypasses the scheduler,
67+
thus evicted Pods will still run on a drained node.
68+
{{< /note >}}
69+
6570
First, identify the name of the node you wish to drain. You can list all of the nodes in your cluster with
6671

6772
```shell

0 commit comments

Comments
 (0)