Repository navigation
fix(deps): update module github.com/cloudnative-pg/cloudnative-pg to v1.30.2 - #1247
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
…v1.30.2 | datasource | package | from | to | | ---------- | ---------------------------------------- | ------- | ------- | | go | github.com/cloudnative-pg/cloudnative-pg | v1.30.1 | v1.30.2 | Signed-off-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.30.1→v1.30.2Release Notes
cloudnative-pg/cloudnative-pg (github.com/cloudnative-pg/cloudnative-pg)
v1.30.2Compare Source
Release date: Nov 17, 2026
Important changes
PostgreSQL 18.7 is the new default image: the default operand image is now
18.7-system-trixie, which fixes several CVEs. It applies only to new clusters that don't set an image. To get the fixes, update existing clusters to 18.7, 17.12, 16.16 or 15.20 by changingimageNameor theImageCatalog. Before updating, read the PostgreSQL 18.7 announcement and the release notes it links. (#11833)PostgreSQL 14 is no longer supported: the PostgreSQL community stopped fixing PostgreSQL 14 on November 12, 2026, and CloudNativePG supports a major version only as long as PostgreSQL does. If you still run PostgreSQL 14, plan an upgrade to a newer major version. PostgreSQL 15 stops receiving fixes on November 11, 2027. (#11935)
The operator now needs the
deletepermission onleases. Users who manage the RBAC manually must add it. (#11609)Enhancements
Streaming retry for standbys on the WAL archive: PostgreSQL tries streaming only after a restore from the archive fails. If WAL is produced about as fast as it is restored, that may never happen, and the standby stays on the archive, with no WAL receiver and no part in synchronous replication. Now, after 30 seconds of continuous restores, WAL restore fails on purpose for 5 seconds, so PostgreSQL tries streaming. These failures are expected and can appear in the logs. (#11868)
Server-side encryption with customer-provided keys (SSE-C): added
sseCustomerKeyins3Credentials, to use SSE-C with S3-compatible object stores. It works with backups, WAL archiving and recovery. (#11711, #11775)BackupandScheduledBackupresources that use thebarmanObjectStoremethod now return an admission warning about the removal of native Barman Cloud support in 1.32, asClusterresources already did. (#11725)extension_control_pathanddynamic_library_pathno longer list directories that are missing from an extension image, for examplesharein an image that ships onlylib. (#11652)Transient network errors from
barman-cloud-wal-restoreare now logged (needs Barman 3.20.0 or later). (#11541)Moved the "Defaulting for ..." operator log lines from info to debug level. They were printed at every reconciliation and hid other messages. (#11790)
cnpgplugin:kubectl cnpg statusno longer fails without thepods/execpermission. It showsnot permitted: requires the pods/exec permissioninstead of the size and configuration sections. (#11687)Security and Supply Chain
golang.org/x/netto v0.62.0, fixing GO-2026-6617, GO-2026-6612, GO-2026-6611, GO-2026-6610, GO-2026-6603, GO-2026-6860 and GO-2026-6866, and bumped the othergolang.org/xmodules. (#11631, #11867)Changes
Updated the default PgBouncer image from 1.25.2 to 1.26.1. Poolers that use the default image roll out the new version when the operator is upgraded. (#11571, #11704)
Updated the
barman-cloudlibrary to v0.7.0, which skips failed backups when it reads the backup catalog. (#11711)Fixes
Fixed enabling a sidecar plugin on a running cluster. Pods created before that have no sidecar until they are recreated. They logged
Unknown pluginerrors, their metrics scrapes failed, and a switchover could wait forever. When the plugin archives WAL, the former primary crash looped until the Pod was deleted. The operator now recreates it. (#11858)Fixed replicas created from an online volume snapshot ignoring the
backup_labelandtablespace_mapstored in the snapshot. PostgreSQL did crash recovery and did not fetch WAL from the archive. (#11847)Fixed logical decoding stalling while a new replica was bootstrapping, with
synchronizeLogicalDecodingenabled. The replica is now left out ofsynchronized_standby_slots(orpg_failover_slots.standby_slot_names) until its volume is initialized. (#11802)Fixed
status.phaseReasonbeing cleared and set again several times a second while a cluster was being created or changed, for example "Some instances are not yet active". This loaded the API server and madekubectl get cluster -wnoisy. (#11789)Fixed the operator retrying instance status requests that failed with an error response, as if the failure was a network error. During a switchover the old primary answers with an error while PostgreSQL is stopped, so each reconciliation waited about 1.6 seconds, which slowed the whole switchover. Contributed by @kabbydriver. (#11793)
Fixed the WAL count and size metrics counting
.partial,.backupand.historyfiles. (#9967)Fixed replicas crash looping with
recovery aborted because of insufficient parameter settingsafter a hot standby parameter such asmax_connectionswas removed from.spec.postgresql.parameters. Contributed by @ichibahn. (#11236)Fixed the instance manager waiting forever on a frozen postmaster, one that accepts connections but never answers. This blocked the instance status, the metrics exporter and the check before an in-tree backup. Local connection attempts to PostgreSQL now time out after 5 seconds. (#11718)
Fixed a
Clusterrecreated over leftover resources (for example by a backup tool) staying inUnable to create required cluster objectswithcannot set an ownerRef on a resource you can't delete. This happened with theOwnerReferencesPermissionEnforcementadmission plugin. When restoring over orphan PVCs, the operator now deletes the stale primaryLease, so the new primary does not wait for it to expire. (#11609)Fixed WAL restore reporting the end of the WAL archive on the wrong timeline. A replica restored from a snapshot could miss valid WAL of the new timeline and replay WAL of the parent timeline instead. Contributed by @ardentperf. (#11133)
Fixed a
Clusternot being reconciled again when a plugin asked for a retry without a delay. For example, aClustercreated before theObjectStoreof the Barman Cloud plugin stayed inBootstrapPending. The operator now retries after one second. Contributed by @valeriodelsarto. (#11683)Fixed
ConsistentSystemIDturningFalsewhile PostgreSQL is not running, for example in replica clusters after a demotion, or on fenced instances. The system ID is now read from disk, so it no longer needs a running PostgreSQL. (#11645)Fixed a
Backupthat could be started more than once, or moved back topendingafter it started. (#11617)cnpgplugin:kubectl cnpg backupfor volume snapshot backups: when only one of--immediate-checkpointand--wait-for-archivewas set, the other option used its default instead of the value in.spec.backup.volumeSnapshot.onlineConfiguration. (#11733)Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.