How to perform key day-2 operations on Tanzu Service Mesh
At this point, we have a distributed application successfully working across two Kubernetes clusters. If you were doing this in a real production environment, there are some day-2 concerns you’d want to address. For example, it’s great that the catalog service can run on a separate cluster, but what if that cluster goes down? How could we load balance across instances on multiple clusters?
Furthermore, we’re living in a world where deployment, upkeep, measuring, and monitoring of services are often the responsibility of Site Reliability Engineers (SREs). If you were the SRE for Acme Fitness, you would have already identified Service-Level Indicators (SLIs) and defined SLOs for your services. Tanzu Service Mesh greatly simplifies this by allowing you to define your SLIs and SLOs right in the Tanzu Service Mesh UI and measure how your services are meeting those SLOs using real-time metrics.
