The State of the Cloud Native Network: Deep-dive from TAG-Network
summary
Cloud native networking centers on one CNI per cluster that gives every pod a flat L3 IP plus isolation via NetworkPolicies and service discovery via Services/CoreDNS; edge uses load balancers (KGB, BFE) and L7 Ingress controllers (Contour, Emissary). Service meshes add Envoy as ubiquitous L7 proxy with mTLS, tracing, circuit breakers and dynamic WASM extensions. Cross-cluster L3 appears via Submariner for cluster‑to‑cluster tunnels, while Network Service Mesh lets individual pods request bespoke network services (SR‑IOV, VPNs) across clusters; Meshery and Nighthawk provide multi‑mesh testing and benchmarks.
AI-written summary · about
chapters (6)
- 0:00Start
- 2:42Workloads
- 8:38Cluster Edge
- 17:31Service Mesh Adjacent
- 20:32Envoy and Friends
- 29:01Network Service Mesh: Think Different
related talks
27mCNCF TAG Network and Cloud Native Network Landscape
37mPanel Discussion: Cloud Native Networking State of the Union
40mCloud, Kubernetes, and Service Networking - Taming the Turtles
39mIntro: Network Service Mesh (NSM)
31mFrom CNI to Service Mesh: Demystifying Kubernetes Networking
35mNext-level Kubernetes Networking with Cilium - Nico Meisenzahl and Philip Welz
01h 28mSIG-Network Intro & Deep-Dive
35mIntro: Network Service Mesh (NSM)