postgres-operator: While deploying Zalando getting issue- could not create cluster: could not create pod disruption budget

• Which image of the operator are you using? e.g. registry.opensource.zalan.do/acid/postgres-operator:v1.8.2-26-gacb3ffd7
• Where do you run it - cloud or metal? Kubernetes Bare Metal K8s]
• Are you running Postgres Operator in production? [no]
• Type of issue? [Bug report, question, feature request, etc.]

Hi Team

We are deploying zalando with the help of helm and it was working fine in our environment earlier this month. Zalando is having some issues when deploying. It is showing an error:

could not create cluster: could not create pod disruption budget: the server could not find the requested resource" cluster-name=default/c-cluster pkg=controller worker=0

The pod distribution budget policy is deprecated in the V1.25 kubernetes version found in zalando.

We have tried installing the k8s cluster with 1.24.0 but are still getting the same issue.

Please find the error:

# Postgres Operator logs:

  Normal   Create     18s   postgres-operator  Started creation of new cluster resources
  Normal   Endpoints  18s   postgres-operator  Endpoint "default/c-cluster" has been successfully created
  Normal   Services   18s   postgres-operator  The service "default/c-cluster" for role master has been successfully created
  Normal   Services   18s   postgres-operator  The service "default/c-cluster-repl" for role replica has been successfully created
  Normal   Secrets    17s   postgres-operator  The secrets have been successfully created
  Warning  Create     17s   postgres-operator  could not create cluster: could not create pod disruption budget: the server could not find the requested resource

Kubernetes version

k8smn    Ready      control-plane,master   39d   v1.24.0
k8swn1   Ready      worker                         39d   v1.24.0
k8swn2   Ready      worker                         39d   v1.24.0

Operator Logs:

time="2022-11-01T07:01:55Z" level=info msg="creating a new Postgres cluster" cluster-name=default/c-cluster pkg=controller worker=0
time="2022-11-01T07:01:55Z" level=warning msg="master is not running, generated master endpoint does not contain any addresses" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:55Z" level=info msg="endpoint \"default/c-cluster\" has been successfully created" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:55Z" level=info msg="master service \"default/c-cluster\" has been successfully created" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:55Z" level=info msg="replica service \"default/c-cluster-repl\" has been successfully created" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:55Z" level=debug msg="team API is disabled" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:55Z" level=debug msg="team API is disabled" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:55Z" level=info msg="users have been initialized" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:55Z" level=info msg="syncing secrets" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:56Z" level=info msg="secrets have been successfully created" cluster-name=default/c-cluster pkg=cluster worker=0
time="2022-11-01T07:01:56Z" level=error msg="could not create cluster: could not create pod disruption budget: the server could not find the requested resource" cluster-name=default/c-cluster pkg=controller worker=0

With the same configuration, it was working fine. Can you please help to fix this issue