Gabriele Bartolini: CloudNativePG and Crunchy PGO: an honest, opinionated comparison
The article provides a comparison between CloudNativePG and Crunchy PGO, two popular open-source operators for PostgreSQL on Kubernetes. It discusses their architectural differences, backup strategies, and community health. The author, a co-founder of CloudNativePG, acknowledges his bias while highlighting the strengths and weaknesses of both operators.
- ▪CloudNativePG and Crunchy PGO are two widely adopted operators for running PostgreSQL on Kubernetes.
- ▪The article emphasizes the architectural divide between the two operators, particularly in their approach to high availability management.
- ▪Crunchy PGO relies on Patroni for high availability, while CloudNativePG takes a different approach by leveraging the Kubernetes API.
Opening excerpt (first ~120 words) tap to expand
CloudNativePG and Crunchy PGO: an honest, opinionated comparison18 May 2026·16 minsPostgresql Postgres Kubernetes K8s Cloudnativepg Cnpg Dok Data on Kubernetes Crunchy Pgo Operator Comparison High Availability Backup Migration Patroni Security Openssf Governance CNCF Observability Logging Logical ReplicationTable of ContentsCrunchy’s pioneering roleThe architectural divideDirect Pod managementThe Instance ManagerOn Kubernetes API server availabilityImage design, footprint and securityMajor version upgradesBackup and recoveryObservabilityCommunity health and governanceMy honest conclusionThis article compares CloudNativePG and Crunchy PGO, two of the most adopted open-source operators for running PostgreSQL on Kubernetes.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Unleashing the Power of Postgres in Kubernetes.
Discussion
0 comments
