Resisting Component Failure Using HA Clusters

In the previous chapter, we looked at how to enable Linkerd or Istio service mesh add-ons and inject sidecars into a sample application. We also looked at the dashboards that allow us to look at telemetry data in order to troubleshoot, manage, and improve applications. We then looked at how metrics, distributed traces, and access logs can help with overall service mesh observability. We additionally looked at some of the most common service mesh use cases today, as well as some recommendations for how to choose the correct service mesh. We also covered a list of service mesh configuration best practices.

Through the use of dynamic container scheduling, Kubernetes offers higher reliability and resiliency for distributed applications. But how can you ensure that Kubernetes itself remains operational when a component, or even an entire data center site, fails? In this chapter, we will look into our next use case on how to configure Kubernetes...