For container-based applications that need to scale, the capability to analyze the traffic between services is key to optimizing and managing the system. While the service mesh facilitates communication between microservices, the observability of component traffic and health requires more tooling. This is where Service Mesh Manager—an add-on to Cisco Intersight—steps in.
In Episode 54 of DevNet Snack Minute, we talked with Michael Chenetz, the Head of Content, Community, and Events at Cisco DevNet, about Service Mesh Manager.
What is a Service Mesh?
Michael begins by introducing Service Mesh Manager and the problem it addresses. As your infrastructure migrates towards containers—and especially Kubernetes clusters—the need arises to see traffic across those containers and pods. As the number of containers and pods increases, so does your need to gather and correlate that information. You need to see how your workloads are performing. Perhaps you even need to set Service Level Objectives (SLOs).
A service mesh serves as a fabric across multiple clusters, collecting all of this information and facilitating communication between containers and clusters. Service Mesh Manager is an add-on within Cisco Intersight that provides additional observability for your service mesh.
Michael continues by highlighting the advantages of a service mesh. With a variety of different containers and services which need to communicate with one another, a service mesh lets you abstract away that functionality which is common across your services. One example of a commonality is the use of mTLS for authentication, which removes the developer’s burden of dealing with certificates and secure connections.
Additionally, logging and analytics can be handled at the service-mesh level rather than needing to be built into the application.
Why Service Mesh Manager? A Demo
With all the fundamentals covered, Michael gives a demo of Cisco’s Service Mesh Manager itself. Through the demo, Michael demonstrates the observability provided through the interactive topology map. Michael walks through the live view of services as well as the timeline which allows viewing the status at any point. Both individual services and the overall topology map can be viewed.
Additionally, Service Mesh Manager allows for the configuration of traffic management through load balancers. To demonstrate this, Michael walks us through a Canary Deployment implementation using Service Mesh Manager.
When compared to Istio—which is a command-line utility only—Service Mesh Manager adds a graphical interface that allows for increased observability as well as quick configuration changes.
We plan to bring Michael back in a later episode for more details, so stay tuned! In the meantime, if you want to learn more about Service Mesh Manager