Anyone here use Patroni for automated high availability with postgres? Does it “just work” or do you need a lot of housekeeping?

We recently rolled out Patroni on k8s and it definitely does not “just work”. I suppose once you get it up and running, there’s some truth to that, but it’s one of the most hostile pieces of software I’ve come across. This isn’t a complaint, after all, Zalando don’t owe me anything. But the documentation, the project structure, the contributors...it all reveals very clearly that this is really just some internal tooling that they happen to make public, as opposed to a first-class OSS project. Unfortunately it’s also the best Postgres HA system out there, but it’s truly a massive PITA to get setup and it’s extremely opinionated about things that it doesn’t need to be.

I'm curious, did you use Patroni directly on Kubernetes or use Zalando's Postgres Operator [1] (based on Patroni)? [1] https://github.com/zalando/postgres-operator