Felix Kunde

When facing connections issue with the standby you need to [copy secrets of the source cluster](https://github.com/zalando/postgres-operator/blob/master/docs/user.md#providing-credentials-of-source-cluster).

LivenessProbes are [dangerous](https://srcco.de/posts/kubernetes-liveness-probes-are-dangerous.html). :fire: :fire: :fire: I'm fine with a toggle so that anybody, who wants to risk it, can go with them. But, I'd prefer just one toggle and...

I would still favor one pre-configured liveness probe that works for the operator and have only one toggle for users to switch.

I talked with @sdudoladov back when I opened this PR. I think he was more in favor for adding another config parameter. I could also think of taking the resources...

@nmlc did you upgrade by editing the deployment? Are you also using the latest Spilo image? Have you updated the cluster roles, too?

@blyry thanks for the detailed feedback (also thanks @nielsmeima for giving the hint). Hm, that sounds like had a working default in place before v1.5.0, but I cannot think of...

@travnewmatic thanks for the feedback. Maybe you link to increase our docs in a PR? :smiley:

Hm, which Spilo version are you using, @arbe ?

I wonder why there are different WAL backup paths listed in the logs? * s3://some-s3-name/spilo/mydb-postgresql/ * s3://some-s3-name/spilo/simplrapi-postgresql/ * s3://postgres-wal-develop/mydb/simplrapi-postgresql/ What do you have configured for `wal_s3_bucket`? Can you create a...

So have you initialized a new clone and checked that it can read this backup? The clone is in the same AWS account, right?