Service Mesh documentation¶
A service mesh is a dedicated infrastructure layer that manages service-to-service communication in microservice architectures. It provides capabilities like traffic management, security, and observability without requiring changes to application code. However, service meshes are complex systems that require significant time to learn and deep understanding to operate effectively.
The Canonical Service Mesh leverages application modeling fro [Juju](https://juju.is/) to simplify service mesh operations. By using charms and relations, complex configurations like creating authorization policies, on-boarding [Kubernetes](https://kubernetes.io/) applications onto the mesh, and managing traffic routing are automated, reducing operational overhead and the potential for misconfiguration. This approach makes service mesh technology more accessible while maintaining the full power of the underlying platform.
For Platform Engineers and DevOps teams, Canonical Service Mesh provides a turn-key, out-of-the-box solution for improved microservice communication, security, and observability.
Note
Currently, Canonical Service Mesh offers Charmed Istio in ambient mode
In this documentation¶
Get started - a hands-on introduction the Canonical Service Mesh.
Step-by-step guides - learn key operations and customization.
Discussion and clarification of key topics and concepts
Technical information - specifications, APIs, architecture