| title | CloudNativePG 1.27.0 RC1 Released! | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| date | 2025-07-29 | ||||||||
| draft | false | ||||||||
| author | fdrees | ||||||||
| image |
|
||||||||
| tags |
|
||||||||
| summary | The CloudNativePG community is excited to announce the first release candidate of CloudNativePG 1.27! This preview introduces features like the dynamic loading of PostgreSQL extensions, and the automatic synchronization of logical decoding slots across high-availability clusters. Join us in testing these updates to shape the final release. |
The CloudNativePG Community is thrilled to announce the first release candidate of CloudNativePG 1.27! This preview release provides an opportunity to explore new features and enhancements before the final version is officially launched. While refinements may still occur, here’s a look at what’s new.
We introduced the .spec.postgresql.extensions field to support mounting
PostgreSQL extensions—packaged as OCI-compliant container images—as read-only,
immutable volumes within instance pods. This enables dynamic extension
management without the need to rebuild base images.
We added the synchronizeLogicalDecoding field under
spec.replicationSlots.highAvailability to enable automatic synchronization
of logical decoding slots across high-availability clusters. This ensures
seamless continuity for logical replication subscribers after a publisher
failover.
The liveness pinger, introduced as an experimental feature in 1.26, has
been promoted to stable. A new .spec.probes.liveness.isolationCheck section
enables primary isolation checks in the liveness probe by default, improving
detection and handling of primary connectivity issues in Kubernetes environments.
Explore other improvements in this release, including:
- An opt-in, experimental feature that enables quorum-based failover to improve safety and data durability during failover events.
- Added support for user maps for predefined users such as
streaming_replica, allowing the use of self-managed client certificates with different Common Names in environments with strict policies or shared CAs. - Added a new
PhaseFailurePluginphase in theCluster statusto improve observability of plugin-related failures.
Dive into the full details in the release notes for 1.27 RC1.
The stability of each CloudNativePG release relies on the community’s engagement. Testing your workloads with this release candidate helps identify bugs and regressions early.
- View the open issues for the 1.27 release.
- Report bugs directly on GitHub.
CloudNativePG 1.27 RC1 is the first in a series of release candidates. Additional release candidates may follow as needed before the final release, currently planned for the end of August.
Connect with our community on your preferred platform!
Thank you for your continued support of CloudNativePG. Your contributions help us advance the Kubernetes-native PostgreSQL experience.