postgres-operator VS postgres-operator

I found a couple of those Postgres operators, like the movetokube/postgres-operator but I honestly can't tell which of them are any good. Do you have any experience with them? I also would need something for MinIO, since I'm able to use Terraform to create databases, buckets and then spin up the app. It's a really comfortable process albeit I do prefer GitOps.

Not everything carries over from Terraform to GitOps but with that said check out this operator that lets you provision an existing postgres database.

On my list is the external postgres operator to provision databases on the external postgres instance, similar to using democratic-csi for providing volumes on the TrueNAS host. https://github.com/movetokube/postgres-operator

Others have mentioned some great operators for managing in-cluster postgres databases, but if you're looking to manage external or previously existing databases: https://github.com/movetokube/postgres-operator

That is my plan, too. I have the External Postgres Server Operator on my list of thing to try out. Does anyone have experience with it already?

Here is an example of an operator that creates databases: https://github.com/movetokube/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.

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)

git clone https://github.com/zalando/postgres-operator.git cd postgres-operator

Zalando / Postgres-Operator

Somewhere between here and here i found out about that.

Here's an example of using the PostgreSQL Operator to deploy a high availability PostgreSQL cluster in Kubernetes. In this example, I'll be using the PostgreSQL Operator from Zalando [https://github.com/zalando/postgres-operator] to deploy a PostgreSQL cluster with two nodes.

Here's the operator for a postgres cluster: 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.