Network Service Mesh
summary
Network Service Mesh claims to provide hybrid multi-cloud L3 IP service mesh connectivity that creates per-workload v-wires between clients and endpoints across clusters, clouds and on‑prem without changing existing Kubernetes or CNIs. It exposes a gRPC API (Request/Close/Monitor) for ephemeral connections with expiry and refresh, supports label-based endpoint selection and multi‑domain registries, and is a CNCF sandbox project since 2019. Concrete uses shown include inter-cluster DB replication and connecting workloads to multiple L7 meshes.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:35Let Me Introduce Myself ANOVA
- 2:04Managing Complexity
- 4:09Where Do L7 Service Meshes Fall Shor
- 5:50Multi/Hybrid Cloud
- 6:23Multi-Corp/Extra-Net
- 6:57Service Mesh Balkanization
- 7:37Multi-Service Mesh
- 8:23Network Service Mesh: Key Concepts
- 11:25Network Service Mesh: Endpoints
- 12:09Network Service Mesh: vWire
- 12:42Network Service Mesh: API
- 13:43Network Service Mesh: Registries
- 15:59Putting it all together
- 16:55Network Service Mesh: What's more?
- 17:42Network Service Mesh: CNCF Project
- 18:31Network Service Mesh: More Resourc
- 19:12Summary
related talks
20mNetwork Service Mesh
39mIntro: Network Service Mesh (NSM)
35mIntro: Network Service Mesh (NSM)
35mIntro: Network Service Mesh (NSM)
09mAn Intro to Network Service Mesh (NSM) and Its Relationship to Service M...
35mDeep Dive: Network Service Mesh (NSM)
43mService Mesh and the future of networking
01h 21mFive Cool Things You Can Do with Network Service Mesh