A multi-mesh management plane with initial functionality as a playground to faciliate learning about functionality and performance of different service meshes. Meshery also serves as a service mesh performance benchmark.
In an effort to produce service mesh agnostic tooling, Meshery uses a common performance benchmark specification to capture and share environment information and test configuration. As a Service Mesh Interface (SMI) partner, Meshery participates in advancing service mesh adoption through standardization of APIs.
If you’re using Meshery or if you like the project, please ★ star this repository to show your support! 🤩
Meshery is intended to be a vendor and project-neutral utility for uniformly benchmarking the performance of service meshes. Between service mesh and proxy projects (and surprisingly, within a single project), a number of different tools and results exist.
A service mesh playground to faciliate learning about functionality of different service meshes. Meshery incorporates a visual interface for manipulating traffic routing rules. Sample applications will be included in Meshery.
See the project site for quick start instructions and project documentation for a complete set of Meshery documentation.
- KubeCon EU 2019 | (video, deck)
- Istio Founders Meetup @ KubeCon EU 2019 | deck
- Cloud Native Rejekts EU 2019 | deck
- DockerCon 2019 Open Source Summit | deck, video
- Container World 2019 | deck
- Service Mesh Day | deck, video
- Innotech San Antonio | deck
- CNCF Networking WG | deck, video
- Join weekly community meeting on Fridays from 10am - 11am Central.
- Watch community meeting recordings.
- Access the community drive.
- Comment on the design document.
Not sure where to start? Grab an open issue with the help-wanted label.
- Functionality
- Running Meshery
- Quick start
- Docs
- Community Drive (Request access!)
- Contributing
This repository and site are available as open source under the terms of the Apache 2.0 License.
About Layer5
Layer5.io is a service mesh community, serving as a repository for information pertaining to the surrounding technology ecosystem (service meshes, api gateways, edge proxies, ingress and egress controllers) of microservice management in cloud native environments.