prepare v2.0.2 release (#3167)

This commit is contained in:
Felix Kunde
2026-08-20 16:49:29 +02:00
committed by GitHub
parent ad3f4340bb
commit 7649aaf79a
25 changed files with 97 additions and 52 deletions
+1 -1
View File
@@ -1578,7 +1578,7 @@ make docker
# build in image in minikube docker env
eval $(minikube docker-env)
docker buildx build --load -t ghcr.io/zalando/postgres-operator-ui:v2.0.1 .
docker buildx build --load -t ghcr.io/zalando/postgres-operator-ui:v2.0.2 .
# apply UI manifests next to a running Postgres Operator
kubectl apply -f manifests/
+2 -2
View File
@@ -851,7 +851,7 @@ grouped under the `logical_backup` key.
runs `pg_dumpall` on a replica if possible and uploads compressed results to
an S3 bucket under the key `/<configured-s3-bucket-prefix>/<pg_cluster_name>/<cluster_k8s_uuid>/logical_backups`.
The default image is the same image built with the Zalando-internal CI
pipeline. Default: "ghcr.io/zalando/postgres-operator/logical-backup:v2.0.1"
pipeline. Default: "ghcr.io/zalando/postgres-operator/logical-backup:v2.0.2"
* **logical_backup_google_application_credentials**
Specifies the path of the google cloud service account json file. Default is empty.
@@ -1092,7 +1092,7 @@ operator being able to provide some reasonable defaults.
* **connection_pooler_image**
Docker image to use for connection pooler deployment.
Default: "ghcr.io/zalando/postgres-operator/pgbouncer:v2.0.1"
Default: "ghcr.io/zalando/postgres-operator/pgbouncer:v2.0.2"
* **connection_pooler_max_db_connections**
How many connections the pooler can max hold. This value is divided among the