postgres-operator

At $WORK we’ve been using the Zalando Postgres kubernetes operator to great success: https://github.com/zalando/postgres-operator As someone who has operated Postgres clusters for over a decade before k8s was even a thing, I fully recommend just using a Postgres operator like this one and moving on. The out of box config is sane, it’s easy to override things, and failover/etc has been working flawlessly for years. It’s just the right line between total DIY and the simplicity of having a hosted solution. Postgres is solved, next problem.

If you are on k8s, the Zalando operator is an excellent choice: https://github.com/zalando/postgres-operator

yes, precisely. It's UI part that's broken, which cannot list snapshots. Issue is here, no fix since 2020, sadly: https://github.com/zalando/postgres-operator/issues/937

I personally like the Zalando operator better, you can add databases and users by updating the CRD, feature parity between the two on HA is pretty good https://github.com/zalando/postgres-operator

one of the solutions which made it pretty simple for us to run postgresql in a ha environment (mostly in k8s, but works standalone as well) is zalandos patroni: https://github.com/zalando/patroni it's really solid and worked for us for a few years already. (it also comes with a haproxy config to have a single leader connection) or for k8s their operator: https://github.com/zalando/postgres-operator (docker image: https://github.com/zalando/spilo) we've also tried other operators which were easier to get started, but they failed miserably (crunchyrolls operator is basically based on the zalando one)

As far as I understand Zalando does this. They have their own PostgreSQL operator https://github.com/zalando/postgres-operator.

And that repo you linked to has 1846 issues, 161 open. Which doesn't seem extraordinary based on my limited exposure to k8s. Another example: https://github.com/zalando/postgres-operator/issues with 445 open issues. Why? Maybe I'm wrong and this is all a good sign of progress, but my impression is that the entire k8s ecosystem is held together with reused duct tape.

In Kubernetes a service call end an operator watches for CRD specifying databases to be created and manages upgrade and backs for those databases. https://github.com/zalando/postgres-operator

My favorite route right now is running a postgres operator on Kubernetes & letting it do all the work for me. Zalando's operator use Patroni under the hood, to create a cluster over streaming replication. It also has Spilo, which orchestrates pg_basebackup or WAL-E for point-in-time backup. https://github.com/zalando/postgres-operator#postgresql-feat... CrunchyData operator seems to have built their own streaming replication system coordinated by Raft. https://access.crunchydata.com/documentation/postgres-operat... Both are fantastically featureful well-integrated operators that are super well maintained. Both are very recommendable.

Another popular alternative: https://github.com/zalando/postgres-operator New player from Enterprise DB: https://github.com/cloudnative-pg/cloudnative-pg

I used this one recently and it worked pretty well: https://github.com/zalando/postgres-operator

If not Kubernetes, check out this: https://github.com/vitabaks/postgresql_cluster – it's Postgres + patroni + pgBouncer + WAL-G or pgBackRest + Netdata + more, managed by Ansible. If you do want to use Kubernetes, then check out: - StackGres.io - https://github.com/zalando/postgres-operator - https://blog.flant.com/comparing-kubernetes-operators-for-po...

link to the zalando postgres operator: https://github.com/zalando/postgres-operator

I'm curious if you've looked at https://github.com/zalando/postgres-operator and had thoughts on how it compared. The CrunchyData operator seems to use Patroni and links to the Patroni documentation which links to the Zalando Postgres Operator from the same company as Patroni.