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.
The Postgres Operator has been developed at Zalando and is being used in production for over three years.
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 tutorial.
There is a browser-friendly version of this documentation at postgres-operator.readthedocs.io
There are two places to get in touch with the community: