What cloudnative-pg/cloudnative-pg shipped
Written by FoxPlug from the repository's own releases; not affiliated with Cloudnative-pg. Paste your own repository in the box below and FoxPlug writes the same weekly update for your product. This page is an automatic summary of the releases, pull requests and commits in github.com/cloudnative-pg/cloudnative-pg; Cloudnative-pg did not write it and does not use or endorse FoxPlug. Every line links to the change it describes.
Get a weekly update like this for your product, free
Week of October 5, 2026
What shipped
- Updated the golang.org/x modules to fix the govulncheck findings, moving net, text, mod, sync and tools to newer versions. Pull request #11631
- Bumped the threat assessment artifacts to Gemara v1.6.0 and updated the SECURITY_INSIGHTS.yml self-assessment to reference the same version. Pull request #11567
- Fixed the replica switchover end-to-end test so it no longer runs out of disk, pausing inserts, capping
max_wal_sizeat 256MB and giving WAL its own 1Gi volume. Pull request #11626 - Made the replica switchover end-to-end test wait for the rollout, since leaving replica mode changes
archive_modeand the operator restarts the primary afterwards. Pull request #11620 - Removed the kubeadmin user after the OpenShift installation in CI and hid its password in the installer output. Pull request #11619
Why it matters
This week the project closed three security and CI hygiene gaps and made two end-to-end tests reliable. Dependencies were bumped to clear govulncheck findings, the threat assessment artifacts were brought to Gemara v1.6.0, and the OpenShift job no longer leaves a kubeadmin user with a password printed in logs. The replica switchover tests no longer fail from a full disk or from querying the primary mid-restart.
Changelog entry
- Fix(deps): bump golang.org/x modules to fix govulncheck findings Pull request #11631
- Chore: bump threat assessment artifacts to Gemara v1.6.0 Pull request #11567
- Test(e2e): stop the replica switchover clusters from running out of disk Pull request #11626
- Test(e2e): wait for the replica switchover rollout Pull request #11620
- Ci(openshift): remove the kubeadmin user after the installation Pull request #11619
Dependency bumps clear govulncheck findings, threat assessment artifacts move to Gemara v1.6.0, and OpenShift CI drops the kubeadmin user after install. Replica switchover e2e tests now stop running out of disk and wait for the rollout.
This week in CloudNativePG: updated golang.org/x modules to fix govulncheck findings, bumped threat assessment artifacts to Gemara v1.6.0 with SECURITY_INSIGHTS.yml aligned to the same version, and removed the kubeadmin user after the OpenShift installation while hiding its password in installer output. The replica switchover end-to-end tests got two fixes: inserts are paused and max_wal_size is capped at 256MB with WAL on its own 1Gi volume so the disk no longer fills, and the spec waits for the second cluster to be ready before querying it, avoiding mid-restart reads.
Week of September 28, 2026
What shipped
- Fixed restore process hanging when backup tool restores an instance Pod with its PVC by making the restore gate skip the operator's own init containers. Pull request #11549
- Replaced rapid test dependency licensed under MPL-2.0 with seeded loop from standard library to resolve licensing concerns flagged by Snyk. Pull request #11592
- Increased upgrade suite timeout to 2 hours to accommodate slower cloud runs that were timing out healthy specs. Pull request #11597
- Added logging of transient network errors with barman-cloud-wal-restore, available from Barman 3.20.0 onwards. Pull request #11541
- Made GKE region and machine type configurable via repository variables, changing default region from europe-west3 to europe-west4. Pull request #11578
- Fixed Renovate error when attempting to pin pgbouncer image digest by removing unsupported digest storage from DefaultPgbouncerImage. Pull request #11576
- Dropped Kubernetes 1.29.x from automation and updated issue template version dropdown as 1.29.3 was the final 1.29.x release. Pull request #11564
- Clarified end-to-end test documentation to explain that goroutine stacks are logged to pod logs rather than exec output. Pull request #11596
Why it matters
This week addresses critical restore issues that were blocking deployments, resolves licensing compliance concerns, and improves CI reliability by increasing timeouts and making infrastructure configuration more flexible. These changes enhance stability for users relying on backup and restore workflows.
Changelog entry
- Fixed restore process hanging by making restore gate skip operator's own init containers (bootstrap-controller, bootstrap-instance) Pull request #11549
- Replaced rapid test dependency (MPL-2.0) with seeded loop from standard library for licensing compliance Pull request #11592
- Increased upgrade suite timeout to 2 hours to prevent healthy specs from timing out on slower cloud runs Pull request #11597
- Added transient network error logging with barman-cloud-wal-restore (requires Barman 3.20.0+) Pull request #11541
- Made GKE region and machine type configurable via GKE_REGION and GKE_MACHINE_TYPE variables; default region changed to europe-west4 Pull request #11578
- Fixed Renovate error attempting to pin pgbouncer image digest by removing unsupported digest storage from DefaultPgbouncerImage Pull request #11576
- Dropped Kubernetes 1.29.x from backport, CI, and CD workflows as 1.29.3 was final release Pull request #11564
This week: fixed restore hangs with backup tools, resolved licensing flags, improved CI reliability with longer timeouts, and made GKE configuration more flexible for different environments.
This week's updates focus on reliability and compliance. We fixed an issue where restore operations would hang when backup tools recreate Pods with PVCs, replaced a licensing-flagged test dependency with a standards-based approach, increased CI timeouts to prevent false failures on slower cloud runs, and made GKE infrastructure configuration more flexible. These changes strengthen backup/restore workflows and improve test reliability.
Week of September 21, 2026
What shipped
- Released v1.30.1 with restoreAdditionalCommandArgs support for.barmanObjectStore.data to forward custom flags to barman-cloud-restore during recovery Release
- Released v1.29.3, the final release in the 1.29.x series, with the same restoreAdditionalCommandArgs enhancement Release
- Fixed data checksums flag handling on PostgreSQL 18+ by setting --no-data-checksums when dataChecksums is false Pull request #11488
- Reverted restore certificate-wait deadlock fix that only changed where bootstrap-instance init containers got stuck without fixing the underlying issue Pull request #11548
- Fixed inheritedMetadata labels being discarded on PVC reconciliation by reordering label application Pull request #11499
- Fixed two monitoring alerts that latched forever after firing by correcting DatabaseDeadlockConflicts and DatabaseLockConflicts rules Pull request #11510
- Fixed Pooler and DatabaseRole objects recreating their owned resources after deletion, which blocked external finalizers like ArgoCD's foreground deletion Pull request #11359
- Fixed replica cluster designated primary sort order so the operator promotes the correct standby Pull request #11494
- Documented a cascading standby reconnect bug fixed in PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 for replica cluster users Pull request #11546
- Clarified that the primary isolation check only fails the liveness probe, triggering container restart through smart shutdown Pull request #11518
Why it matters
Two minor releases ship with recovery improvements for Barman Cloud backups. Several fixes address monitoring false positives, object deletion ordering, and replica cluster reliability. PostgreSQL 18 compatibility receives attention with data checksums handling.
Changelog entry
- Added restoreAdditionalCommandArgs to.barmanObjectStore.data for in-tree Barman Cloud recoveries Release
- Set --no-data-checksums when dataChecksums is false on PostgreSQL 18+ Pull request #11488
- Fixed DatabaseDeadlockConflicts and DatabaseLockConflicts alerts latching forever Pull request #11510
- Fixed inheritedMetadata labels being discarded on PVC reconciliation Pull request #11499
- Fixed Pooler and DatabaseRole recreating owned resources after deletion Pull request #11359
- Fixed replica cluster designated primary sort order Pull request #11494
- Reverted restore certificate-wait deadlock fix that did not resolve underlying issue Pull request #11548
V1.30.1 and v1.29.3 released. v1.29 is now end-of-life. Fixes include Barman Cloud recovery args, PVC label handling, monitoring alert latching, and replica cluster sort order.
CloudNativePG v1.30.1 and v1.29.3 are now available. v1.29 reaches end-of-life; users should upgrade. This week's releases include enhanced Barman Cloud recovery parameter forwarding, fixes for monitoring alerts that latch forever, corrected replica cluster designated primary sorting, and improved PostgreSQL 18 compatibility with data checksums handling.
Week of September 14, 2026
What shipped
- Fixed the controller from stalling or reverting an in-progress failover by checking whether the failover could complete instead of requeuing blindly, and by not mistaking a pending marker for a missing pod. Pull request #11336
- Fixed a deadlock during multi-instance cluster restore from orphan PVCs where a replica's bootstrap would hang waiting for certificates that the restore gate prevented from being set. Pull request #11492
- Fixed failover to immediately shut down an unreachable old primary instead of waiting for checkpoint and fast-shutdown attempts that would never complete, so it can rejoin as a replica. Pull request #11347
- Fixed fencing to only take out a single instance instead of preventing the entire cluster from electing a new primary or recreating deleted pods. Pull request #11274
- Fixed a window during primary restart or reschedule where PostgreSQL starts before acquiring the primary lease, which could allow multiple primaries. Pull request #11356
- Fixed plugin status reporting to include the PostgresCapabilities field that was being dropped during updates. Pull request #11447
- Made the disk-space e2e test deterministic by stopping the postmaster once the disk is full, preventing timeouts from harmless temporary file writes. Pull request #11490
- Fixed pgbouncer SHOW POOLS parsing to bind columns by name instead of relying on column count, avoiding failures when future pgbouncer releases add new columns. Pull request #11464
- Fixed preflight CI to create image-pull secrets in the randomized namespace that preflight v1.20.0+ now uses. Pull request #11472
- Fixed Rook CRD race on AKS by waiting for CRD registration before applying custom resources. Pull request #11479
Why it matters
This week addresses critical failover and recovery scenarios that can leave clusters unavailable or stuck in deadlock. Fixes to fencing, primary lease acquisition, and restore operations ensure the cluster can reliably handle failures and maintenance events. These changes make the controller more resilient when instances are unreachable or the cluster needs to reorganize.
Changelog entry
- Fixed controller avoiding stalling or reverting an in-progress failover Pull request #11336
- Fixed certificate-wait deadlock in orphan-PVC restore Pull request #11492
- Fixed demotion of unreachable old primary immediately during failover Pull request #11347
- Fixed cluster recovery while an instance is fenced Pull request #11274
- Fixed PostgreSQL start to gate on holding the primary lease Pull request #11356
- Fixed plugin status reporting of PostgreSQL capabilities Pull request #11447
- Made disk-space e2e test deterministic Pull request #11490
- Fixed pgbouncer SHOW POOLS column binding by name Pull request #11464
- Fixed preflight image-pull secret creation in randomized namespace Pull request #11472
- Fixed Rook CRD race on AKS Pull request #11479
- Fixed incorrect field name in
wal_archivingdocumentation Pull request #11477
This week: failover no longer stalls, fencing affects only the target instance, restore deadlocks are fixed, and primary startup is safer. Critical reliability improvements for PostgreSQL on Kubernetes.
This week we fixed several critical reliability issues in CloudNativePG: failover operations no longer stall or revert, fencing now correctly isolates only the target instance, restore from orphan PVCs no longer deadlocks, and primary startups now properly acquire the lease first. These changes ensure clusters can reliably recover from failures and maintenance events.