Update Helm release postgres-operator to v1.15.1

[renovate]

This PR contains the following updates:

Package	Update	Change
postgres-operator	minor	1.11.0 → 1.15.1

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

zalando/postgres-operator (postgres-operator)

v1.15.1: Boggling Moles

Compare Source

This is a bugfix release to the 1.15 version of the Postrges Operator. Thanks to everyone who gave feedback, raised issues or fixed bugs.

Fixes and enhancements

• fixed ghcr build pipeline and stop pushing to registry.opensource.zalan.do (#​2991, #​3010, #​3013, #​3017)
• prevent sidecars without image specification to not run into cascading failures (#​2997)
• prevent potential password override when syncing secrets fails in between (#​2969)
• handle edge case when two different users accidentally share the same secret (#​2999)
• make schedule switchover test use specific timestamp to not fail in some edge cases (#​2995)
• removed unsupported format field for integer type in Postgresql CRD (#​3017)
• update logical backup image default in OperatorConfiguration CRD (#​3017)
• reworked the e2e test runner docker file (#​3017)
• updated dependencies (#​2989, #​2996, #​2997, #​3001, #​3008, #​3011)

Breaking change

• We stopped pushing images to registry.opensource.zalan.do (#​2991, #​3017)
• Removed 1.9.0 helm chart releases

Images

Postgres Operator: ghcr.io/zalando/postgres-operator:v1.15.1
UI: ghcr.io/zalando/postgres-operator-ui:v1.15.1
Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v1.15.1
Default Spilo image: ghcr.io/zalando/spilo-17:4.0-p3

Thanks to our contributors: @​FxKu, @​idanovinda, @​mikkeloscar, @​ovnozdrach, @​berler, @​aleksandr-vin

v1.15.0: Boggling Mole

Compare Source

⚠️ This release is missing images for the UI and logical backup. Please go straight to v1.15.1.

Here's a new release of the Postgres Operator. Thanks to everyone who contributed with PRs, feedback, raising issues or providing ideas. For those asking for Postgres 18: We haven't yet included it into Spilo and you have to wait for the next minor release in Q1 2026.

Enhancements

• introducing a second PDB for critical operations e.g. to protect pods during boostrap phase (#​2830, #​2844)
• added support for Patroni's bootstrap_labels feature (#​2872, #​2875)
• ensure podAnnotations are removed from pods if reset in the config (#​2826)
• inlcude service selector comparison to compareServices. Required when switching to kubernetes_use_configmaps (#​2955)
• include external traffic policy comparison into service diffing (#​2956)
• improved maintenanceWindows checks during major version upgrades and pod migrations (#​2810, #​2842, #​2849)
• extended example RBAC in preparation to switch to configmap-based cluster management (#​2961)
• upgrade to go 1.25.3 + updated dependencies (#​2945, #​2922, #​2857)
• [UI] Remove deprecated WAL-E library and enable WAL-G backup support in UI backend (#​2915)
• [Logical backup] try to get creds from gcp metadata if LOGICAL_GOOGLE_APPLICATION_CREDENTIALS is not set (#​2837)

Bugfixes

• fix to not create duplicate secrets for rotation users (#​2863)
• fix creation of secrets in other namespaces when using preparedDatabases and OwnerReference (#​2912)
• do not remove publications of slots defined in manifest (#​2868)
• streams section removal now deletes the stream resource (#​2868)
• docs fixes (#​2896, #​2948, #​2949)

Breaking changes

• Removed 1.9.0 helm chart releases

Important note on deprecated K8s Endpoints

⚠️ This is the last release to have kubernetes_use_configmaps disabled by default. This option has once been introduced to support deployments on OpenShift but will now become the standard for K8s, too. For clusters with replicas you cannot easily switch from using Endpoints to ConfigMaps without risking a split-brain scenario because Patroni would read DCS-related facts from both these resources at the same time during a rotation. There are two possible migration paths:

Migrate in-place

This migration path requires three steps to be deployed separately:

1. Scale in all your database clusters to only one primary pod. This can be achivied with the max_instances config option set to '1'. A config change requires an operator pod restart. Make sure every Postgres cluster is scaled in to one pod before proceeding.
2. Change the operator config again and enable kubenertes_use_configmaps. Check if extra ConfigMaps ('-config' and '-failover') are created. It will also trigger a pod rotation and, since there's only the primary left, it will cause downtime.
3. Revert step 1, so all clusters are scaled out again.
4. (Optional) Remove all the Endpoints the Postgres Operator has managed before. But they do not cause eny harm if you leave them.

If you do not want to migrate all your clusters at once you can try working with multiple Postgres Operators instances that use different configs but have a CONTROLLER_ID specified. By annotating the Postgres manifest with different controller ids, you could move a single cluster through the migration steps mentioned above.

Migrate via standby clusters

To reduce impact during the migration one can also do the following steps:

1. Set up a second Postgres Operator (+ CONTROLLER_ID specified) running with ConfigMaps
2. Create standby clusters to all Postgres resources (or one by one). The standbys would then be managed by the second operator using the annotation with the corresponding controller ID. Ideally, also copy all secrets of the source cluster beforehand to avoid connection issues later (see docs).
3. Stop writes on the source cluster and promote the standby cluster. Downtime depends mostly on the deployment time of your app to point to the new database cluster.

✔️ Docker image: registry.opensource.zalan.do/acid/postgres-operator:v1.15.0
✔️ UI Docker image: registry.opensource.zalan.do/acid/postgres-operator-ui:v1.15.0
✔️ Logical Backup Docker image: registry.opensource.zalan.do/acid/logical-backup:v1.15.0

Multi-arch image (arm):
✔️ Postgres Operator: ghcr.io/zalando/postgres-operator:v1.15.0
✖️ UI: ghcr.io/zalando/postgres-operator-ui:v1.15.0
✖️ Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v1.15.0

✔️ Default Spilo image: ghcr.io/zalando/spilo-17:4.0-p3

Thanks to our contributors: @​hughcapet, @​FxKu, @​idanovinda, @​jopadi
@​ggramal, @​mortenlj, @​Juneezee, @​mjtrangoni, @​remram44

v1.14.0: Hopeful Amoeba

Compare Source

The year is coming to a close and we are happy to announce another new release of the Postgres Operator. Thanks to everyone who contributed with PRs, feedback, raising issues or providing ideas. Have a smooth transition into 2025.

New features

• support for Postgres 17 (#​2773)
• ability to set QPS and burst limits for api client to make operator handle bigger fleets better (#​2667)
• sidecars can be running with a set of Commands (#​2449, #​2825)
• support for new EBS CSI Driver (#​2677)
• provide more scaling means for streams and support ignore recovery type (zalando-internal) (#​2817)

Enhancements

• added retry logic for switchover candidate search in asynchronous mode (#​2760)
• preparedDatabases feature supports database and schema names with special characters (#​2745, #​2782)
• operator sets annotation if last major version upgrade failed, next attempt skipped when annotation is present (#​2727, #​2755)
• added more pre-checks before executing major version upgrade script (#​2772)
• remember specs of PVCs on sync to make cluster deletion not miss out on them in edge cases (#​2785)
• added compatibility with Patroni 4, but operator still uses old master label behavior for now (#​2818)
• cleaned up code problems reported by go linter (mostly redundant type from arrays) (#​2739)
• improved docs about automated major version upgrades (#​2807)
• use a more recent postgres-exporter example in servicemonitor manifest (#​2777)
• update Go to 1.23.4 and also updated dependencies (#​2824, #​2740, #​2816, #​2819)
• [Helm] make replica count for UI deployment configurable (#​2708)

Bugfixes

• update CRD schema pattern for resources to allow empty strings (#​2735)
• do not use extra labels to list stream resources because they can change and lead to duplicates (#​2803)
• Spilo image contains fix for breaking change for pushing backups with wal-g (#​2786)
• [Helm] fix indentation of extraEnvs in operator deployment (#​2783, #​2814)
• [Helm] cluste role was lacking patch privilege on PVCs (#​2762)

Breaking changes

• updated logs on SYNC and UPDATE events (breaking only if you rely on certain log messages) (#​2738)
• dropping support for Postgres 12 (#​2773)

amd images:
Docker image: registry.opensource.zalan.do/acid/postgres-operator:v1.14.0
UI Docker image: registry.opensource.zalan.do/acid/postgres-operator-ui:v1.14.0
Logical Backup Docker image: registry.opensource.zalan.do/acid/logical-backup:v1.14.0

Multi-arch image (arm):
Postgres Operator: ghcr.io/zalando/postgres-operator:v1.14.0
UI: ghcr.io/zalando/postgres-operator-ui:v1.14.0
Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v1.14.0

Default Spilo image: ghcr.io/zalando/spilo-17:4.0-p2

Thanks to our contributors: @​idanovinda, @​hughcapet, @​FxKu, @​macedigital, @​sdudoladov
@​fahedouch, @​cosimomeli, @​tabbyl21, @​Demch1k, @​dmotte, @​prasadkris,
@​mjtrangoni @​zyue110026, @​DaDummy, @​Mart-Kuc

v1.13.0: Panoramic Lapwing

Compare Source

We are excited to announce yet another new release of the Postgres Operator. Thanks to everyone who contributed with PRs, feedback, raising issues or providing ideas.

New features

• new option to enable owner references on all child resources (#​2688, #​2199)
• implement per-cluster maintenance windows to define when automatic major version upgrade can happen (#​2710, #​2731)
• [Helm] add extraEnvs for operator deployments (#​2671)

Enhancements

• pass inherited annotations also to existing child resources (#​2657, #​2713, #​2723)
• all child resources are now represented in the cluster's Go struct incl. service, endpoints/configmaps created by Patroni (#​2713, #​2733)
• stream resources are not created after errors on syning the publication and slot (#​2704, #​2728)
• update package dependencies when building image (#​2665)
• simplify delivery yaml file for building operator (#​2673)
• resolve code problems reported by newer linters (#​2715, #​2713)
• config map example has been fully aligned with CRD config defaults (#​2729)
• update Go to 1.22.5 and also updated dependencies (#​2699, #​2729)

Bugfixes

• fix deletion of resources when cluster fields are empty (#​2713)
• fix volumeMounts diff (nil vs. empty) when comparing containers (#​2686)
• do not set empty secret env vars for logical backup on GCS and Azure when not configured (#​2732)
• handle publications without tables (#​2722)

Breaking changes

• ⚠️ wal-g backups will not work out-of-the box with this release. Please use Spilo version ghcr.io/zalando/spilo-16:3.3-p3
• removing streams from manifest triggers a removal of database publication, slots and FES resources (#​2684, #​2563)
• automatic major version upgrades are enabled by default (manual mode) (#​2729)
• dropped default of additional_secret_mount_path option when configured via config CRD (#​2729)
• dropped support for Postgres 11 (#​2706)
• dropped helm packages for 1.8.2 releases (#​2729)

amd images:
Docker image: registry.opensource.zalan.do/acid/postgres-operator:v1.13.0
UI Docker image: registry.opensource.zalan.do/acid/postgres-operator-ui:v1.13.0
Logical Backup Docker image: registry.opensource.zalan.do/acid/logical-backup:v1.13.0

Multi-arch image (arm):
Postgres Operator: ghcr.io/zalando/postgres-operator:v1.13.0
UI: ghcr.io/zalando/postgres-operator-ui:v1.13.0
Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v1.13.0

Default Spilo image: ghcr.io/zalando/spilo-16:3.3-p1

Thanks to our contributors: @​idanovinda, @​FxKu, @​hughcapet, @​macedigital, @​sdudoladov
@​fahedouch, @​mbegenau, @​nickmansrob, @​desaintmartin

v1.12.2: Blissful Ants

Compare Source

This is a bugfix release to the 1.12 version of the Postrges Operator. Thanks to everyone who gave feedback, raised issues or fixed bugs.

Fixes and enhancements

• use json tag for schema mapping of InfrastructureRole struct (#​2659)
• align base images in arm build pipeline with Docker images (#​2663)
• align dependencies in Makefile (#​2647)
• [UI] fix exec format error on ARM (#​2663, #​2649)
• [UI] use nodejs-lts instead of outdated alpine version to workaround permission issue with old npm version (#​2653)

Breaking changes

• removed helm chart version 1.10.0, 1.12.0 and 1.12.1 and only provide the last point release of each version (#​2664)

amd images:
Docker image: registry.opensource.zalan.do/acid/postgres-operator:v1.12.2
UI Docker image: registry.opensource.zalan.do/acid/postgres-operator-ui:v1.12.2
Logical Backup Docker image: registry.opensource.zalan.do/acid/logical-backup:v1.12.2

Multi-arch image (arm):
Postgres Operator: ghcr.io/zalando/postgres-operator:v1.12.2
UI: ghcr.io/zalando/postgres-operator-ui:v1.12.2
Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v1.12.2

Default Spilo image: ghcr.io/zalando/spilo-16:3.2-p3

Thanks to our contributors: @​macedigital, @​FxKu, @​idanovinda, @​hemakshis, @​Skoucail @​crkochan

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.