Many Cluster Operators become unable to work after OCP upgrade if using taints feature
$ oc version
Client Version: 4.4.0-202004250654-2576e48
Server Version: 4.4.3
Kubernetes Version: v1.17.1
Steps to Reproduce:
1. Add taints one of worker nodes
$ oc adm taint nodes worker5.example.com app=batch:NoSchedule
2. Upgrade OCP
$ oc adm upgrade --to=<version>
Many Cluster Operator pods launched by daemonset disappeared after OCP upgrade.
OCP upgrade finishes with no problem.
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.6.8 security and bug fix 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.