3scale operator in CrashLoopBackOff status and "PodDisruptionBudget" API missing message
Issue
After upgrading our Openshift cluster to version 4.12, we are trying to upgrade our 3scale instance from version 2.11 to version 2.13, but it still remains at the old version. There is an error in the threescale-operator-controller-manager
pod of the 3scale Operator:
{"level":"error","ts":1691134791.155926,"logger":"setup","msg":"problem running manager","error":"no matches for kind \"PodDisruptionBudget\" in version \"policy/v1beta1\"","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Errornt/remote-source/deps/gomod/pkg/mod/github.com/go-logr/zapr@v0.1.1/zapr.go:128nmain.mainnt/remote-source/app/main.go:318nruntime.mainnt/opt/rh/go-toolset-1.13/root/usr/lib/go-toolset-1.13-golang/src/runtime/proc.go:203"}
Environment
- Red Hat 3scale API Management
- 2.11 On-Premises in OpenShift 4.12
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.