DevOps Articles

The Rush to Fix the Kubernetes Failover Problem

Services and clusters will certainly fail on Kubernetes, and all too often, the unfortunate SRE or operations person will get that call in the middle of the night to manually fix it. While Kubernetes does indeed offer a failover mechanism it is not automated in such a way that in the event of a cluster or a service failure, the services are instantly transferred to a replica cluster configuration where they resume functionality. A new automated failover functionality for https://linkerd.io/ gives Linkerd the ability to automatically redirect all traffic from a failing or inaccessible service to one or more replicas of that service — including replicas on other clusters, Buoyant’s https://co.linkedin.com/in/alpeb, a senior software developer, wrote in a https://linkerd.io/2022/03/09/announcing-automated-multi-cluster-failover-for-kubernetes/.

The push to automate the failover functionality of Kubernetes supports the original conept of policy-driven application placement, Volk said.

The main issue is how Kubernetes does not provide an automated failover functionality in the event of a failure.