Skip to content

Percona Operator for PostgreSQL 2.1.0 (Tech preview)

The Percona Operator built with best practices of configuration and setup of Percona Distribution for PostgreSQL on Kubernetes .

Percona Operator for PostgreSQL helps create and manage highly available, enterprise-ready PostgreSQL clusters on Kubernetes. It is 100% open source, free from vendor lock-in, usage restrictions and expensive contracts, and includes enterprise-ready features: backup/restore, high availability, replication, logging, and more.

The benefits of using Percona Operator for PostgreSQL include saving time on database operations via automation of Day-1 and Day-2 operations and deployment of consistent and vetted environment on Kubernetes.


Version 2.1.0 of the Percona Operator for PostgreSQL is a tech preview release and it is not recommended for production environments. As of today, we recommend using Percona Operator for PostgreSQL 1.x, which is production-ready and contains everything you need to quickly and consistently deploy and scale PostgreSQL clusters in a Kubernetes-based environment, on-premises or in the cloud.

Release Highlights

  • PostgreSQL 15 is now officially supported by the Operator with the new exciting features it brings to developers

  • UX improvements related to Custom Resource have been added in this release, including the handy pg, pg-backup, and pg-restore short names useful to quickly query the cluster state with the kubectl get command and additional information in the status fields, which now show name, endpoint, status, and age

New Features

  • K8SPG-328: The new delete-pvc finalizer allows to either delete or preserve Persistent Volumes at Custom Resource deletion

  • K8SPG-330: The new delete-ssl finalizer can now be used to automatically delete objects created for SSL (Secret, certificate, and issuer) in case of cluster deletion

  • K8SPG-331: Starting from now, the Operator adds short names to its Custom Resources: pg, pg-backup, and pg-restore

  • K8SPG-282: PostgreSQL 15 is now officially supported by the Operator


  • K8SPG-262: The Operator now does not attempt to start Percona Monitoring and Management (PMM) client if the corresponding secret does not contain the pmmserver or pmmserverkey key

  • K8SPG-285: To improve the Operator we capture anonymous telemetry and usage data. In this release we add more data points to it

  • K8SPG-295: Additional information was added to the status of the Operator Custom Resource, which now shows name, endpoint, status, and age fields

  • K8SPG-304: The Operator stops using trust authentication method in pg_hba.conf for better security

  • K8SPG-325: Custom Resource options previously named paused and shutdown were renamed to unmanaged and pause for better alignment with other Percona Operators

Bugs Fixed

  • K8SPG-272: Fix a bug due to which PMM agent related to the Pod wasn’t deleted from the PMM Server inventory on Pod termination

  • K8SPG-279: Fix a bug which made the Operator to crash after creating a backup if there was no backups.pgbackrest.manual section in the Custom Resource

  • K8SPG-298: Fix a bug due to which the shutdown Custom Resource option didn’t work making it impossible to pause the cluster

  • K8SPG-334: Fix a bug which made it possible for the monitoring user to have special characters in the autogenerated password, making it incompatible with the PMM Client

Supported platforms

The following platforms were tested and are officially supported by the Operator 2.1.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: 2024-07-04