cloudflare-ingress-controller VS postgres-operator

I guess that would really depend on your setup. It would differ significantly if you’re doing virtualised nodes ontop of vmware/proxmox/qemi/etc, if you’re doing single node with storage, or if you’re doing something more exotic like raspberry pis with either one node with storage or external nas.

I have a couple of different setups (mostly for fun), which are pretty simple. Main things I use are a csi driver to allow me to use my trunas scale as storage (https://github.com/democratic-csi/democratic-csi), cloudflare’s argo tunnel to expose my clusters to the outside world (https://github.com/cloudflare/cloudflare-ingress-controller), an operator for managing external dns with cloudflare (https://github.com/kubernetes-sigs/external-dns/blob/master/...). Everything else is pretty much they way any other cluster would look.

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.