chore(deps): update dependency cloudnative-pg/cloudnative-pg to v1.19.1 #7

Merged
renovator merged 1 commits from renovate/crds-catalog into main 2023-03-20 11:08:49 +01:00
Member

This PR contains the following updates:

Package Update Change
cloudnative-pg/cloudnative-pg patch v1.19.0 -> v1.19.1

Release Notes

cloudnative-pg/cloudnative-pg

v1.19.1

Compare Source

Release date: March 20, 2023

Enhancements:

  • Allow overriding the default backup target policy (#​1602): previously, all backups and scheduled backups would use the cluster-level target policy
  • Extend the debug cluster's log level to the initdb job (#​1503)
  • Support IPv6 and custom pg_hba for the PgBouncer pooler (#​1395)
  • Enhance observability of backups with two new metrics and additional information in the status (#​1428)
  • Document API calls from the instance manager (#​1641)
  • Clarify deployment name via Helm (#​1505)
  • Add the psql command to the cnpg plugin for kubectl (#​1668) allowing the user to start a psql session with a pod (the primary by default)

Technical enhancements:

  • Adopt Renovate for dependency tracking/updating (#​1367, #​1473)
  • Inject binaries for all supported architectures in the operator image (#​1513)
  • Use the backup name to match resources in the backup object store (#​1650) Leverages the --name option introduced with Barman 3.3 to make the association betwen backups and the object store more robust.

Fixes:

  • Prevent panic with error handling in the probes (#​1716)
  • Ensure that the HTTP package and controller runtime logs are in JSON format (#​1442)
  • Adds WAL storage to a cluster in a single instance Cluster (#​1570)
  • Various improvements to make backup code more robust (#​1536, #​1564, #​1588, #​1466, #​1647)
  • Properly show WAL archiving information with status command of the cnpg plugin (#​1666)
  • Ensure nodeAffinity is applied even if AdditionalPodAffinity and AdditionalPodAntiAffinity are not set (#​1663)
  • Introduce failover delay during OnlineUpgrading phase (#​1728) Previously, the online upgrade process could trigger failover logic unnecessarily.

Configuration

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

🚦 Automerge: Enabled.

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 Renovate Bot.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [cloudnative-pg/cloudnative-pg](https://github.com/cloudnative-pg/cloudnative-pg) | patch | `v1.19.0` -> `v1.19.1` | --- ### Release Notes <details> <summary>cloudnative-pg/cloudnative-pg</summary> ### [`v1.19.1`](https://github.com/cloudnative-pg/cloudnative-pg/releases/tag/v1.19.1) [Compare Source](https://github.com/cloudnative-pg/cloudnative-pg/compare/v1.19.0...v1.19.1) **Release date:** March 20, 2023 Enhancements: - Allow overriding the default backup target policy ([#&#8203;1602](https://github.com/cloudnative-pg/cloudnative-pg/issues/1602)): previously, all backups and scheduled backups would use the cluster-level target policy - Extend the `debug` cluster's log level to the `initdb` job ([#&#8203;1503](https://github.com/cloudnative-pg/cloudnative-pg/issues/1503)) - Support IPv6 and custom `pg_hba` for the PgBouncer pooler ([#&#8203;1395](https://github.com/cloudnative-pg/cloudnative-pg/issues/1395)) - Enhance observability of backups with two new metrics and additional information in the status ([#&#8203;1428](https://github.com/cloudnative-pg/cloudnative-pg/issues/1428)) - Document API calls from the instance manager ([#&#8203;1641](https://github.com/cloudnative-pg/cloudnative-pg/issues/1641)) - Clarify deployment name via Helm ([#&#8203;1505](https://github.com/cloudnative-pg/cloudnative-pg/issues/1505)) - Add the `psql` command to the `cnpg` plugin for `kubectl` ([#&#8203;1668](https://github.com/cloudnative-pg/cloudnative-pg/issues/1668)) allowing the user to start a `psql` session with a pod (the primary by default) Technical enhancements: - Adopt Renovate for dependency tracking/updating ([#&#8203;1367](https://github.com/cloudnative-pg/cloudnative-pg/issues/1367), [#&#8203;1473](https://github.com/cloudnative-pg/cloudnative-pg/issues/1473)) - Inject binaries for all supported architectures in the operator image ([#&#8203;1513](https://github.com/cloudnative-pg/cloudnative-pg/issues/1513)) - Use the backup name to match resources in the backup object store ([#&#8203;1650](https://github.com/cloudnative-pg/cloudnative-pg/issues/1650)) Leverages the `--name` option introduced with Barman 3.3 to make the association betwen backups and the object store more robust. Fixes: - Prevent panic with error handling in the probes ([#&#8203;1716](https://github.com/cloudnative-pg/cloudnative-pg/issues/1716)) - Ensure that the HTTP package and controller runtime logs are in JSON format ([#&#8203;1442](https://github.com/cloudnative-pg/cloudnative-pg/issues/1442)) - Adds WAL storage to a cluster in a single instance Cluster ([#&#8203;1570](https://github.com/cloudnative-pg/cloudnative-pg/issues/1570)) - Various improvements to make backup code more robust ([#&#8203;1536](https://github.com/cloudnative-pg/cloudnative-pg/issues/1536), [#&#8203;1564](https://github.com/cloudnative-pg/cloudnative-pg/issues/1564), [#&#8203;1588](https://github.com/cloudnative-pg/cloudnative-pg/issues/1588), [#&#8203;1466](https://github.com/cloudnative-pg/cloudnative-pg/issues/1466), [#&#8203;1647](https://github.com/cloudnative-pg/cloudnative-pg/issues/1647)) - Properly show WAL archiving information with `status` command of the `cnpg` plugin ([#&#8203;1666](https://github.com/cloudnative-pg/cloudnative-pg/issues/1666)) - Ensure `nodeAffinity` is applied even if `AdditionalPodAffinity` and `AdditionalPodAntiAffinity` are not set ([#&#8203;1663](https://github.com/cloudnative-pg/cloudnative-pg/issues/1663)) - Introduce failover delay during OnlineUpgrading phase ([#&#8203;1728](https://github.com/cloudnative-pg/cloudnative-pg/issues/1728)) Previously, the online upgrade process could trigger failover logic unnecessarily. </details> --- ### Configuration 📅 **Schedule**: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined). 🚦 **Automerge**: Enabled. ♻ **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. --- - [ ] <!-- rebase-check -->If you want to rebase/retry this PR, check this box --- This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate). <!--renovate-debug:eyJjcmVhdGVkSW5WZXIiOiIzNS4xNC4wIiwidXBkYXRlZEluVmVyIjoiMzUuMTQuMCJ9-->
renovator added 1 commit 2023-03-20 11:03:15 +01:00
continuous-integration/drone/pr Build is passing Details
continuous-integration/drone/push Build is passing Details
3e533fcca4
chore(deps): update dependency cloudnative-pg/cloudnative-pg to v1.19.1
renovator merged commit 3e533fcca4 into main 2023-03-20 11:08:49 +01:00
Sign in to join this conversation.
No reviewers
No Label
No Milestone
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: infra/crds-catalog#7
No description provided.