From 3dd265c40bb035c21beb83d57bdc575fc392e18c Mon Sep 17 00:00:00 2001 From: Draven Date: Tue, 22 Oct 2019 09:09:21 +0800 Subject: [PATCH] feat: graduate TaintNodesByCondition to GA (#17073) --- content/en/docs/concepts/configuration/taint-and-toleration.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/docs/concepts/configuration/taint-and-toleration.md b/content/en/docs/concepts/configuration/taint-and-toleration.md index 7e95539ddf..67a5574ac1 100644 --- a/content/en/docs/concepts/configuration/taint-and-toleration.md +++ b/content/en/docs/concepts/configuration/taint-and-toleration.md @@ -280,7 +280,7 @@ which matches the behavior when this feature is disabled. ## Taint Nodes by Condition -In version 1.12, `TaintNodesByCondition` feature is promoted to beta, so node lifecycle controller automatically creates taints corresponding to +The node lifecycle controller automatically creates taints corresponding to Node conditions. Similarly the scheduler does not check Node conditions; instead the scheduler checks taints. This assures that Node conditions don't affect what's scheduled onto the Node. The user can choose to ignore some of the Node's problems (represented as Node conditions) by adding appropriate Pod tolerations. Note that `TaintNodesByCondition` only taints nodes with `NoSchedule` effect. `NoExecute` effect is controlled by `TaintBasedEviction` which is a beta feature and enabled by default since version 1.13.