Felix Kunde

So far we've been reluctant to ownerReferences and finalizes as we fear it makes deleting DBs by accident too easy. Of course, I see that you want things to be...

It's possible. Simply not implemented yet from the operator side. Maybe you want to go ahead? Shouldn't be too hard following the other AWS and [GCP](https://github.com/zalando/postgres-operator/pull/1446) examples in the [code](https://github.com/zalando/postgres-operator/blob/master/pkg/cluster/k8sres.go#L1907)....

At Zalando we consider [liveness probes](https://srcco.de/posts/kubernetes-liveness-probes-are-dangerous.html) as something to avoid. The readiness probe might a good addition, though.

We haven't yet open sourced the image. It also includes some patches to pgBouncer. Would like to publish, but other topics had a higher priority so far

You can also edit pg_hba.conf to `trust` all connections :smiling_face_with_tear: , then passwords are ignored. Seriously, I think, it's an anti pattern these days to set human readable passwords in...

@wolacinio The operator creates a service for you. You don't have to do it yourself. Would be interesting to know, which resources you have defined in the postgres manifest. Maybe...

@Yannig sorry to keep you waiting. I'm not sure we want to add a Prometheus dependency. I thought, people were usually solving this via sidecars.

Because we support the full affinity spec, I'm afraid it would be too verbose for the UI. Can you post a screenshot?

I don't know if the operator should block annotations from triggering actions in the chosen cloud infrastructure. Maybe another option can be added to define which pod and service instances...

Config looks fine, I think. So the problem is with bootstrapping a new standby cluster? What do the Postgres logs inside the pod tell? Depending on the size of the...