Crunchy Postgres for Kubernetes

Crunchy Postgres for Kubernetes (PGO) is a Kubernetes operator from Crunchy Data Solutions that automates the lifecycle of PostgreSQL clusters on Kubernetes.

Updated 8 Jun 2026 Reviewed by 7wData

Publisher review

Crunchy Postgres for Kubernetes (PGO) is a Kubernetes operator from Crunchy Data Solutions that automates the lifecycle of PostgreSQL clusters on Kubernetes. It is designed for teams that need production-ready PostgreSQL with minimal manual intervention, offering features like automatic failover, self-healing, backups, and disaster recovery out of the box. The operator is particularly suited for enterprises requiring compliance certifications, 24/7/365 support, and deployment flexibility across various environments including OpenShift, GKE, EKS, AKS, Tanzu, and Rancher. It targets organizations that want to run PostgreSQL at scale, from a single database to thousands, using a GitOps-native approach with tools like Helm, Kustomize, OLM, and ArgoCD.

The operator works by defining PostgreSQL cluster specifications as Kubernetes custom resources (CRDs). For example, a simple YAML manifest specifying `postgresVersion: 14`, instance replicas, storage claims, and backup repo configurations can deploy a fully functional cluster. PGO automates major version upgrades, point-in-time recovery, and TLS/SSL encryption with automated certificate management. It includes advanced connection pooling and load balancing via pgBouncer, real-time performance monitoring with metrics and dashboards, and zero-downtime updates for both software and PostgreSQL versions. Backups use pgBackrest with support for multiple repositories, and the operator enforces WAL archival by default to a separate PersistentVolume.

In the Kubernetes PostgreSQL operator market, Crunchy Postgres competes directly with CloudNative PG, StackGres, Zalando Postgres Operator, and Percona Operator for PostgreSQL. Compared to CloudNative PG, which lacks automated major version upgrades, PGO provides seamless major version updates, though some manual steps remain. Against Zalando's operator, which has seen reduced maintenance activity, PGO offers more mature lifecycle management and out-of-the-box integration for enterprise concerns like HashiCorp Vault. StackGres and Percona operators offer similar features but lack the same level of certified compliance and multi-cloud support. PGO is rated as having more mature lifecycle management out of the box than alternatives, making it a strong choice for organizations prioritizing stability and enterprise readiness.

Key trade-offs include the default enforcement of WAL archival to another PersistentVolume, which may not suit all users and can increase storage costs. Major version upgrades, while automated, still require manual steps and careful planning, reducing the fully hands-off experience some teams expect. The operator's rich feature set introduces complexity, meaning smaller teams or simple use cases might find it over-engineered compared to lighter operators like CloudNative PG. Additionally, while the core operator is free, enterprise support and advanced features require a paid subscription, which could be a barrier for budget-conscious organizations. Overall, PGO excels in environments where enterprise compliance, high availability, and multi-cloud deployment are critical, but it demands a commitment to its operational model and potential additional costs.

How it works

Automatic failover and self-healing

The operator automatically detects failures and promotes replicas to primary, ensuring continuous database operations without manual intervention.
Backups and disaster recovery

Automated backup management using pgBackrest with point-in-time recovery, supporting multiple repositories and WAL archival for data protection.
Performance monitoring and analytics

Real-time monitoring and alerting for database health and performance metrics, with detailed dashboards for query analysis and resource usage.
Secure connections and TLS management

Built-in TLS/SSL encryption with automated certificate management, ensuring secure client-server and replication connections.
Connection pooling and load balancing

Advanced connection pooling via pgBouncer and load balancing across replicas, optimizing database performance for high-concurrency workloads.
Zero-downtime updates and upgrades

Seamless software updates and PostgreSQL major version upgrades without service interruption, using rolling update strategies.
GitOps-native deployment

Declarative management via Helm, Kustomize, OLM, and ArgoCD, enabling version-controlled, reproducible database deployments.

Strengths and trade-offs

Strengths

Mature lifecycle management out of the box, with automated failover and self-healing reducing downtime in production clusters.
Out-of-the-box integration for enterprise problems like HashiCorp Vault and compliance certifications, simplifying security and audit requirements.
Supports deployment on six major Kubernetes environments (OpenShift, GKE, EKS, AKS, Tanzu, Rancher) and multiple infrastructure types including bare metal and hybrid cloud.
Automated backup management with point-in-time recovery and WAL archival, providing robust disaster recovery capabilities.

Trade-offs

Enforcement of WAL archival by default to a separate PersistentVolume may increase storage costs and complexity for users who prefer alternative backup strategies.
Major version upgrades require manual steps and careful planning, reducing the fully automated experience some teams expect from an operator.
The operator's rich feature set introduces operational complexity, making it potentially over-engineered for small or simple PostgreSQL deployments.
Enterprise-grade features and 24/7/365 support require a paid subscription, which may be a barrier for budget-constrained organizations.

Pricing context

Crunchy Postgres is available in several editions: self-managed (free core operator, paid enterprise support), fully managed cloud via Crunchy Bridge on AWS, Azure, GCP, and Crunchy Data Warehouse optimized for analytical workloads. Pricing details are not publicly listed; contact sales for quotes.

