The Postgres Operator delivers an easy to run highly-available PostgreSQL
clusters on Kubernetes (K8s) powered by Patroni.
It is configured only through Postgres manifests (CRDs) to ease integration into automated CI/CD
pipelines with no access to Kubernetes API directly, promoting infrastructure as code vs manual operations.
- Rolling updates on Postgres cluster changes, incl. quick minor version updates
- Live volume resize without pod restarts (AWS EBS, PVC)
- Database connection pooling with PGBouncer
- Support fast in place major version upgrade to PG13. Supports global upgrade of all clusters.
- Restore and cloning Postgres clusters on AWS, GCS and Azure
- Additionally logical backups to S3 or GCS bucket can be configured
- Standby cluster from S3 or GCS WAL archive
- Configurable for non-cloud environments
- Basic credential and user management on K8s, eases application deployments
- Support for custom TLS certificates
- UI to create and edit Postgres cluster manifests
- Support for AWS EBS gp2 to gp3 migration, supporting iops and throughput configuration
- Compatible with OpenShift
- Supports PostgreSQL 14, starting from 9.6+
- Streaming replication cluster via Patroni
- Point-In-Time-Recovery with
WAL-E via Spilo
- Preload libraries: bg_mon,
- Incl. popular Postgres extensions such as
The Postgres Operator has been developed at Zalando and is being used in
production for over three years.
Using Spilo 12 images or lower
If you are already using the Postgres operator in older version with a Spilo 12 Docker image you need to be aware of the changes for the backup path.
We introduce the major version into the backup path to smoothen the major version upgrade that is now supported.
The new operator configuration can set a compatibility flag enable_spilo_wal_path_compat to make Spilo look for wal segments in the current path but also old format paths.
This comes at potential performance costs and should be disabled after a few days.
The newest Spilo image is:
The last Spilo 12 image is:
For a quick first impression follow the instructions of this
Supported setups of Postgres and Applications
There is a browser-friendly version of this documentation at
There are two places to get in touch with the community:
- The GitHub issue tracker
- The #postgres-operator slack channel