Percona Operator for PostgreSQL - Percona Operator for PostgreSQL 2.6.0 (2025-03-17) (original) (raw)

Installation

Release Highlights¶

This release provides the following features and improvements:

Backup improvements¶

This release implemented several improvements to the backup/restore process:

• A new delete-backups finalizer was implemented to automatically remove all backups when deleting the cluster. This finalizer is off by default. It’s experimental and, therefore, is not recommended for production environments.
• Backup logic was improved and now allows retrying a failed backup in the same backup Pod for a specified number of times before deleting this Pod and creating a new one. This should be beneficial in case of short connectivity issues or timeouts. This behavior is controlled by the new backups.pgbackrest.jobs.backoffLimit and backups.pgbackrest.jobs.restartPolicy Custom Resource options.
• You can now overwrite the default restore command for pgBackRest via the patroni.dynamicConfiguration Custom Resource option. Particularly, this allows to control and filter files restored to pg_wal directory without editing these files in the backup repository storage.

PostgreSQL 17 support¶

PostgreSQL 17 is now supported by the Operator in addition to versions 13 - 16. The appropriate images are now included in the list of Percona-certified images. See these blogposts for details about the latest PostgreSQL 17 features with the added security and functionality improvements:

• Encrypt PostgreSQL Data at Rest on Kubernetes by Ege Gunes
• The Powerful Features Released in PostgreSQL 17 Beta 2 by Shivam Dhapatkar
• PostgreSQL 17: Two Small Improvements That Will Have a Major Impact by David Stokes.

PostgreSQL 17 is currently not recommended for production environments due to the known limitation.

Update from April 1, 2025: We have added PostgreSQL 17.4 image and database cluster components based on this image. It is now production ready and we recommend updating the database cluster from PostgreSQL 17.2 to 17.4. Check the upgrade instructions for steps

pgvector is added to the PostgreSQL image¶

To support you with your AI journey, we’ve added the pgvector extension to the PostgreSQL images shipped with our Operator. Now, you can easily use Percona Distribution for PostgreSQL as a vector database by simply enabling it in your Custom Resource options. No more custom extension installations needed.

New features¶

• K8SPG-628: The custom restore_command can be now passed to pgBackRest via the patroni.dynamicConfiguration Custom Resource option
• K8SPG-619: New backups.pgbackrest.jobs.backoffLimit and backups.pgbackrest.jobs.restartPolicy Custom Resource options allow to retry backup in the backup Pod for a specified number of times before abandoning the Pod and creating the new one
• K8SPG-648: PostgreSQL 17 is now supported by the Operator

Improvements¶

• K8SPG-487: New spec.metadata.labels and spec.metadata.annotations Custom Resource options allow setting labels and annotation globally for all Kubernetes objects created by the Operator
• K8SPG-554: New tlsOnly Custom Resource option allows the user to enforce TLS connections for the database cluster
• K8SPG-586: The new experimental finalizers.delete-backups finalizer (off by default) removes all backups of the cluster at cluster deletion event
• K8SPG-634: The new autoCreateUserSchema Custom Resource option enhances the declarative user management by automatically creating per-user schemas
• K8SPG-652: Improve security and meet compliance requirements by using PostgreSQL images built based on Red Hat Universal Base Image (UBI) 9 instead of UBI 8
• K8SPG-692: Patroni versions 4.x are now supported by the Operator in addition to versions 3.x
• K8SPG-699: The pgvector extension is now included within the PostgreSQL image used by the Operator
• K8SPG-701: The extensions.image Custom Resource option is now optional, and can be omitted for builtin PostgreSQL extensions
• K8SPG-702: A retry logic was implemented to fix intermittent Pod exec failures caused by timeouts (Thanks to dcaputo-harmoni for contribution)
• K8SPG-711: The new README.md explains how to build your own images for the PostgreSQL cluster components used by the Operator

Bugs Fixed¶

• K8SPG-594: Fix a bug where extension was still appearing in pg_extension table after being removed from Custom Resource and physically deleted by the Operator
• K8SPG-637: Fix a bug where restore was failing with “waiting for another restore to finish” if the pg-restore object of a previous unfinished restore was manually deleted
• K8SPG-638: Fix a bug that caused flooding the logs with no completed backups found error at cluster initialization.
• K8SPG-645: Fix a bug where creating sidecar containers for pgBouncer did not work
• K8SPG-681: Fixed a bug where the “Last Recoverable Time” information field was missing from the output of the kubectl get pg-backup command due to misdetection cases
• K8SPG-713: Fix a bug where The cluster not found errors were appearing in the Operator logs on cluster deletion

Deprecation, Change, Rename and Removal¶

• The new versions of Percona distribution for PostgreSQL used by the Operator come with Patroni 4.x, which introduces breaking changes compared to previously used 3.x versions.
  To maintain backward compatibility, the Operator detects the Patroni version used in the image. It is also possible to disable this auto-detection feature by manually setting the Patroni version via the following annotation set in the metadata part of the Custom Resource:
  pgv2.percona.com/custom-patroni-version: "4"
• PostgreSQL 12 is no longer supported by the Operator 2.6.0 and newer versions.

Known limitations¶

• PostgreSQL 17.2 image and images for other database cluster components based on PostgreSQL 17 contain the known CVE-2025-1094 - a vulnerability in the libpq PostgreSQL client library, which makes images used by the Operator vulnerable to SQL injection within the PostgreSQL interactive terminal due to the lack of neutralizing quoting. Images for PostgreSQL 17 will be available soon, while images for other PosgreSQL versions have already been fixed.
• PostgreSQL 17.4 image includes the fix for CVE-2025-1094 , which closed a vulnerability in the libpq PostgreSQL client library but introduced a regression related to string handling for non-null terminated strings. The error would be visible based on how a PostgreSQL client implemented this behavior.

Supported platforms¶

The Operator 2.6.0 is developed, tested and based on:

• PostgreSQL 13.18, 14.15, 15.10, 16.8, 17.2 and 17.4 as the database. Other versions may also work but have not been tested.
• pgBouncer for connection pooling:
  • version 1.23.1 - for PostgreSQL 17.2
  • version 1.24.0 - for PostgreSQL 13.20, 14.17, 15.12, 16.8, 17.4
• Patroni for high-availability:
  • version 4.0.5 - for PostgreSQL 17.4
  • version 4.0.3 - for PostgreSQL 17.2
  • version 4.0.4 - for PostgreSQL 13.20, 14.17, 15.12, 16.8

Percona Operators are designed for compatibility with all CNCF-certified Kubernetes distributions.

Our release process includes targeted testing and validation on major cloud provider platforms and OpenShift, as detailed below for Operator version 2.6.0:

• Google Kubernetes Engine (GKE) 1.29 - 1.31
• Amazon Elastic Container Service for Kubernetes (EKS) 1.29 - 1.32
• OpenShift 4.14 - 4.18
• Azure Kubernetes Service (AKS) 1.29 - 1.31
• Minikube 1.35.0 with Kubernetes 1.32.0

This list only includes the platforms that the Percona Operators are specifically tested on as part of the release process. Other Kubernetes flavors and versions depend on the backward compatibility offered by Kubernetes itself.

Last update: 2025-04-07