Service Mesh Interface: Developer Friendly APIs for Service Mesh
summary
SMI defines Kubernetes CRDs (for example TrafficSplit CRD) and ships a SMI Go SDK so tools can programmatically control meshes; demos show applying a TrafficSplit to move 50/50 traffic shift and 90/10 then back to 100% between v1 and v2 services. An operator called the sto adapter watches SMI CRDs and configures Istio and Linkerd clusters; Flagger and other tools already integrate, and the demo traffic routing works as expected.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:16About Michelle
- 1:06Push to Production
- 1:34Breaking Production
- 2:04Building Running Distributed Systems
- 3:05Service Mesh Explosion
- 5:54Collaboration
- 7:09Service Mesh Interface
- 7:38Custom Resource Definitions
- 9:42Traffic Split Demo
related talks
08mDemocratizing Service Mesh on Kubernetes
28mService Mesh: Demystifying Istio
43mService Mesh for developers
58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...
53mService Mesh: What, Why, And How?
39mDo you need a Service Mesh?
33mMircoservices the right way: an introduction to Istio
34mService Mesh for Developers
