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 1uJSvS-0001L9-Dv for pgsql-announce@arkaria.postgresql.org; Mon, 26 May 2025 08:11:15 +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 1uJSvP-003vA5-QV for pgsql-announce@arkaria.postgresql.org; Mon, 26 May 2025 08:11:11 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uJSvO-003v8y-E6 for pgsql-announce@lists.postgresql.org; Mon, 26 May 2025 08:11:10 +0000 Received: from mahout.postgresql.org ([2001:4800:3e1:1::227]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uJSvK-0009tZ-1p for pgsql-announce@lists.postgresql.org; Mon, 26 May 2025 08:11:09 +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=wxu4XLd4uvfB3RQcSZFNf2/l9okruyChCVm3wVHObKg=; b=xRqYIYz2mevYq+f4HSVpwhkCf+ ZnKT6zZXBjLsKvb4WpAtea/AQIpc9nEoO97PyU5jHccOaYpLOoEup5UnnYaLc1UvWB8TOnUexOmNa stpwo8wIncXrlKHnfIwWscxNSkthUyjmWRuvLEiJRps71t5pvAYGr1wGLNWLrx0OOFnTLrlxRKdAX PRXmv0U8JkC74EXem3TvQvjQUGAd9LE4VVh7hoB2NivYPmTWGFoO/2M/cY1U9L0/CCBHf0SC3WMqE TuNUeFM01lU+CxrM1b9A9gDdii63bLdO67sFBjhNBONZFrST0fn22QUd2maoFPfW9446qZkNW11Sp PjzAGtzg==; Received: from wrigleys.postgresql.org ([217.196.149.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 1uJSvJ-00B3yW-I3 for pgsql-announce@lists.postgresql.org; Mon, 26 May 2025 08:11: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 1uJSvI-00FoZL-2P for pgsql-announce@lists.postgresql.org; Mon, 26 May 2025 08:11:03 +0000 Content-Type: multipart/mixed; boundary="===============7122445576014024518==" MIME-Version: 1.0 Subject: CloudNativePG 1.26.0 and 1.25.2 Released! To: PostgreSQL Announce From: The CloudNativePG Contributors via PostgreSQL Announce Reply-To: gabriele.bartolini@gmail.com Date: Mon, 26 May 2025 08:10:28 +0000 Message-ID: <174824702807.790.8962633422478009117@wrigleys.postgresql.org> X-Auto-Response-Suppress: All Auto-Submitted: auto-generated X-pglister-tags: related X-pglister-tagsig: d94cde73d3cbaf93488a3c1fd0c8596df4a839018050b6c50aeac37b13798fbc List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --===============7122445576014024518== Content-Type: multipart/alternative; boundary="===============3164492194456143555==" MIME-Version: 1.0 --===============3164492194456143555== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable The **CloudNativePG Community** is pleased to announce the release of: - CloudNativePG 1.26.0, featuring major enhancements and new capabilities - CloudNativePG 1.25.2, a maintenance update for the 1.25.x series - CloudNativePG 1.24.4, the final patch for the now unsupported 1.24.x seri= es This is our first release since CloudNativePG officially entered the [CNCF Sandbox](https://www.cncf.io/sandbox-projects/), a major milestone th= at reinforces our commitment to sustainable, community-driven innovation. ## What=E2=80=99s New in CloudNativePG 1.26.0? ### Declarative Offline In-Place Major Upgrades of PostgreSQL You can now declaratively trigger [offline in-place major upgrades](https://cloudnative-pg.io/documentation/1= .26/postgres_upgrades/) of PostgreSQL by simply updating the container image to a newer major versi= on. The cluster shuts down safely, and `pg_upgrade` performs the upgrade, ensur= ing consistency. This long-awaited feature simplifies major upgrades while maintaining declarative workflows. ### Enhanced Startup and Readiness Probes for Replicas We've enhanced [startup and readiness probes](https://cloudnative-pg.io/doc= umentation/1.26/instance_manager/) for replicas, enabling both startup and readiness to be gated by replication lag. This means you can restrict promotion to only lag-free, synchronous replicas=E2=80=94greatly improving your high availability posture. ### Declarative Management of Extensions and Schemas The `Database` resource now supports the declarative creation of: - [PostgreSQL extensions](https://cloudnative-pg.io/documentation/1.26/decl= arative_database_management/#managing-extensions-in-a-database) - [`SCHEMA` objects](https://cloudnative-pg.io/documentation/1.26/declarati= ve_database_management/#managing-schemas-in-a-database) This makes it easier to manage consistent database configurations across environments. ## Important Changes ### Barman Cloud Deprecation Begins With the 1.26 release, the **deprecation period** for in-tree Barman Cloud support officially begins. While it remains fully functional in 1.26, we **strongly encourage** users to begin planning the migration to the [Barman Cloud Plugin](https://cloudnative-pg.io/plugin-barman-cloud/) as early as possible and to adopt it for all new deployments. To help with this, we=E2=80=99ve published a comprehensive [migration guide](https://cloudnative-pg.io/plugin-barman-cloud/docs/migrat= ion/). In CloudNativePG 1.28, Barman Cloud will be fully removed from CloudNativeP= G=E2=80=99s core. You have until then to complete your migration. This marks a significant milestone in CloudNativePG=E2=80=99s evolution=E2= =80=94the culmination of a multi-year effort that introduced CNPG-I, our extensible plugin interf= ace. It is a crucial step toward making CloudNativePG a backup-agnostic solution while enabling leaner operand images by removing the need to bundle Barman Cloud directly. It also paves the way for future plugin support for volume snapshot backups and restores. ### Declarative Hibernation Support for the Plugin The `hibernate` command of the plugin now leverages the declarative hiberna= tion capability. Instead of executing an imperative hibernation process that destroyed replica PVCs, it will now annotate the cluster, aligning with CloudNativePG=E2=80=99s declarative approach. ## Additional Enhancements in 1.26.0 Explore other improvements in this release, including: - A new annotation to enable/disable webhook validation. - A configuration option to set the TCP timeout for replicas, improving failover recovery speed. - Integration with autoscalers like Karpenter for better node drain managem= ent. - Experimental enhancement to the liveness probe to detect network isolatio= n on primaries=E2=80=94allowing self-demotion in split-brain scenarios. Dive into the full details in the [release notes](https://cloudnative-pg.io/documentation/1.26/release_notes/= v1.26/). ## Upgrade Guidance We recommend all users: - Upgrade to 1.26.0 for the latest features and long-term stability. - If you're on 1.25.x, upgrade to 1.25.2 to stay up to date with fixes and improvements. Support for the 1.25.x series continues until **22 August 2025**. Refer to the [upgrade instructions](https://cloudnative-pg.io/documentation= /1.26/installation_upgrade/#upgrades) for a smooth transition. ## Get Involved with the Community CloudNativePG is a **vendor-neutral, open-source** project backed by a vibr= ant community of PostgreSQL and Kubernetes enthusiasts. [Join us](https://github.com/cloudnative-pg/cloudnative-pg?tab=3Dreadme-ov-= file#communications) to help shape the future of cloud-native Postgres! Thank you for your continued support! Upgrade today and discover how CloudNativePG can elevate your PostgreSQL experience to new heights. ## About CloudNativePG [CloudNativePG](https://cloudnative-pg.io) is an open-source Kubernetes Operator specifically designed for PostgreSQL workloads. It manages the ent= ire lifecycle of a PostgreSQL cluster, including bootstrapping, configuration, = high availability, connection routing, and comprehensive backup and disaster recovery mechanisms. By leveraging PostgreSQL's native streaming replicatio= n, CloudNativePG efficiently distributes data across pods, nodes, and zones us= ing standard Kubernetes patterns, enabling seamless scaling of replicas in a Kubernetes-native manner. Originally developed and supported by [EDB](https://www.enterprisedb.com/), CloudNativePG is a [CNCF Sandbox project](https://www.cncf.io/projects/cloudnativepg/) and the sole PostgreSQL operator in this category. --===============3164492194456143555== Content-Type: text/html; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable CloudNativePG 1.26.0 and 1.25.2 Released!
 

CloudNativePG 1.26.0 and 1.25.2 Released!

The CloudNativePG Community is pleased to announce the release of:

  • CloudNativePG 1= .26.0, featuring major enhancements and new capabilities
  • CloudNativePG 1= .25.2, a maintenance update for the 1.25.x series
  • CloudNativePG 1= .24.4, the final patch for the now unsupported 1.24.x series

This is our first release since CloudNative= PG officially entered the CNCF Sandbox, a major milestone that reinforces our commitment to sustainable, community-driven innovation.

What=E2=80=99s New in CloudNati= vePG 1.26.0?

Declarative Offline In-Place Ma= jor Upgrades of PostgreSQL

You can now declaratively trigger offline in-place majo= r upgrades of PostgreSQL by simply updating the container image to a newer major versi= on. The cluster shuts down safely, and pg_upgrade performs the upg= rade, ensuring consistency. This long-awaited feature simplifies major upgrades while maintaining declarative workflows.

Enhanced Startup and Readiness = Probes for Replicas

We've enhanced startup and readiness probes for replicas, enabling both startup and readiness to be gated by replication lag. This means you can restrict promotion to only lag-free, synchronous replicas=E2=80=94greatly improving your high availability posture.

Declarative Management of Exten= sions and Schemas

The Database resource now supp= orts the declarative creation of:

This makes it easier to manage consistent d= atabase configurations across environments.

Important Changes

Barman Cloud Deprecation Begins=

With the 1.26 release, the deprecat= ion period for in-tree Barman Cloud support officially begins. While it remains fully functional in 1.26, we strongly encourage users to begin planning the migration t= o the Barman Cloud Plugin as early as possible and to adopt it for all new deployments. To help with this, we=E2=80=99ve published a comprehensive migration guide.

In CloudNativePG 1.28, Barman Cloud will be= fully removed from CloudNativePG=E2=80=99s core. You have until then to complete your migration.

This marks a significant milestone in Cloud= NativePG=E2=80=99s evolution=E2=80=94the culmination of a multi-year effort that introduced CNPG-I, our extensible plugin interf= ace. It is a crucial step toward making CloudNativePG a backup-agnostic solution while enabling leaner operand images by removing the need to bundle Barman Cloud directly. It also paves the way for future plugin support for volume snapshot backups and restores.

Declarative Hibernation Support= for the Plugin

The hibernate command of the p= lugin now leverages the declarative hibernation capability. Instead of executing an imperative hibernation process that destroyed replica PVCs, it will now annotate the cluster, aligning with CloudNativePG=E2=80=99s declarative approach.

Additional Enhancements in 1.26= .0

Explore other improvements in this release,= including:

  • A new annotatio= n to enable/disable webhook validation.
  • A configuration= option to set the TCP timeout for replicas, improving failover recovery speed.
  • Integration wit= h autoscalers like Karpenter for better node drain management.
  • Experimental en= hancement to the liveness probe to detect network isolation on primaries=E2=80=94allowing self-demotion in split-brain scenarios.

Dive into the full details in the release notes.<= /p>

Upgrade Guidance

We recommend all users:

  • Upgrade to 1.26= .0 for the latest features and long-term stability.
  • If you're on 1.= 25.x, upgrade to 1.25.2 to stay up to date with fixes and improvements.

Support for the 1.25.x series continues unt= il 22 August 2025.

Refer to the upgrade instructions for a smooth transition.

Get Involved with the Community=

CloudNativePG is a vendor-neutral, = open-source project backed by a vibrant community of PostgreSQL and Kubernetes enthusiasts. = Join us to help shape the future of cloud-native Postgres!

Thank you for your continued support! Upgra= de today and discover how CloudNativePG can elevate your PostgreSQL experience to new heights.

About CloudNativePG

CloudNativePG is an ope= n-source Kubernetes Operator specifically designed for PostgreSQL workloads. It manages the ent= ire lifecycle of a PostgreSQL cluster, including bootstrapping, configuration, = high availability, connection routing, and comprehensive backup and disaster recovery mechanisms. By leveraging PostgreSQL's native streaming replicatio= n, CloudNativePG efficiently distributes data across pods, nodes, and zones us= ing standard Kubernetes patterns, enabling seamless scaling of replicas in a Kubernetes-native manner. Originally developed and supported by EDB, CloudNativePG is a CNCF Sandbox project and the sole PostgreSQL operator in this category.
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/.
 
--===============3164492194456143555==-- --===============7122445576014024518==--