Update to OpenShift Container Platform 4.11 stuck because openshift-dns-operator pod is in CrashLoopBackOff state

Solution Verified - Updated 2023-01-23T16:28:36+00:00 -

Issue

Today, the update from 4.10.20 to 4.11.16 got stuck because of an blocked network clusteroperator. Checking further we found the below message reported by the network co and also openshift-dns-operator is reporting CrashLoopBackOff state with failed to create operator: failed to create operator manager: Get \"https://172.30.0.1:443/api?timeout=32s\": dial tcp 172.30.0.1:443: i/o timeout.
```
message: DaemonSet "/openshift-network-diagnostics/network-check-target" is not
available (awaiting 1 nodes)
```

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