The CloudNativePG Community has released version 1.16.0, a new minor version of the CloudNativePG Operator, which introduces two important capabilities:
We are starting our policy from this release to support the last two minor versions of CloudNativePG. This means that the 1.15 minor version will be supported by the Community for another month after 1.17.0 is released. We are today releasing the patch version 1.15.2 for the 1.15.x branch. For details, please refer to the "Supported releases" section.
Version 1.16.0 also introduces a few enhancements in the backup and recovery area, as well as in the fencing mechanism, by removing the existing limitation that disables failover when one or more instances are fenced. It adds support for Kubernetes 1.24 and provides several bug fixes.
Such fixes have been back-ported to the 1.15 release branch and included in the 1.15.2 version.
We strongly encourage you to update the operator at your earliest possible convenience. You can either jump directly to 1.16.0 and benefit from all the new capabilities and enhancements introduced, or stay in the 1.15 minor release by moving to 1.15.2 with bug fixes only.
CloudNativePG is an open source Kubernetes Operator for PostgreSQL workloads that orchestrates the full life cycle of a PostgreSQL cluster, from bootstrapping and configuration, through high availability and connection routing, to backups and disaster recovery. CloudNativePG relies on PostgreSQL’s native streaming replication to distribute data across pods, nodes, and zones, using standard Kubernetes patterns. Replicas can be scaled up and down in a Kubernetes native manner, and the operator automatically and safely reconfigure replication as appropriate.
CloudNativePG is the first PostgreSQL Operator to pursue the whole graduation process with the Cloud Native Computing Foundation (CNCF) by submitting the request to join the Sandbox in April 2022. CloudNativePG is a project originally created and supported by EDB.