Service Mesh Interface 

Lachlan Evenson @LachlanEvenson • Program Manager in Azure Container Compute • Our team is responsible for building and supporting upstream open source projects • Kubernetes 1.16 release lead • CNCF Ambassador • Loves learning new languages • We’re Hiring! 

Policy Routing Telemetry Smart endpoints, dumb pipes This has worked for the past 25 years But with so many endpoints today, how do you manage @LachlanEvenson 

Service Mesh technology Smarter pipes @LachlanEvenson 

…and more @LachlanEvenson 

Service Mesh Interface (SMI) for Kubernetes In partnership with @LachlanEvenson 

Service Mesh Interface (SMI) for Kubernetes A Kubernetes interface that provides traffic routing, traffic telemetry, and traffic policy Apps Tooling Ecosystem Standardized Standard interface for service mesh on Kubernetes Simplified Basic feature set to address most common scenarios Extensible Support for new features as they become widely available …and more Service Mesh Interface @LachlanEvenson 

What SMI Covers Service Mesh Interface is a specification that covers the most common service mesh capabilities Traffic policy apply policies like identity and transport encryption across services Traffic telemetry capture key metrics like error rate and latency between services Traffic management shift traffic between different services Kubernetes Native The SMI is specified as a collection of Kubernetes Custom Resource Definitions (CRD) and Extension API Servers. Provider Agnostic The goal of the SMI API is to provide a common, portable set of service mesh APIs which a Kubernetes user can use in a provider agnostic manner. @LachlanEvenson 

This isn’t a new concept If the SMI concept sounds familiar, that’s because it is Apps Tooling Ecosystem Ingress @LachlanEvenson 

How is SMI implemented? @LachlanEvenson Adapter Adapter Native 

Meet the APIs @LachlanEvenson Traffic management shift traffic between different services 

Meet the APIs @LachlanEvenson Traffic telemetry capture key metrics like error rate and latency between services 

Meet the APIs @LachlanEvenson Traffic policy apply policies like identity and transport encryption across services 

Demo 

Traffic Access Traffic Metrics Traffic Split Service Mesh Hub 

SMI – Traffic Split 

No content

SMI – Traffic Metrics 

No content

SMI – Traffic Access 

No content

SMI – Service Mesh Hub 

ServiceMeshHub.io Dashboard • Supports the SMI Spec • Unified dashboard for service meshes • Run the Hub on any cluster • Simplifies mesh installation and auto- discovers existing meshes 

ServiceMeshHub.io Extensions • Browse and install from a catalog of 3rd party software to extend your service mesh • Or build a custom extension for your environment (SDK coming soon) Or build your own! 

So, why SMI? Because it’s faster, simpler, and friendlier Get started quickly Simpler is better Ecosystem friendly 

Stabilize current APIs API integrations into Linkerd, Consul and Istio Provide Istio adapters for all SMI APIs Develop more APIs based on community feedback The future of SMI @LachlanEvenson 

smi-spec.io 

Links • https://github.com/deislabs/smi-spec • https://docs.flagger.app/usage/linkerd-progressive-delivery • https://docs.flagger.app/tutorials/flagger-smi-istio • https://github.com/deislabs/smi-adapter-istio • https://github.com/deislabs/smi-metrics • http://servicemeshhub.io/meshes/ @LachlanEvenson