Skip to content

Percona Operator for PostgreSQL 2.6.0

Release Highlights

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-594: Run DROP EXTENSION on extension deletion
  • 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-689: Document 2.5.0-cw (cluster-wide variant) availability in OpenShift Marketplace
  • 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-710: It is now possible to completely disable backup functionality
  • 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-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

Deprecation, Change, Rename and Removal

With the Operator versions prior to 2.6.0, autogenerated TLS certificates for all database clusters were based on the same generated root CA. Starting from 2.5.0, the Operator creates root CA on a per-cluster basis.

Supported platforms

The Operator was developed and tested with PostgreSQL versions 13.18, 14.15, 15.10, 16.6, and 17.2. Other options may also work but have not been tested. The Operator 2.6.0 provides connection pooling based on pgBouncer 1.23.1 and high-availability implementation based on Patroni 4.0.3.

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:

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.

Get expert help

If you need assistance, visit the community forum for comprehensive and free database knowledge, or contact our Percona Database Experts for professional support and services. Join K8S Squad to benefit from early access to features and “ask me anything” sessions with the Experts.


Last update: 2025-02-28