chore(deps): update helm release postgres-operator to v2 #105
No reviewers
Labels
No labels
No milestone
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
shivering-isles/infrastructure-gitops!105
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/postgres-operator-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.15.1→2.0.1Release Notes
zalando/postgres-operator (postgres-operator)
v2.0.1: Postgres Operator v2.0.1Compare Source
This is a new major release. Please, read the instructions how to migrate to v2.0. Thanks to everyone who contributed with PRs, feedback, raising issues or providing ideas.
New features
Enhancements
standby_hostcan be combined withs3_wal_pathto help with cross infra migrations (#3033)cluster_labelsand annotations also passed to logical backup CronJob and Jobs (#2117 ,#3085)Bugfixes
Breaking changes
kubernetes_use_configmapsis now true by default because endpoints will disappear (#3102, #3116)aws-load-balancer-connection-idle-timeoutby default (#3054)enable_ebs_gp3_migrationandenable_ebs_gp3_migration_max_size) (#3142)useLoadBalancer,replicaLoadBalancerandpod_priority_class_nameandinit_containers(#3106)Images
Postgres Operator: ghcr.io/zalando/postgres-operator:v2.0.1
Pooler: UI: ghcr.io/zalando/postgres-operator/pgbouncer:v2.0.1
UI: ghcr.io/zalando/postgres-operator-ui:v2.0.1
Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v2.0.1
Default Spilo image: ghcr.io/zalando/spilo-17:4.1-p2
Helm charts
via ghcr.io
ghcr.io/zalando/charts/postgres-operator:2.0.1
ghcr.io/zalando/charts/postgres-operator-ui:2.0.1
or via Github pages
https://opensource.zalando.com/postgres-operator/charts/postgres-operator/Chart.yaml
https://opensource.zalando.com/postgres-operator/charts/postgres-operator-ui/Chart.yaml
Thanks to our contributors: @FxKu, @mikkeloscar, @idanovinda, @hughcapet, @tcondeixa, @jopadi,
@raphaeltorquat0, @lucasl0st, @laiminhtrung1997, @thoro, @annielzy, @unkhz @jorsol, @pierreozoux,
@kadaffy, @k0da, @chobostar, @a1994sc, @aslafy-z, @zak905, @addreas, @SAY-5, @alimelgohary,
@ioanalytica, @dandeandean, @exciler, @bramhanandlingala, @yajo, @a-thomas-22, @davidspek,
@sdudoladov, @nctram
v2.0.0: Postgres Operator v2Compare Source
See release notes of v2.0.1. The OperatorConfigurationCRD contained a type mismatch that breaks GitOps pipelines.
Images
Postgres Operator: ghcr.io/zalando/postgres-operator:v2.0.0
Pooler: UI: ghcr.io/zalando/postgres-operator/pgbouncer:v2.0.0
UI: ghcr.io/zalando/postgres-operator-ui:v2.0.0
Logical Backup: ghcr.io/zalando/postgres-operator/logical-backup:v2.0.0
Default Spilo image: ghcr.io/zalando/spilo-17:4.1-p2
Thanks to our contributors: @FxKu, @mikkeloscar, @idanovinda, @hughcapet, @tcondeixa, @jopadi,
@raphaeltorquat0, @lucasl0st, @laiminhtrung1997, @thoro, @annielzy, @unkhz @jorsol, @pierreozoux,
@kadaffy, @k0da, @chobostar, @a1994sc, @aslafy-z, @zak905, @addreas, @SAY-5, @alimelgohary,
@dandeandean, @exciler, @bramhanandlingala, @yajo, @a-thomas-22, @davidspek, @sdudoladov, @nctram
Configuration
📅 Schedule: (UTC)
🚦 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.
This PR has been generated by Renovate Bot. The local configuration can be found in the SI Renovate Bot repository.
4db769cd15b0dc643820To migrate:
Scale-in all your database clusters to only one primary instance. This can be done by changing the global config options max_instances and min_instances to 1. If you have allowed users to ignore globally defined instance limits by configuring an ignore_instance_limits_annotation_key, remove it for now.
Wait for all clusters to be healthy and change the kubernetes_use_configmaps setting to true. This will trigger the replacement of the primary pod of all clusters and cause downtime for as long as the pods are rescheduled and start up.
Check again that all clusters are healthy with configmaps created. There should be three for each cluster called like cluster name with suffixes -config, -failover and -leader. Now, revert the changes from step 1 and scale-out the to number of instances set in the manifests.
The orphaned endpoints, which use the same names like the new configmaps, have to be deleted by you or your K8s garbage collection.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.