This is a bugfix release to the 2.0 version of the Postrges Operator. Thanks to everyone who gave feedback, raised issues or fixed bugs.
Bugfixes
- Allowing
scram-sha-256authentication as the new default for pgBouncer connections (#3193) - Fix retry loop to move the primary pod off nodes (#3179, #3190)
- Avoid switchover after migrating a single-pod cluster (#3187)
- Pass CLONE_AWS_REGION and STANDBY_AWS_REGION when IRSA is configured (#3180)
- Set
SPILO_PROVIDER=awswhen using IRSA to avoid unnecessary warning messages (#3185) - [UI] Bump js-yaml dependency to 4.3.2 (#3186)
- [helm] make UI helm chart released via gh-pages includes the values.yaml file is (back patched also for v2.0.2) - (#3178)
Breaking change
- If you rely on
md5auth for pooler connections you have to configurepassword_encryption: md5in the manifest (#3193)
Images
Postgres Operator: ghcr.io/zalando/postgres-operator:v2.0.3
Pooler: UI: ghcr.io/zalando/postgres-operator/pgbouncer:v2.0.3
UI: ghcr.io/zalando/postgres-operator-ui:v2.0.3
Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v2.0.3
Default Spilo image: ghcr.io/zalando/spilo-17:4.1-p2
Helm charts
via ghcr.io
ghcr.io/zalando/charts/postgres-operator:2.0.3
ghcr.io/zalando/charts/postgres-operator-ui:2.0.3
Thanks to our contributors: @Shubham-Padkonde, @pdixit26, @tcondeixa , @FxKu, @jopadi, @idanovinda, @rpalfi-stratec, @nctram