Description of problem: DaemonSet/node-resolver is not recreated by dns operator after deleting it Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-04-24-175929 How reproducible: 100% Steps to Reproduce: 1. $ oc -n openshift-dns delete ds/node-resolver 2. Actual results: all node-resolver pods are removed and the ds is not recreated. Expected results: the dns operator should watch the ds/node-resolver and recreate it if needed. Additional info: workaround is restarting the dns operator pod
verified with 4.8.0-0.nightly-2021-04-30-201824 and passed $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.8.0-0.nightly-2021-04-30-201824 True False 2m10s Cluster version is 4.8.0-0.nightly-2021-04-30-201824 $ oc -n openshift-dns delete ds/node-resolver daemonset.apps "node-resolver" deleted $ oc -n openshift-dns get ds NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE dns-default 6 6 6 6 6 kubernetes.io/os=linux 24m node-resolver 6 6 6 6 6 kubernetes.io/os=linux 3s
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.8.2 bug fix and security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2021:2438