Crunchy Data is pleased to announce the release of PGO v5, the Postgres Operator from Crunchy Data, which automates and simplifies deploying and managing open source Postgres clusters on Kubernetes and other Kubernetes-enabled Platforms. Instructions for getting started with the Postgres Operator can be found here:
The focus of the PGO v5 release was to take the features from the previous versions of PGO, add in some new features, and allow you to deploy Kubernetes native Postgres through a fully declarative, GitOps style workflow. As with previous versions, PGO v5 makes it easy to deploy production-ready, cloud native Postgres.
PGO v5 continues to support the Postgres architecture that was built up in previous releases. This means that Postgres clusters are deployed without a single-point-of-failure and can continue operating even if PGO is unavailable. PGO v5 includes support for Postgres high availability, backup management, disaster recovery, monitoring, full customizability, database cloning, connection pooling, security, running with locked down container settings, and more.
PGO 5.0 also continuously monitors your environment to ensure all of the components you want deployed are available. For example, if PGO detects that your connection pooler is missing, it will recreate it as you specified in the custom resource. PGO v5 can watch for Postgres clusters in all Kubernetes namespaces or be isolated to individual namespaces. There are a set of examples for how to use Kustomize and Helm with PGO v5. This example set will grow and we encourage you to contribute to it.
For a full explanation of the PGO v5, including additional features that were added since PGO 4.x, please see the release notes.
Crunchy Data is proud to support the development and maintenance of PGO, the Postgres Operator from Crunchy Data.