The CloudNativePG Community has announced version 1.17.0, a new minor
release of the CloudNativePG Operator, which introduces the possibility to
create a new PostgreSQL cluster with a dedicated volume for Write-Ahead Log
(WAL) files. Separating I/O workloads of database (PGDATA) and WAL files
improves vertical scalability of PostgreSQL clusters, among the others.
In this version, a new command, destroy, has been added to the cnpg plugin
for kubectl to help remove an instance and the associated persistent volume
claims from an existing cluster.
Two new labels, cnpg.io/instanceName and cnpg.io/podRole, are now managed
by the operator on all persistent volume claims that belong to a cluster.
Some minor bugs have been fixed, in particular in the in-place operator upgrade process.
New patch releases are available for all the supported versions, including 1.16.2 and 1.15.4.
With the release of 1.17.0, the 1.15.x minor version will be end of life from 6 October, 2022.
We encourage you to update the operator at your earliest possible convenience.
For a complete list of changes, please refer to:
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.