From 84f35c3cc99cdab5699e175ad4b6a35eac280dd0 Mon Sep 17 00:00:00 2001 From: Thiago Vinhas Date: Mon, 8 Jan 2018 15:11:11 -0500 Subject: [PATCH] Provide command to "untaint" a node Had a lot of trouble finding the exact way to "un-do" the tainting example provided here. Even the great folks on Slack couldn't provide the correct command to achieve this, even though it seems so trivial now that I know it. :-) --- docs/concepts/configuration/taint-and-toleration.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/concepts/configuration/taint-and-toleration.md b/docs/concepts/configuration/taint-and-toleration.md index ebf153aa2d..75207274f2 100644 --- a/docs/concepts/configuration/taint-and-toleration.md +++ b/docs/concepts/configuration/taint-and-toleration.md @@ -31,6 +31,12 @@ kubectl taint nodes node1 key=value:NoSchedule places a taint on node `node1`. The taint has key `key`, value `value`, and taint effect `NoSchedule`. This means that no pod will be able to schedule onto `node1` unless it has a matching toleration. + +To remove the taint added by the command above, you can run: +```shell +kubectl taint nodes kube11 key:NoSchedule- +``` + You specify a toleration for a pod in the PodSpec. Both of the following tolerations "match" the taint created by the `kubectl taint` line above, and thus a pod with either toleration would be able to schedule onto `node1`: