wang.jun.1974 reported:

Today i update my lab cluster from 4.11.5 -> 4.11.21 -> 4.12.0.rc6. After upgrade finished pod ‘updateservice-operator’ is in ‘CrashLoopBackOff’ Status.:thread:

$ oc get pods -n openshift-update-service
NAME                                        READY   STATUS             RESTARTS         AGE
update-service-oc-mirror-596fbfbcfb-kxvh4   2/2     Running            4                18h
updateservice-operator-58596cbfcd-p6hdr     0/1     CrashLoopBackOff   21 (4m36s ago)   24h

$ oc -n openshift-update-service logs $(oc get pods -n openshift-update-service -l name=updateservice-operator -o name ) 
...
2022-12-30T04:51:14.711Z        ERROR   controller-runtime.source       if kind is a CRD, it should be installed before calling Start   {"kind": "PodDisruptionBudget.policy", "error": "no matches for kind \"PodDisruptionBudget\" in version \"policy/v1beta1\""}
...

We are using v1beta1 PDB e.g. in https://github.com/openshift/cincinnati-operator/blob/81be0659170ef22c04f7fb23622a5a41c748e581/controllers/new.go#L79 and we should probably also check whether it is using some other to-be-deprecated APIs