The CloudNativePG Community is thrilled to announce the first release candidate of CloudNativePG 1.29! This preview release provides an opportunity to explore new features and enhancements before the final version is officially launched. While refinements may still occur, here’s a look at what’s new.
The most significant architectural advancement in 1.29 is the integration of
Image Catalogs
with a new dedicated ecosystem for PostgreSQL extensions. By leveraging the
postgres-extensions-containers
project and its official extension images and catalogs,
CloudNativePG now provides a structured way to distribute and manage
extension-specific images.
This feature allows you to define these extensions within a catalog, ensuring that the database engine and its modules are version-aligned, secure, and treated as a single cohesive unit. This approach centralizes your image supply chain and removes the need for users to manually build and maintain complex custom PostgreSQL images.
We’ve introduced a major enhancement to how PostgreSQL network security is
handled in Kubernetes. By using the new
podSelectorRefs
field, you can now
define pg_hba.conf rules that dynamically resolve the IP addresses of client
pods based on label selectors. This ensures that only authorized workloads in
the same namespace can connect to your database, eliminating the need for
manual IP management or static CIDR ranges.
CloudNativePG now supports referencing a pre-existing
ServiceAccount
in Cluster and Pooler resources. This enables a more streamlined integration
with cloud provider IAM services, such as AWS IRSA, GCP Workload Identity, and
Azure Workload Identity.
Explore other improvements in this release, including:
pg_upgrade jobs when an image is reverted.Dive into the full details in the release notes for 1.29 RC1.
The stability of each CloudNativePG release relies on the community’s engagement. Testing your workloads with this release candidate helps identify bugs and regressions early.
This is the first release candidate for CloudNativePG 1.29. Further candidates will be released only as necessary before the final launch, currently planned before the end of March.
Connect with our community on your preferred platform!
Thank you for your continued support of CloudNativePG. Your contributions help us advance the Kubernetes-native PostgreSQL experience.