Another popular alternative: https://github.com/zalando/postgres-operator
New player from Enterprise DB: https://github.com/cloudnative-pg/cloudnative-pg
In case some of you are interested in learning more about running databases on Kubernetes, or more generally stateful workloads, there is a community dedicated to that https://dok.community/
I a am part of the community team. We have weekly live streams/blog posts about the topic and a Slack channel.
I used this in the past. Helped a lot with provisioning micro-pg-clusters.
But honestly, the project always felt like a one-man-show, some (realy great) dev had a working set of scripts and kubernetized / operatorized it, but the whole thing feels hacky as hell.
I'd still give a try if I ever needed postgresql again, but I would also know that I need to implement (again) my set of scripts and hacks on top of it.
CloudNativePG community member here.
I think this is a super interesting space. What I mean by that is the fact we have Postgres, which is arguably one of the most successful publicly governed open source project out there, for many decades! That meats on of the most vibrant and transformative publicly governed projects as well, called Kubernetes (CNCF).
Why then consider a (proprietary) vendor governed (open source) project to bring these two technologies together? With CloudNativePG, you bring these two super strong communities together using these exact same governance principles, enabling everyone to benefit and contribute.
It is my conviction that this is going to be one of those elements that is going to contribute to the ongoing transformation of data management today.
How does this compare with something like kubegres?
I cannot trust critical infrastructure components to 3rd party kubernetes operators. I don't like operators (I didn't write) in general because I find them too opinionated and obfuscated. It's unbelievable to me that someone would deploy a production datastore using one.
https://www.crunchydata.com/developers/terms-of-use
Before using Crunchy Data, I'd read their terms of use.
"without an active Crunchy Data Support Subscription or other signed written agreement with Crunchy Data are not intended for... using the services provided under the Program (or any part of the services) for a production environment, production applications or with production data"
https://hub.docker.com/r/crunchydata/crunchy-postgres
If you look at their Docker Hub images, you'll see that they're provided under the terms of use of the Crunchy Data developer program which means you can't use them in production without an active subscription.
Maybe I'm reading it wrong, but if that's the case Crunchy Data should definitely change their terms of service.
https://www.percona.com/blog/2021/05/26/percona-distribution...
Percona certainly seems to think you can't use the Crunchy Data images in production saying, "CrunchyData container images are provided under Crunchy Data Developer Program, which means that without an active contract they could not be used for production."