This is not the right approach. First, ReadWriteMany implementations (which depend on your cluster) might not guarantee the sort of POSIX filesystem consistenc

This is not the right approach. First, ReadWriteMany implementations (which depend on your cluster) might not guarantee the sort of POSIX filesystem consistency that databases expect. Second, does Postgres in read-only replica expect to be run on a read-only, possibly-changing volume? What's the consistency model then? The standard way of doing this is to run a single postgres instance on a single PVC/PV (that replicates across the cluster anyway), letting the cluster move the pod if it dies. In addition, you can run read-only postgres replicas for some semblance of read-only HA while the master reschedules on failure. You can also go deeper into faster failover mechanisms (without having the k8s scheduler in the hot path of that) using any of the tons of postgres HA systems.