Skip to content

Commit 0faafb0

Browse files
authored
Merge pull request #45384 from network-charles/network-charles-patch-1
Update Taints and Tolerations Documentation
2 parents e88e8da + 6554ad4 commit 0faafb0

File tree

1 file changed

+9
-1
lines changed

1 file changed

+9
-1
lines changed

content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md

Lines changed: 9 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,15 @@ tolerations:
6262
effect: "NoSchedule"
6363
```
6464
65-
Here's an example of a pod that uses tolerations:
65+
The default Kubernetes scheduler takes taints and tolerations into account when
66+
selecting a node to run a particular Pod. However, if you manually specify the
67+
`.spec.nodeName` for a Pod, that action bypasses the scheduler; the Pod is then
68+
bound onto the node where you assigned it, even if there are `NoSchedule`
69+
taints on that node that you selected.
70+
If this happens and the node also has a `NoExecute` taint set, the kubelet will
71+
eject the Pod unless there is an appropriate tolerance set.
72+
73+
Here's an example of a pod that has some tolerations defined:
6674

6775
{{% code_sample file="pods/pod-with-toleration.yaml" %}}
6876

0 commit comments

Comments
 (0)