Service Mesh Interface (SMI)
is a specification for service meshes that run on Kubernetes. SMI defines a common standard that can be implemented by
a variety of service mesh projects and vendors. SMI’s aim for consistent APIs facilitates Meshery’s same goals,
allowing for users and tools to flourish. As SMI was unveiled at KubeCon + CloudNativeCon Europe 2019, so did Meshery’s compatibility.
This project is community-built and welcomes collaboration!
Join the weekly community meeting on Friday from 10am to 11am Central.
Watch community meeting recordings.
Subscribe to the community calender.
Access the community drive
Join the community on Slack
The Benchmark Specification is a
common format for describing and capturing performance benchmark tests and results. This specification is
currently being advanced through discussion in the Meshery project.
Does Meshery manage service meshes?
Yes, Meshery acts as a management plane to provision and manage the lifecycle of service meshes.
Why do I need to authenticate my social account to use Meshery?
Create your account - avoid having to reconfigure Meshery each time you deploy it.
When you use a social account to authenticate to Meshery, your environment configuration persists from session to session.
Meshery sources from Mixer Prometheus adapter and uses Prometheus node-exporter.
Rank your deployment
- results of performance tests are anonymously collected using the
Service Mesh Performance Benchmark, so that
Meshery may provide the public service of ranking the speed of your deployment against that of the rest of the world's users.
Why use Meshery?
Meshery is an open source, vendor neutral projects that facilitates testing across meshes.
Other performance benchmark tools are not packaged into a mesh testing utility, butare only a load-generators unto their own.