CloudNativePG v1.29.0-rc1
Release Notes
Release date: Mar 13, 2026
Important changes
- Updated the deprecation notice for native (in-tree) Barman Cloud support to reflect that it will now be removed in CloudNativePG 1.30.0, rather than 1.29.0. Users are still encouraged to migrate to the Barman Cloud Plugin. (#10167)
Features
-
PostgreSQL extensions in image catalogs: extended the
ImageCatalogfunctionality to support PostgreSQL extensions. This allows users to define and manage extension-specific images within a catalog, simplifying the deployment of customized PostgreSQL builds. (#9781) -
Dynamic network access control via pod selectors: introduced the declarative definition of
podSelectorRefsto managepg_hba.confrules dynamically. By using label selectors to identify client pods, the operator automatically resolves their ephemeral IP addresses and updates the PostgreSQL host-based authentication rules accordingly. This ensures that only authorized workloads in the same namespace can connect to the database, eliminating the need for manual IP management or static CIDR ranges. (#10148) -
Shared
ServiceAccountsupport: added an optionalserviceAccountNamefield to bothClusterandPoolerspecifications. This allows multiple resources to share a pre-existing ServiceAccount, facilitating one-time IAM configurations (such as AWS IRSA, GCP Workload Identity, or Azure Workload Identity) across all clusters and poolers. Contributed by @bozkayasalihx. (#9287)
Enhancements
-
Improved the
PoolerCRD with support for granular configuration of TLS cipher suites and minimum/maximum TLS versions. This enables administrators to meet strict security compliance requirements for pooler-to-client and pooler-to-server connections. Contributed by @alex1989hu. (#9571) -
Improved the reliability of major upgrades by setting
BackoffLimit=0on the upgrade job, preventing unnecessary retries of a failedpg_upgrade. The operator now automatically deletes the failed job when a user reverts the container image, allowing the cluster to restart gracefully on the original version. (#10104) -
Improved the operator's observability by emitting native Kubernetes events during key phases of the reconciliation loop. This provides much better visibility into the operator's decision-making process and the lifecycle of managed resources directly through
kubectl get events. (#10040) -
Extended support for the
cnpg.io/reconciliationDisabledannotation on Backup resources. This allows administrators to temporarily freeze the operator's reconciliation logic for specific backup objects. Contributed by @GabriFedi97. (#10020) -
Added a
bin_pathfield to thepostgresql.extensionsstanza, as well as inImageCatalogandClusterImageCatalogresources. This allows extensions to specify directory paths for external binaries, which are automatically appended to thePATHenvironment variable of the Postgres process. (#10250) -
Implemented a finalizer for plugins to ensure that resources managed by a plugin are gracefully cleaned up when the corresponding service is deleted. (#9560)
-
Enhanced the security and reliability of role management by verifying the primary status of an instance before each reconciliation cycle. (#9971)
-
The operator now honors the
primaryUpdateMethodwhen adding new PVCs to a cluster, ensuring that the rollout strategy (e.g., switchover vs. restart) is respected during storage expansion or additions. (#9720) -
Refined the
alpha.cnpg.io/unrecoverableannotation logic to allow it to function even on pods that have not yet reached theReadystate, facilitating the recovery of stuck instances. (#9968) -
Introduced a "Terminal Error" phase for backups that encounter unrecoverable issues (such as invalid credentials or non-existent cloud buckets). This ensures the operator stops retrying doomed operations, preventing resource exhaustion and providing immediate, clear feedback in the status. (#9353)
-
Improved monitoring of long-running backups by introducing
reconciliationStartedAtandreconciliationTerminatedAtfields to theBackupstatus. This change separates the operator's internal lifecycle from the actual backup tool's execution timing (startedAt/stoppedAt), allowing users to track when the operator begins processing a request. (#9351) -
Added a
Pendingphase to theBackupstatus to explicitly indicate when a backup is queued and waiting for an available worker or instance availability. (#9364)
Security and Supply Chain
- Security best practices integration: integrated the OpenSSF baseline scanner and added a
SECURITY-INSIGHTS.yamlfile to the repository to align with industry-standard security reporting. (#10054, [#10062](https:
[truncated]