PGO, the Postgres Operator from Crunchy Data, gives you a declarative Postgres solution that automatically manages your PostgreSQL clusters.
Designed for your GitOps workflows, it is easy to get started with Postgres on Kubernetes with PGO. Within a few moments, you can have a production-grade Postgres cluster complete with high availability, disaster recovery, and monitoring, all over secure TLS communications. Even better, PGO lets you easily customize your Postgres cluster to tailor it to your workload!
With conveniences like cloning Postgres clusters to using rolling updates to roll out disruptive changes with minimal downtime, PGO is ready to support your Postgres data at every stage of your release pipeline. Built for resiliency and uptime, PGO will keep your Postgres cluster in its desired state, so you do not need to worry about it.
PGO is developed with many years of production experience in automating Postgres management on Kubernetes, providing a seamless cloud native Postgres solution to keep your data always available.
We recommend following our Quickstart for how to install and get up and running with PGO, the Postgres Operator from Crunchy Data. However, if you can't wait to try it out, here are some instructions to get Postgres up and running on Kubernetes:
- Fork the Postgres Operator examples repository and clone it to your host machine. For example:
YOUR_GITHUB_UN="<your GitHub username>"
git clone --depth 1 "git@github.com:${YOUR_GITHUB_UN}/postgres-operator-examples.git"
cd postgres-operator-examples- Run
kubectl apply -k kustomize/install
For more information please read the Quickstart and Tutorial.
PGO, the Postgres Operator from Crunchy Data, comes with all of the features you need for a complete cloud native Postgres experience on Kubernetes!
PostgreSQL Cluster Provisioning
Create, Scale, & Delete PostgreSQL clusters with ease, while fully customizing your Pods and PostgreSQL configuration!
Safe, automated failover backed by a distributed consensus high availability solution. Uses Pod Anti-Affinity to help resiliency; you can configure how aggressive this can be! Failed primaries automatically heal, allowing for faster recovery time.
Support for standby PostgreSQL clusters that work both within and across multiple Kubernetes clusters.
Backups and restores leverage the open source pgBackRest utility and includes support for full, incremental, and differential backups as well as efficient delta restores. Set how long you to retain your backups. Works great with very large databases!
Security and TLS
PGO enforces that all connections are over TLS. You can also bring your own TLS infrastructure if you do not want to use the defaults provided by PGO.
PGO runs containers with locked-down settings and provides Postgres credentials in a secure, convenient way for connecting your applications to your data.
Track the health of your PostgreSQL clusters using the open source pgMonitor library.
Safely apply PostgreSQL updates with minimal impact to the availability of your PostgreSQL clusters.
Choose between asynchronous and synchronous replication for workloads that are sensitive to losing transactions.
Create new clusters from your existing clusters or backups with efficient data cloning.
Advanced connection pooling support using pgBouncer.
Have your PostgreSQL clusters deployed to Kubernetes Nodes of your preference. Set your pod anti-affinity, node affinity, Pod tolerations, and more rules to customize your deployment topology!
Choose the type of backup (full, incremental, differential) and how frequently you want it to occur on each PostgreSQL cluster.
Store your backups in Amazon S3 or any object storage system that supports the S3 protocol. You can also store backups in Google Cloud Storage and Azure Blob Storage.
You can also mix-and-match: PGO lets you store backups in multiple locations.
PGO makes it easy to fully customize your Postgres cluster to tailor to your workload:
- Choose the resources for your Postgres cluster: container resources and storage size. Resize at any time with minimal disruption.
-
- Use your own container image repository, including support
imagePullSecretsand private repositories
- Use your own container image repository, including support
- Customize your PostgreSQL configuration
Deploy PGO to watch Postgres clusters in all of your namespaces, or restrict which namespaces you want PGO to manage Postgres clusters in!
PostgreSQL containers deployed with the PostgreSQL Operator include the following components:
- PostgreSQL
- PostgreSQL Contrib Modules
- PL/Python + PL/Python 3
- PL/Perl
- PL/Tcl
- pgAudit
- pgAudit Analyze
- pg_cron
- pg_partman
- pgnodemx
- set_user
- TimescaleDB (Apache-licensed community edition)
- wal2json
- pgBackRest
- pgBouncer
- pgAdmin 4
- pgMonitor
- Patroni
- LLVM (for JIT compilation)
In addition to the above, the geospatially enhanced PostgreSQL + PostGIS container adds the following components:
PostgreSQL Operator Monitoring uses the following components:
Additional containers that are not directly integrated with the PostgreSQL Operator but can work alongside it include:
For more information about which versions of the PostgreSQL Operator include which components, please visit the compatibility section of the documentation.
PGO, the Postgres Operator from Crunchy Data, is tested on the following platforms:
- Kubernetes 1.20+
- OpenShift 4.6+
- Rancher
- Google Kubernetes Engine (GKE), including Anthos
- Amazon EKS
- Microsoft AKS
- VMware Tanzu
This list only includes the platforms that the Postgres Operator is specifically tested on as part of the release process: PGO works on other Kubernetes distributions as well.
Want to contribute to the PostgreSQL Operator project? Great! We've put together a set of contributing guidelines that you can review here:
Once you are ready to submit a Pull Request, please ensure you do the following:
- Reviewing the contributing guidelines and ensure your that you have followed the commit message format, added testing where appropriate, documented your changes, etc.
- Open up a pull request based upon the guidelines. If you are adding a new
feature, please open up the pull request on the
masterbranch. - Please be as descriptive in your pull request as possible. If you are referencing an issue, please be sure to include the issue in your pull request
If you believe you have found a bug or have a detailed feature request, please open a GitHub issue and follow the guidelines for submitting a bug.
For general questions or community support, we welcome you to join the PGO project community mailing list at https://groups.google.com/a/crunchydata.com/forum/#!forum/postgres-operator/join and ask your question there.
For other information, please visit the Support section of the documentation.
For additional information regarding the design, configuration, and operation of the PostgreSQL Operator, pleases see the Official Project Documentation.
If you are looking for the nightly builds of the documentation, you can view them at:
https://crunchydata.github.io/postgres-operator/latest/
Documentation for previous releases can be found at the Crunchy Data Access Portal
When a PostgreSQL Operator general availability (GA) release occurs, the container images are distributed on the following platforms in order:
The image rollout can occur over the course of several days.
To stay up-to-date on when releases are made available in the Crunchy Data Developer Portal, please sign up for the Crunchy Data Developer Program Newsletter. You can also join the PGO project community mailing list
The PGO Postgres Operator project source code is available subject to the Apache 2.0 license with the PGO logo and branding assets covered by our trademark guidelines.