Democratizing Service Mesh on Kubernetes

on YouTube ↗08m

" summary

Announces the Service Mesh Interface (SMI) — a portable API surface that already covers three concrete features: SMI traffic split (used with Flagger to run an automated canary and shift weights between versions), SMI metrics server (an aggregated API exposing ~five metrics: RPS, latency percentiles, success/failure counts) and SMI traffic policy (mTLS identities and intent-based routing wired into Consul/Istio/Linkerd via adapters). Adapters reconfigure each mesh dynamically, KubeCost and other tools consume the metrics, and the demos show the integrations working end to end.

AI-written summary · about

" chapters (7)

1. 0:00Intro
2. 0:17Smart endpoints dumb pipes
3. 0:54What is Service Mesh
4. 4:22Traffic Split Demo
5. 5:12Traffic Metrics Demo
6. 6:14Traffic Policy Demo
7. 7:25Why SMI

" related talks

• 24mService Mesh Interface: Developer Friendly APIs for Service MeshMichelle Noorali · ServiceMeshCon 2019
• 28mService Mesh: Demystifying IstioJeferson Fernando · DevOpsDays Vitória 2020
• 01h 03mJust what is a "service mesh", and if I get one will it make everything OK?Elton Stoneman · NDC London 2019
• 58mUsing Service Meshes and Kubernetes to Solve Service-to-Service Communications...Ben Hall · NDC Porto 2019
• 39mDo you need a Service Mesh?Matt Turner · DevDays Europe 2019
• 30mA Developer’s Introduction to Service MeshRosemary Wang · Conf42 Cloud Native 2022
• 34mService Mesh for DevelopersAbdellfetah Sghiouar · DevDays Europe 2022
• 53mService Mesh: What, Why, And How?Flynn · DevOpsDays Boston 2017