compare

Crunchy Postgres for Kubernetes vs Percona Operator for MySQL based on Percona XtraDB Cluster

The same facts for both, read from GitHub every night, and the relation a person reviewed.

Crunchy Postgres for Kubernetes vs Percona Operator for MySQL based on Percona XtraDB Cluster
FactCrunchy Postgres for KubernetesPercona Operator for MySQL based on Percona XtraDB Cluster
LanguageGoGo
LicenceApache-2.0Other
Stars4.5k624
Latestv6.0.2v1.20.0
Last push2026-09-162026-10-05
Release cadenceabout 39 days between releasesabout 104 days between releases
Active contributors3 commit authors on the default branch in the last 90 days2 commit authors on the default branch in the last 90 days
Flagsnonenone
  • Both replace Amazon RDS. Alternatives to Amazon RDS →

    PartialCrunchy Postgres for KubernetesPostgreSQL clusters on Kubernetes with pgBackRest backups, Patroni failover and PgBouncer pooling; PostgreSQL only.

    PartialPercona Operator for MySQL based on Percona XtraDB ClusterSynchronously replicated MySQL clusters on Kubernetes, with ProxySQL or HAProxy in front and scheduled backups.