Openshift-dns daemonsets doesn't include toleration to run on nodes with taints

Solution Verified - Updated -

Issue

  • Openshift-dns daemonset doesn't include toleration to run on nodes with taints. After a NoSchedule taint is configured for a node, the daemon set 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.
    • no dns-default pod found for node is reported.

    • The following alerts are triggering:

      Pods of `DaemonSet openshift-dns/dns-default` are running where they are not supposed to run.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content