From TA: > My advice for running Postgres in Kubernetes is then to: > - Rely on PostgreSQL replication to synchronize the state within and across Kubernetes c

From TA: > My advice for running Postgres in Kubernetes is then to: > - Rely on PostgreSQL replication to synchronize the state within and across Kubernetes clusters – in Kubernetes lingo: choose application level replication (Postgres), instead of storage level replication > - Fully exploit availability zones in Kubernetes, instead of “siloing” data centers in separate Kubernetes clusters, in order to automatically achieve zero data loss with very low RTO high availability within a single region, out-of-the-box [deploy across multiple availability zones within at least one region]