Keynote: Open Service Mesh - Why, What, How?
summary
Open Service Mesh is a lightweight, Envoy-based service mesh that implements SMI, offers automatic sidecar injection, mTLS, traffic splitting and service-level access controls, and integrates with Flagger for progressive delivery and with Prometheus, Jaeger and Azure Monitor. Managed OSM runs as an AKS add-on or self-installed via osmctl; load tests with ~1,000 services, ~2,000 sidecars and 70,000 RPS show the proxy adds ~2.65 ms latency and uses about 0.35% CPU and 40 MB per 1,000 RPS. Roadmap includes Windows container support and AGIC integration; deployment works end-to-end. AKS add-on managed OSM
AI-written summary · about
chapters (16)
- 0:00Open Service Mesh intro
- 1:07Service mesh architecture
- 3:34Choosing a service mesh
- 6:41Service Mesh Interface
- 11:55What is Open Service Mesh
- 17:10How Open Service Mesh works
- 20:59Sidecar overhead
- 22:42Managed vs self-installed
- 25:31Dapper vs OpenSM
- 27:38OpenSM demo setup
- 33:37Traffic access policies
- 35:00mTLS encryption
- 35:42Traffic splitting & delivery
- 37:49Monitoring & observability
- 38:53OpenSM roadmap
- 40:17Q&A
related talks
34mZero to Secure: Using Open Service Mesh to Easily...
53mDo you need a Service Mesh?
01h 03mJust what is a "service mesh", and if I get one will it make everything OK?
30mIntroduction to Service Mesh for DevOps
30mA Developer’s Introduction to Service Mesh
26mAn Introduction to Service Mesh in Action
34mService Mess to Service Mesh
28mService Mesh: Demystifying Istio