The Service Mesh Interface (SMI) is a specification for service meshes that run on Kubernetes. It defines a common standard that can be implemented by a variety of providers. This allows for both standardization for end-users and innovation by providers of Service Mesh Technology. SMI enables flexibility and interoperability, and covers the most common service mesh capabilities.
The following documents are available:
| Latest Release | Working Draft | |
|---|---|---|
| Core Specification: | ||
| SMI Specification | v0.5.0 | v0.6.0-WD |
| Specification Components | ||
| Traffic Access Control | v1alpha2 | v1alpha3-WD |
| Traffic Metrics | v1alpha1 | v1alpha2-WD |
| Traffic Specs | v1alpha3 | v1alpha4-WD |
| Traffic Split | v1alpha3 | v1alpha4-WD |
- Consul Connect*: service segmentation (consul.io/docs/connect)
- Flagger: progressive delivery operator (flagger.app)
- Istio*: connect, secure, control, observe (servicemeshinterface/smi-adapter-istio)
- Linkerd: ultralight service mesh (linkerd.io)
- Maesh: simpler service mesh (mae.sh)
- Meshery: the service mesh management plane (layer5.io/meshery)
- Rio: application deployment engine (rio.io)
- Service Mesh Hub: unified dashboard (solo.io/products/service-mesh-hub)
- Open Service Mesh: lightweight and extensible cloud native service mesh (openservicemesh.io)
* via adaptor
- Community Meeting: every other Wednesday at 10:00-10:30 Pacific: https://zoom.us/my/cncfsmiproject
Sign up for CNCF Slack
Please refer to CONTRIBUTING.md for more information on contributing to the specification.
Whether you are a user or contributor, you can open issues on GitHub:
Service Mesh Interface follows the CNCF Code of Conduct.