From 6554ad4fe0f0b8f918f0675f5d3d49e8b418350a Mon Sep 17 00:00:00 2001 From: Charles Uneze Date: Tue, 16 Apr 2024 18:11:48 +0100 Subject: [PATCH] Update content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md Co-authored-by: Ricardo Amaro --- .../docs/concepts/scheduling-eviction/taint-and-toleration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md b/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md index d7824a2a0f..f4644471e2 100644 --- a/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md +++ b/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md @@ -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.