Add toleration seconds condition

kubernetes · Sep 22, 2020 · ad4d75f · ad4d75f
1 parent 15011a6
commit ad4d75f
Showing 1 changed file with 3 additions and 0 deletions.
diff --git a/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md b/content/en/docs/concepts/scheduling-eviction/taint-and-toleration.md
@@ -101,6 +101,9 @@ effect `PreferNoSchedule` then Kubernetes will *try* to not schedule the pod ont
 * if there is at least one un-ignored taint with effect `NoExecute` then the pod will be evicted from
 the node (if it is already running on the node), and will not be
 scheduled onto the node (if it is not yet running on the node).
+* if there is only one tolerated taint with effect `NoExecute` then the pod will still be scheduled onto the node even if
+the toleration has toleration seconds which causes a probability that the pod will be repeatedly scheduled onto the node,
+this can be solved by adding a `NoSchedule` taint to the node.
 
 For example, imagine you taint a node like this