The CloudNativePG community is releasing CloudNativePG 1.30.2, a maintenance update for the 1.30 series and the first release since the project became a CNCF Incubating project.
We had planned to ship these fixes together with 1.31.0. Given the security relevance of the PostgreSQL 18.7 release, though, we decided to make an exception and release 1.30.2 on its own, ahead of the new minor version.
Three changes are worth knowing about before you upgrade to 1.30.2:
18.7-system-trixie), which
fixes several CVEs
(#11833). It
only applies to new clusters that don’t set an image. To get the fixes on
existing clusters, update them to 18.7, 17.12, 16.16 or 15.20 by changing
imageName or the ImageCatalog, after reading the
PostgreSQL 18.7 announcement.delete permission on leases. If you
manage RBAC manually, you must add it
(#11609).The release also improves the robustness of replicas and switchovers. Standbys
that stay on the WAL archive can now retry streaming replication, so they no
longer miss out on synchronous replication
(#11868), and
replicas created from an online volume snapshot now honor the backup_label
and tablespace_map stored in it
(#11847).
S3-compatible object stores gain support for server-side encryption with
customer-provided keys (SSE-C) through the new sseCustomerKey field
(#11711).
There are also several other fixes and dependency updates for Go
vulnerabilities, all listed in the release notes below.
Follow the upgrade instructions to upgrade your clusters.
For the complete list of changes, see the release notes:
Join us to help shape the future of cloud-native Postgres!
CloudNativePG is now a CNCF Incubating project. Read the CNCF announcement to learn more. This milestone follows the evolution of our governance model and our contributor ladder, and it belongs to everyone in the community who contributed along the way.
If you’re using CloudNativePG in production, consider adding your organization as an adopter to support the project.
We’d also like to thank everyone who contributed a pull request to this release, in particular @kabbydriver, @ichibahn, @ardentperf and @valeriodelsarto. The number of community contributions keeps growing, which is great to see.
Thank you for your continued support!