Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vIHGO-00275k-Aq for pgsql-announce@arkaria.postgresql.org; Mon, 10 Nov 2025 02:04:12 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1vIHGL-00CYKw-OJ for pgsql-announce@arkaria.postgresql.org; Mon, 10 Nov 2025 02:04:09 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vIHGK-00CYJy-MH for pgsql-announce@lists.postgresql.org; Mon, 10 Nov 2025 02:04:08 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1vIHGI-006IUT-0R for pgsql-announce@lists.postgresql.org; Mon, 10 Nov 2025 02:04:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=postgresql.org; s=20171124; h=Message-ID:Date:Reply-To:From:To:Subject: MIME-Version:Content-Type:Sender:Cc:Content-Transfer-Encoding:Content-ID: Content-Description:In-Reply-To:References; bh=gypTDatqnbv4jWzpyPxkn4xRT6vJFng9pk3WV2gbS9M=; b=iKv6qn0gU0wSv2E+P3N56Lrfs5 Nn+dsRlnB4YgEW/GYaz7A2h0FQNJ+8s1hTEmVBE+kcPjmlEGxB33cA0XV+L0Maz+XR5mbcKv/5nXi +YIyg7m7DCr0OjJ3CHEdvY1sSg48tvX2vihj42bBgkiNsv939BlsxQxn1R8bmIlbgEqhgRc+rNedR TwiQi1nixzxde/PMXWsQY3lAHDm8nRQl7MEyjxlByO5MFOAdexB7osksSRkfGiOpCm2ZfEQ7Izjcj Yr5e8Ckq8FDNxkKF1U2iCZMsik84xRNbDUHRs7ymm1ZyzwH2nVj8VtEJ86b02KwgKgEDNwxWVwtoy ynQhkoRA==; Received: from wrigleys.postgresql.org ([2a02:16a8:dc51::60]) by mahout.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1vIHGH-00CMWd-9a for pgsql-announce@lists.postgresql.org; Mon, 10 Nov 2025 02:04:05 +0000 Received: from localhost ([127.0.0.1] helo=wrigleys.postgresql.org) by wrigleys.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vIHGE-003hLg-3A for pgsql-announce@lists.postgresql.org; Mon, 10 Nov 2025 02:04:03 +0000 Content-Type: multipart/mixed; boundary="===============5314115875289204903==" MIME-Version: 1.0 Subject: CloudNativePG 1.28.0 RC1 Released! To: PostgreSQL Announce From: The CloudNativePG Contributors via PostgreSQL Announce Reply-To: gabriele.bartolini@gmail.com Date: Mon, 10 Nov 2025 02:03:23 +0000 Message-ID: <176274020395.761.12955899444590958934@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: 7dc880695ce86bdfa666314566c0d5ae1b25a591941c73bce4a39fb914a2bc2e List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============5314115875289204903== Content-Type: multipart/alternative; boundary="===============4168312170311477537==" MIME-Version: 1.0 --===============4168312170311477537== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable The CloudNativePG Community is thrilled to announce the first release candi= date of CloudNativePG 1.28! This preview release provides an opportunity to= explore new features and enhancements before the final version is official= ly launched. While refinements may still occur, here=E2=80=99s a look at wh= at=E2=80=99s new. ## Key Features ### Quorum-Based Failover Promoted to Stable The quorum-based failover feature, introduced experimentally in 1.27, has b= een promoted to a stable API. This data-driven failover mechanism is now co= nfigured via the `spec.postgresql.synchronous.failoverQuorum` field, gradua= ting from the previous `alpha.cnpg.io/failoverQuorum` annotation. This enha= nces [failover safety and data durability](/documentation/preview/failover/= #quorum-based-failover) for high-availability clusters. ### Declarative Foreign Data Management We introduced comprehensive declarative management for Foreign Data Wrapper= s (FDW) by extending the `Database` CRD. This feature adds the `.spec.fdws`= and `.spec.servers` fields, allowing you to [manage FDW extensions and for= eign servers](/documentation/preview/database_crd/#foreign-data-wrappers) d= irectly from the `Database` resource. This work was implemented by Ying Zhu ([@EdwinaZhu](https://github.com/Edwi= naZhu)) as part of the [LFX Mentorship Program 2025 Term 2](https://mentors= hip.lfx.linuxfoundation.org/project/53fa853e-b5fa-4d68-be71-f005c75aea89). ## There=E2=80=99s More=E2=80=A6 Explore other improvements in this release, including: - Introduced granular control over [fine-grained security contexts](/docume= ntation/preview/cluster_spec/#security-contexts), allowing `securityConte= xt` at the pod level and `containerSecurityContext` for individual containe= rs. - Allowed providing [custom TLS for PgBouncer](/documentation/preview/poole= r_spec/#custom-tls) for both client-to-pooler and pooler-to-server connecti= ons, taking precedence over operator-generated certificates. - Added optional [TLS support for the operator's metrics server](/documenta= tion/preview/operator_config/#metrics-tls), enabled via the `METRICS_CERT_D= IR` environment variable. - Enabled the `cnpg report operator` command to work with [minimal, least-p= rivileged access](/documentation/preview/cnpg_plugin/#report), gracefully h= andling permission errors. - Introduced the `alpha.cnpg.io/unrecoverable=3Dtrue` annotation to [automa= tically delete and recreate a replica pod](/documentation/preview/instance_= management/#unrecoverable-replicas) and its PVCs. Dive into the full details in the [release notes for 1.28 RC1](https://clou= dnative-pg.io/documentation/preview/release_notes/v1.28/). ## Testing The stability of each CloudNativePG release relies on the community=E2=80= =99s engagement. Testing your workloads with this release candidate helps i= dentify bugs and regressions early. - View the [open issues for the 1.28 release](https://github.com/cloudnativ= e-pg/cloudnative-pg/milestone/29). - Report bugs directly on [GitHub](https://github.com/cloudnative-pg/cloudn= ative-pg/issues/new/choose). ## Release Timeline CloudNativePG 1.28 RC1 is the first in a series of release candidates. Addi= tional release candidates may follow as needed before the final release, cu= rrently planned for the second half of November. # Join the Community [Connect with our community on your preferred platform](https://github.com/= cloudnative-pg/cloudnative-pg?tab=3Dreadme-ov-file#communications)! Thank you for your continued support of CloudNativePG. Your contributions h= elp us advance the Kubernetes-native PostgreSQL experience. --===============4168312170311477537== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable CloudNativePG 1.28.0 RC1 Released!
 

