Kubernetes split-brain / HA across AZ

10/2/2017

The Kubernetes HA documentation shows that you can ensure availability in the case of the failure of an apiserver by having multiple instances behind a load balancer.

However, it doesn't cover what happens if the Kubernetes is deployed across multiple availability zones. There is some documentation here but it doesn't really go into failure scenarios.

What is best practice here? Should you pin the api-servers to instances inside each AZ? What happens in the event of a split brain? If I have a pod running in one AZ and it becomes unavailable to the rest of the world, what happens to it?

I specifically want to know about a custom on-premise installation, not AWS or GCE.

-- John
kubernetes
kubernetes-health-check

0 Answers