5 ms·
I’ve been using it in prod for a while now, pretty happy with it. Solid, integrated pgbouncer, crd based, good license. I do wish there was a simpler way to ha
by nz_cal 3y ago
I’ve been using it in prod for a while now, pretty happy with it. Solid, integrated pgbouncer, crd based, good license.
I do wish there was a simpler way to handle major version upgrades of pg.
When I looked at some alternatives, these were my thoughts (may be out of date by now)
- kubegres: maintained by one guy, lots of GitHub issues with no responses
- crunchy data pgo: licensing is not obvious, seems to require license in some cases
- stackgres: agpl, no thanks
- zalando: they know pg extremely well, but it’s not kubernetes native. Doesn’t include pgbouncer. Doesn’t handle automatic failover when a node dies, and during testing it often got confused when killing a node.
- uneekname 3y agoI appreciate your perspective, thanks. Major version bumps do seem to be difficult sometimes with pg in my limited experience.
- gbartolini 3y agoIf you are interested, I suggest this article I wrote that covers the current state of major upgrades with CloudNativePG: https://www.enterprisedb.com/blog/current-state-major-postgresql-upgrades-cloudnativepg-kubernetes https://www.enterprisedb.com/blog/current-state-major-postgr...
- samokhvalov 3y ago> Doesn’t handle automatic failover when a node dies Patroni, the most popular autofailover solution for Postgres, is developed in Zalando. Of course it's included in Zalando operator by default.