CloudNativePG 1.28.0 RC1 Released!

The CloudNativePG Community is thrilled to = announce the first release candidate of CloudNativePG 1.28! This preview re= lease provides an opportunity to explore new features and enhancements befo= re the final version is officially launched. While refinements may still oc= cur, here=E2=80=99s a look at what=E2=80=99s new.

Key Features

Quorum-Based Failover Promoted = to Stable

The quorum-based failover feature, introduc= ed experimentally in 1.27, has been promoted to a stable API. This data-dri= ven failover mechanism is now configured via the spec.postgresql.sync= hronous.failoverQuorum field, graduating from the previous alp= ha.cnpg.io/failoverQuorum annotation. This enhances failover safety and data durability= for high-availability clusters.

Declarative Foreign Data Manage= ment

We introduced comprehensive declarative man= agement for Foreign Data Wrappers (FDW) by extending the Database CRD. This feature adds the .spec.fdws and .spec.serv= ers fields, allowing you to manage FDW extensions and foreign servers directly from= the Database resource.

This work was implemented by Ying Zhu (@EdwinaZhu) as part of the LFX Mentorship Program 202= 5 Term 2.

There=E2=80=99s More=E2=80=A6

Explore other improvements in this release,= including:

Dive into the full details in the release notes for 1.28 = RC1.

Testing

The stability of each CloudNativePG release= relies on the community=E2=80=99s engagement. Testing your workloads with = this release candidate helps identify bugs and regressions early.

Release Timeline

CloudNativePG 1.28 RC1 is the first in a se= ries of release candidates. Additional release candidates may follow as nee= ded before the final release, currently planned for the second half of Nove= mber.

Join the Community

Connect with our community on your preferre= d platform!

Thank you for your continued support of Clo= udNativePG. Your contributions help us advance the Kubernetes-native Postgr= eSQL experience.
This email was sent to you from The CloudNativePG Contributors. It was deli= vered on their behalf by the PostgreSQL project. Any questions about the content of the message shou= ld be sent to The CloudNativePG Contributors.

You were sent this email as a subscriber of the pgsql-announce mai= linglist, for the content tag Related Open Source. To unsubscribe from further emails, or change which emails you want to receive, please click th= e personal unsubscribe link that you can find in the headers of this email, or visit https://lists.postgresql.org/unsubscribe/.
 
--===============4168312170311477537==-- --===============5314115875289204903==--