[RHOCP 4.x] openshift-dns daemonset doesn't include toleration to run on nodes with taints.
Issue
- Openshift-dns daemonset doesn't include toleration to run on nodes with taints. After a NoSchedule taint is configured for a node, the daemonset stops managing the pods on that node and 2 things happen:
- If the pods are deleted on nodes with taint, they won't be recovered.
- In OCP 4.9, alerts are shown in the OCP dashboard: Pods of DaemonSet openshift-dns/dns-default are running where they are not supposed to run.
Environment
- Red Hat OpenShift Container Platform 4.x
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.