We have noticed an instance of incorrect helming in one of your Kubernetes configuration files. Hardcoded or default configuration values in the template are considered anti-pattern and configurable values in the values.yaml file are not being respect, resulting in user-provided configurations never being applied. Additionally, we provide anecdotal evidence from trivy-operator#729 regarding the incorrect helming defect.

replicaCount does not take effect when changed to a value other than 1. This issue arises due to replicaCount value is hardcoded in deployment.yaml file:

Please, answer some short questions which should help us to understand your problem / question better?

• Which image of the operator are you using?

ghcr.io/zalando/postgres-operator:v1.12.2

• Where do you run it - cloud or metal? Kubernetes or OpenShift? [AWS K8s | GCP ... | Bare Metal K8s]
  Bare Metal K8s
• Are you running Postgres Operator in production? [yes | no]
  no
• Type of issue? [Bug report, question, feature request, etc.]
  Bug report
  Some general remarks when posting a bug report:
• Please, check the operator, pod (Patroni) and postgresql logs first. When copy-pasting many log lines please do it in a separate GitHub gist together with your Postgres CRD and configuration manifest.
• If you feel this issue might be more related to the Spilo docker image or Patroni, consider opening issues in the respective repos.