Summary
The number of services that make up an application grows dramatically as monolithic apps are split down into microservices. And managing a huge number of entities isn’t easy. By standardizing and automating communication between services, a Kubernetes native service mesh, such as Istio or Linkerd, tackles difficulties created by container and service sprawl in a microservices architecture. Security, service discovery, traffic routing, load balancing, service failure recovery, and observability are all standardized and automated by a service mesh.
In this chapter, we learned how to enable the Linkerd and Istio add-ons and inject sidecars into sample applications. Then, we examined the respective dashboards, which allowed us to examine telemetry data to debug, maintain, and improve applications. We also examined how metrics, distributed traces, and access logs can be used to improve overall service mesh observability.
After that, we looked at some of the most prevalent...
