Skip to content

Commit 8ca7db2

Browse files
authored
Merge pull request #91556 from mburke5678/mco-taint-daemonset
Tainting nodes fail for Daemonsets
2 parents 566bbe4 + b05b5ca commit 8ca7db2

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

modules/binding-infra-node-workloads-using-taints-tolerations.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -78,6 +78,8 @@ spec:
7878
+
7979
These examples place a taint on `node1` that has the `node-role.kubernetes.io/infra` key and the `NoSchedule` taint effect. Nodes with the `NoSchedule` effect schedule only pods that tolerate the taint, but allow existing pods to remain scheduled on the node.
8080
+
81+
If you added a `NoSchedule` taint to the infrastructure node, any pods that are controlled by a daemon set on that node are marked as `misscheduled`. You must either delete the pods or add a toleration to the pods as shown in the Red Hat Knowledgebase solution link:https://access.redhat.com/solutions/6592171[add toleration on `misscheduled` DNS pods]. Note that you cannot add a toleration to a daemon set object that is managed by an operator.
82+
+
8183
[NOTE]
8284
====
8385
If a descheduler is used, pods violating node taints could be evicted from the cluster.

0 commit comments

Comments
 (0)