# PodDisruptionBudget in version "policy/v1beta1"

**URL:** <https://forums.percona.com/t/poddisruptionbudget-in-version-policy-v1beta1/30858>\
**Category:** Percona Operator for MongoDB\
**Created:** [June 7, 2024, 2:38am UTC](https://forums.percona.com/t/poddisruptionbudget-in-version-policy-v1beta1/30858 "2024-06-07T02:38:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamoser](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jamoser](https://forums.percona.com/u/jamoser)\
**Post date:** [June 7, 2024, 2:38am UTC](https://forums.percona.com/t/poddisruptionbudget-in-version-policy-v1beta1/30858/1 "2024-06-07T02:38:57Z")

</div>

Hello

Cluster is on 1.27.13-gke.1000000

Operator on 1.11

I mistakenly updated the cluster with an Operator version 1.0.9. I reverted back to Operator 1.11 but the logs on Operator do not look good and started up but:

kubectl -n dev-staging-mongodb01 get all  
NAME READY STATUS RESTARTS AGE  
pod/mongodb01-cluster-cfg-0 1/1 Running 0 2m11s  
pod/mongodb01-cluster-cfg-1 1/1 Running 0 95s  
pod/mongodb01-cluster-cfg-2 1/1 Running 0 59s  
pod/percona-server-mongodb-operator-574cf768db-mdr5x 1/1 Running 0 2m27s  
NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE  
service/mongodb01-cluster-cfg ClusterIP None 27017/TCP 2y20d  
service/mongodb01-cluster-mongos ClusterIP 10.128.12.23 27017/TCP 2y20d  
service/mongodb01-cluster-rs01 ClusterIP None 27017/TCP 2y20d  
NAME READY UP-TO-DATE AVAILABLE AGE  
deployment.apps/percona-server-mongodb-operator 1/1 1 1 2m27s  
NAME DESIRED CURRENT READY AGE  
replicaset.apps/percona-server-mongodb-operator-574cf768db 1 1 1 2m27s  
NAME READY AGE  
statefulset.apps/mongodb01-cluster-cfg 3/3 2m11s

=\> the RS does not startup ?!

Operator shows these errors non stop:

“level”:“error”,“ts”:1717727752.870584,“logger”:“controller-runtime.controller”,“msg”:“Reconciler error”,“controller”:“psmdb-controller”,“request”:“dev-staging-mongodb01/mongodb01-cluster”,“error”:“reconcile StatefulSet for cfg: PodDisruptionBudget for mongodb01-cluster-cfg: get object: no matches for kind "PodDisruptionBudget" in version "policy/v1beta1"”,“errorVerbose”:"reconcile StatefulSet for cfg: PodDisruptionBudget for mongodb01-cluster-cfg: get object: no matches for kind "PodDisruptionBudget" in version "policy/v1beta1\

{“level”:“error”,“ts”:1717727752.8703017,“logger”:“controller\_psmdb”,“msg”:“failed to update cluster status”,“Request.Namespace”:“dev-staging-mongodb01”,“Request.Name”:“mongodb01-cluster”,“replset”:“rs01”,“error”:“set upgradeInProgres: StatefulSet.apps "luz-mongodb01-cluster-rs01" not found”

---

<div class="post-metadata">

**Author:** ![Sergey\_Pronin](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/sergey_pronin/32/14887_2.png) [@Sergey\_Pronin](https://forums.percona.com/u/Sergey_Pronin)\
**Post date:** [June 24, 2024, 6:15pm UTC](https://forums.percona.com/t/poddisruptionbudget-in-version-policy-v1beta1/30858/2 "2024-06-24T18:15:29Z")

</div>

Hey @jamoser ,

I’m confused with versions.

1. What was the starting version?
2. Which version you upgraded to?
3. To which you rolled back?  
3.1 And what was the procedure you used to roll it back?

PodDisruptionBudget v1beta is removed in k8s 1.25. Because of that we switched from v1beta to v1 API in Operator 1.13. Here is the PR: [K8SPSMDB-760 pdb is policy/v1 since v1.21.0 by pkeuter · Pull Request #1017 · percona/percona-server-mongodb-operator · GitHub](https://github.com/percona/percona-server-mongodb-operator/pull/1017)

So operator versions \< 1.13 will throw the error about PDB on k8s \>= 1.25.

---

<div class="post-metadata">

**Author:** ![jamoser](https://avatars.discourse-cdn.com/v4/letter/j/b2d939/32.png) [@jamoser](https://forums.percona.com/u/jamoser)\
**Post date:** [June 25, 2024, 7:19am UTC](https://forums.percona.com/t/poddisruptionbudget-in-version-policy-v1beta1/30858/3 "2024-06-25T07:19:23Z")

</div>

Pls ignore. We have updated to the latest Operator and all is ok.