Release date: Jul 25, 2025

In memory of DJ Walker-Morgan.

Important Changes

CloudNativePG is moving toward a plugin-based, backup and recovery agnostic architecture (initiated in 1.26.0 with Barman Cloud). As part of this transition, the following fields in the .status section of the Cluster resource are now deprecated:

• firstRecoverabilityPoint
• firstRecoverabilityPointByMethod
• lastSuccessfulBackup
• lastSuccessfulBackupByMethod
• lastFailedBackup

Additionally, the following Prometheus metrics are deprecated:

• cnpg_collector_first_recoverability_point
• cnpg_collector_last_available_backup_timestamp
• cnpg_collector_last_failed_backup_timestamp

These fields and metrics will no longer update when using plugin-based backups (e.g., Barman Cloud via CNPG-I). They remain functional for users still using in-core Barman Cloud and volume snapshot backups.

Note: We, as maintainers, are sorry for any inconvenience caused by not highlighting this change during the 1.26.0 release. As we transition to a plugin-based backup and recovery architecture, we encourage you to test your chosen plugin thoroughly in a staging environment before moving to production to ensure your workflows and observability integration continue to meet your needs. Thank you for your understanding and for working with us as CloudNativePG evolves to provide a more modular and robust experience.

Changes

• Removed 386 and ARM (v5/v6/v7) architectures from the cnpg plugin build matrix, reducing the number of published binaries (#7648).

Enhancements

• Improved validation of shared_buffers by correctly considering HugePages settings, ensuring accurate memory configuration checks (#7864).

• Set oom_score_adj for PostgreSQL worker processes to improve prioritization during out-of-memory situations (#7891).

• Added fqdn-uri and fqdn-jdbc-uri fields in user secrets to simplify application connection string management and align with DNS-based connection best practices (#7852).

• Added the systemID field and related condition in the Cluster status to track the PostgreSQL system identifier. (#7717).

Fixes

• Added a mutex in the connection pooler to protect concurrent access to the connections map, improving stability in high-concurrency environments (#7804).

• Fixed replica cluster instance ordering by correctly detecting the designated primary, improving replica cluster stability and switchover operations (#8108).

• Added support for reconciling VolumeAttributesClass for PVCs, enhancing storage compatibility and lifecycle management (#7885).

• Made the internal webserver routines non-blocking to improve responsiveness under load (#8071).

• Fixed an issue where the ensureReplicationClientLeafCertificate error did not display the correct secretName in the not found message (#8086).

• Prevented invalid ALTER SUBSCRIPTION statements by updating only PostgreSQL‑supported parameters; unsupported options like copy_data are ignored to avoid reconciliation failures (7844).

• Fixed an issue where the bootstrap-controller in the connection pooler did not apply resources settings correctly (#7922).

• Ensured online backups fail cleanly if the targetPod becomes unhealthy during backup, preventing partial or misleading backups (#7944).

• Ensured the Backup resource status is set properly after a failure, improving observability and scripting reliability (#7898).

• Improved liveness probe handling to avoid unnecessary timeouts when they are not required (#7902).