Getting started with Crunchy Postgres for Kubernetes

Install the PGO operator

Deploy the Crunchy Postgres operator into your Kubernetes cluster using Helm, Kustomize, or OLM. Follow the official quickstart guide to apply the manifests and verify the operator pod is running.
Define a PostgreSQL cluster

Create a YAML manifest specifying your PostgreSQL cluster as a custom resource. Set parameters like postgresVersion, instance replicas, storage size, and backup repo configuration. Apply the manifest with kubectl.
Connect to the database

Retrieve the generated database credentials from the Kubernetes secret. Use the primary service endpoint and port to connect with any PostgreSQL client, such as psql, providing the username and password.
Configure automated backups

Edit your cluster manifest to define pgBackrest repositories for backups. Set retention policies and schedule intervals. Apply the changes to enable automatic WAL archival and point-in-time recovery.
Monitor cluster health

Access the built-in monitoring dashboards by exposing the metrics service. Use kubectl port-forward to view real-time performance metrics, query analysis, and alerting for database health.

Frequently Asked Questions

What is Crunchy Postgres for Kubernetes?

Crunchy Postgres for Kubernetes (PGO) is a Kubernetes operator from Crunchy Data Solutions that automates PostgreSQL cluster lifecycle management. It handles failover, backups, and upgrades with minimal manual intervention, targeting production environments needing high availability and compliance.

How does Crunchy Postgres for Kubernetes handle failover?

PGO automatically detects failures and promotes replicas to primary without manual intervention. This self-healing capability ensures continuous database operations, reducing downtime in production clusters and maintaining high availability for PostgreSQL deployments on Kubernetes.

What backup features does Crunchy Postgres for Kubernetes offer?

PGO uses pgBackrest for automated backups with point-in-time recovery and WAL archival to a separate PersistentVolume. It supports multiple backup repositories, ensuring robust disaster recovery and data protection for PostgreSQL clusters on Kubernetes.

How does Crunchy Postgres for Kubernetes compare to CloudNative PG?

Unlike CloudNative PG, PGO provides automated major version upgrades and more mature lifecycle management out of the box. It also offers enterprise compliance certifications and multi-cloud support, making it a stronger choice for organizations prioritizing stability and enterprise readiness.

What are the weaknesses of Crunchy Postgres for Kubernetes?

PGO enforces WAL archival by default to a separate PersistentVolume, increasing storage costs. Major version upgrades require manual steps, and the rich feature set adds complexity for small deployments. Enterprise support also requires a paid subscription.

Is Crunchy Postgres for Kubernetes free to use?

The core PGO operator is free for self-managed use, but enterprise support and advanced features require a paid subscription. Pricing details are not publicly listed; contact sales for quotes. Fully managed options like Crunchy Bridge are also available on major clouds.

Alternatives

How Crunchy Postgres for Kubernetes compares

Direct head-to-head against 3 competitors. Picked by 7wData.

Pricing: Crunchy Postgres is available in several editions: self-managed (free core operator, paid enterprise support), fully managed cloud via Crunchy Bridge on AWS, Azure, GCP, and Crunchy Data Warehouse optimized for analytical workloads. Pricing details are not publicly listed; contact sales for quotes.
Target: Crunchy Postgres for Kubernetes (PGO) is a Kubernetes operator from Crunchy Data Solutions that automates the lifecycle of PostgreSQL clusters on Kubernetes.
Strength: Mature lifecycle management out of the box, with automated failover and self-healing reducing downtime in production clusters.
Watch for: Enforcement of WAL archival by default to a separate PersistentVolume may increase storage costs and complexity for users who prefer alternative backup strategies.

Pricing: Open source (Apache 2.0); commercial support via Zalando or third parties.
Target: Teams needing a mature, open-source Postgres operator with strong HA and backup features.
Deployment: Kubernetes operator
Strength: Battle-tested at scale within Zalando; supports complex HA and backup configurations.
Watch for: Steeper learning curve for advanced features; community support may lag behind Crunchy's commercial support.

Pricing: Open source (Apache 2.0); commercial support from EDB.
Target: Organizations seeking a CNCF-backed operator with declarative management and native K8s integration.
Deployment: Kubernetes operator
Strength: CNCF sandbox project with built-in rolling updates, backup, and declarative configuration.
Watch for: Younger project with smaller ecosystem; EDB commercial support may be costly for some use cases.

Pricing: Open source core; enterprise edition with support starts at contact sales.
Target: Enterprises wanting a full-featured Postgres platform with built-in connection pooling and monitoring.
Deployment: Kubernetes operator
Strength: Integrated PgBouncer, WAL-G backups, and Prometheus monitoring out of the box.
Watch for: Enterprise edition pricing not public; some users report complex initial setup.

User reviews

No user reviews yet. Be the first to write one.

Sources

Reporting on this tool draws on these publicly available sources.

Crunchy Postgres for Kubernetes

On this page

Publisher review

How it works

Automatic failover and self-healing

Backups and disaster recovery

Performance monitoring and analytics

Secure connections and TLS management

Connection pooling and load balancing

Zero-downtime updates and upgrades

GitOps-native deployment