Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update helm release postgres-operator to v1.12.0 - autoclosed #364

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Apr 17, 2024

Mend Renovate

This PR contains the following updates:

Package Type Update Change
postgres-operator config minor 1.10.1 -> 1.12.0

Release Notes

zalando/postgres-operator (postgres-operator)

v1.12.0: Blissful Ant

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 config option to prevent operator from removing secrets on cluster deletion (#​2582)
  • New flag for volumes to specify subPath as an expression to include env variables (#​2463, #​2638)
  • [UI] Allow scheduling constraints for UI deployment (#​2326)
  • [LogicalBackup] make bucket prefix for logical backup configurable (#​2609)
Enhancements
  • Apply template on all keys of OperatorConfiguration (#​2608)
  • [UI] Removal of manual authentication for user login (#​2635)
  • [UI] Centralized logging to eliminate logger errors in UI pod logs (#​2645)
  • [LogicalBackup] re-use configured pod tolerations also for logical backup job pods (#​2018)
  • [Helm] charts are using ARM images by default (#​2634)
Bugfixes
  • Add missing json mapping to infrastructure_roles_secrets config option (#​2645)
  • [Helm] fix creation of configuration when ConfigMap is used (#​2584)
  • [Helm] add pdb_master_label_selector to helm chart and example manifests (#​2595)

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

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

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

Thanks to our contributors: @​FxKu, @​idanovinda, @​hughcapet
@​dmotte, @​LordGaav, @​hemakshis, @​duckhawk, @​smutel, @​ThoreKr, @​pratheekrebala

v1.11.0: Deliberate Dog

Compare Source

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

New features
  • Added support for Postgres 16 (#​2437, #​2557)
  • ARM support for UI and logical backup images (#​2426, #​2527)
  • New config option to prevent operator from removing PVCs on cluster deletion (#​2579, #​1074)
  • New config option to specify PVC retention policy when deleting or scaling statefulset (#​2343, #​2415, #​2420, #​2584)
  • Add support for hugepages-2Mi/-1Gi in resources section incl. sidecars (#​2311, #​2512)
  • Finalizers can be enabled so custom resource in only removed after its child resources (#​941, #​2509, #​2521, #​2538)
  • Support for dead letter queue to recover from failed events (#​2421)
  • Master label selector can be disabled for the cluster's PodDisruptionBudget (#​2364, #​2595)
  • Single users can opt out from globally enabled password rotation (#​2528)
  • [LogicalBackup] Can specify extra environment variables in a logical_backup_cronjob_environment_secret (#​2051)
Enhancements
  • Allow empty resources when defaults are no set (#​2524)
  • Removal of standby section will promote the cluster (#​2472, #​2513)
  • Support switching secret rotation mode to in-place directly (#​2549)
  • Reduced number of calls on transitive team mappings (#​2445)
  • Configurable priority class for helm chart (#​2499)
  • Double check current Postgres version before trying upgrade (#​2533)
  • Inherited labels and annotations are also passed to logical backup pod (#​2456)
  • Improve appearance of Readme image in github dark mode (#​2431)
  • Improve docs on prepared users (#​2424, #​2425)
  • Improve docs structure on cluster configuration (#​2504)
  • Logging of all returned errors on closing database connections (#​2578)
  • Use Alpine 3 base image without minor version (#​2488)
  • Added unit test for cluster Create() method (#​2509)
  • Replaced deperecated ioutil package (#​2480, #​2531)
  • Bumped the pgBouncer version in pooler image to 1.22.0 (#​2529)
  • Go to 1.21 and updated depedencies (#​2554, #​2577, #​2676, #​2443, #​2433, #​2501, #​2442)
  • Add OCI label for container image source (#​2541)
  • [UI] Improve docs on watched namespaces (#​2412)
  • [LogicalBackup] Bump Ubuntu version (#​2478)
Bugfixes
  • Operator reflects new member states returned by Patroni cluster endpoint (#​2515)
  • Avoid password replacement if system users for pooler or streams are listed in the manifest (#​2489)
  • Compare single volume templates only if the number of templates has not changed (#​2493)
  • Changes to synchronous node count in Patroni section are now diffed (#​2558)
  • Update internal PostgresSpec after updating cluster status to not block subsequent updates (#​2546)
Breaking changes
  • Operator will not set the users section in Patroni config anymore (was not utilized anyway) (#​2490)
  • Dropped support for Postgres 10 (#​2557)
  • Dropped helm packages for 1.7.x releases (#​2580)

Docker image: registry.opensource.zalan.do/acid/postgres-operator:v1.11.0
Multi-arch image (arm): ghcr.io/zalando/postgres-operator:v1.11.0
UI Docker image: registry.opensource.zalan.do/acid/postgres-operator-ui:v1.11.0
Sample logical backup image: registry.opensource.zalan.do/acid/logical-backup:v1.11.0
Default Spilo image: ghcr.io/zalando/spilo-16:3.2-p2

Thanks to our contributors: @​FxKu, @​idanovinda, @​Jan-M, @​jopadi, @​hughcapet, @​sdudoladov, @​macedigital,
@​silenium-dev, @​frittentheke, @​b1zzu, @​stgrace, @​bootc, @​cstohr1, @​seekingua, @​andrejshapal, @​urashidmalik,
@​capuche2412, @​urashidmalik, @​senthilnathan, @​dgiebert, @​tm604, @​testwill, @​dmotte, @​ThoreKr, @​Lukkie,
@​drivebyer, @​sklirg, @​ghost, @​MisguidedEmails, @​ErikLundJensen, @​boomskats @​spreeker, @​regme


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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested a review from a team as a code owner April 17, 2024 08:57
@renovate renovate bot changed the title chore(deps): update helm release postgres-operator to v1.11.0 Update Helm release postgres-operator to v1.11.0 May 15, 2024
@renovate renovate bot changed the title Update Helm release postgres-operator to v1.11.0 chore(deps): update helm release postgres-operator to v1.11.0 May 27, 2024
@renovate renovate bot changed the title chore(deps): update helm release postgres-operator to v1.11.0 chore(deps): update helm release postgres-operator to v1.12.0 Jun 1, 2024
@renovate renovate bot force-pushed the renovate/postgres-operator-1.x branch from b821ae6 to 60e654d Compare June 1, 2024 00:53
@renovate renovate bot changed the title chore(deps): update helm release postgres-operator to v1.12.0 chore(deps): update helm release postgres-operator to v1.12.0 - autoclosed Jun 6, 2024
@renovate renovate bot closed this Jun 6, 2024
@renovate renovate bot deleted the renovate/postgres-operator-1.x branch June 6, 2024 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants