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

Co-authored-by: Ricardo Amaro <ricardoamaro@users.noreply.github.com>
pull/45384/head
Charles Uneze 2024-04-16 18:11:48 +01:00 committed by GitHub
parent 5568cd2a39
commit 6554ad4fe0
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 1 deletions

View File

@ -65,7 +65,7 @@ tolerations:
The default Kubernetes scheduler takes taints and tolerations into account when
selecting a node to run a particular Pod. However, if you manually specify the
`.spec.nodeName` for a Pod, that action bypasses the scheduler; the Pod is then
bound onto on the node where you assigned it, even if there are `NoSchedule`
bound onto the node where you assigned it, even if there are `NoSchedule`
taints on that node that you selected.
If this happens and the node also has a `NoExecute` taint set, the kubelet will
eject the Pod unless there is an appropriate tolerance set.