I concur. There was supposedly a migration path from their postgresql image & chart to the postgresql-ha image & chart.

Aside of having to re-mount the data disk and move things around manually; the -ha chart has numerous other issues where it always requires the master to be node-0. And with pods being rescheduled within a statefulset, good look having the master be on node-0. If there was an outage and the master is anywhere else, node-0 will just 'wait' for a master to come online, time out and shoot itself in the head thinking it is in a network partition and that retrying may help.

The algorithm implemented by postgresql-ha turned out to be plain broken. Only able to survive pods neatly shutting down.