Skip to content
Percona Documentation
Rate this page
☆ ☆ ☆ ☆ ☆
Thanks for your feedback
Thank you! The feedback has been submitted.

Get free database assistance or contact our experts for personalized support.

Get help from Percona

Percona Operator for PostgreSQL 3.0.0 has been released

Percona Operator for PostgreSQL 3.0.0 has been released on May 22, 2026.

This version establishes Percona Operator for PostgreSQL as a hard fork of the Crunchy PGO project , making it fully independent and empowering the Percona team and community to drive and rapidly deliver features and improvements tailored to user needs.

Try it out using the Quickstart guide.

New features and improvements introduced by this release include:

  • Crunchy CRD renaming and seamless resource migration — Upstream Crunchy Custom Resource Definitions (CRDs) are now moved to a new API group upstream.pgv2.percona.com and the Operator automatically migrates all dependent resources to this API group. This change enables seamless coexistence of Crunchy and Percona Operators in the same Kubernetes cluster and provides a smooth migration path from one to another.

  • Improved namespace scoping for Operator OLM installations from Community catalogues - Operator installs from Community catalogues now respect the OperatorGroup namespace scope. In the all-namespaces mode it now correctly watches the whole cluster instead of its install namespace as in previous versions. In the single-namespace mode it only watches the namespaces listed in olm.targetNamespaces. After upgrade, the Operator may start reconciling PerconaPostgreSQL resources in namespaces it previously ignored. Check the Operator installation mode before you upgrade, especially if several Operators share a cluster; consider enabling the single-namespace mode per Operator to avoid overlapping reconciliation.

Learn more in Percona Operator for PostgreSQL 3.0.0 release notes.