3 ms·
It's not Kubernetes specific and that is actually addressed in the article! It's not postgres specific either. It will happen whenever you have a cluster or H
by emmelaich 9y ago
It's not Kubernetes specific and that is actually addressed in the article!
It's not postgres specific either. It will happen whenever you have a cluster or HA solution which is not intimately cognizant of the app it is supporting.
Shit, it is hard enough to get any database extremely reliable even with their own solutions (Oracle RAC, Postgres SLONY, mysql replication).
Adding Kubernetes / Docker to that mix makes for an interesting life. Caution is advised.