Use Merido to Create Network Services for Telco Use Cases Using Secondary...
summary
Meridio is an open‑source project that builds on Network Service Mesh and Linux kernel features (Kubernetes 1.21 baseline) to give pods a tapa sidecar gRPC endpoint, create a logical trench per use case, and announce virtual IPs called whips via BGP so external traffic is attracted to secondary interfaces. It preserves the primary CNI, avoids NAT (same VIP for ingress and egress), classifies/steers flows (example: DNS UDP vs TCP), and targets high‑performance user‑plane and telco needs with minimal app changes — deploy sidecar, define trench/flow/conduit, and traffic lands at the pod.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03What is Merido
- 3:05Secondary networking in Kubernetes
- 4:07Sidecar traffic control
- 6:16Telecom industry requirements for Kubernetes workloads
- 8:01Merido telco use cases
- 11:51Traffic segregation with trenches
- 13:18Traffic classification examples
- 18:18Key takeaways
- 21:13References
- 21:57Q&A
related talks
10mLightning Talk: NSM, Network Service Mesh at Scale for Telco Networking
26mNetworking the Service Mesh Proxy: Where We Are, Where We’re Going
43mService Mesh and the future of networking
43mService MESH without the MESS
37mService MESH without the MESS - Raymond de Jong
20mNetwork Service Mesh
35mService Mesh use cases for Telco and Edge
33mMircoservices the right way: an introduction to Istio