Noverlay Networks for Health and Wellbeing
summary
Argues that many Kubernetes deployments pile unnecessary overlays and end up with four to five layers of load balancing (envoy sidecars, kube-proxy, ingress, cloud LB) and shows concrete alternatives: OpenStack/OVS-style overlays complicate troubleshooting, WebSocket tunnels like inlets tunneling bypass perimeter firewalls (works but signals org dysfunction), and Calico can advertise service IPs so traffic routes only to nodes with endpoints — Calico external IP routing — removing extra hops and improving performance.
AI-written summary · about
chapters (22)
- 0:00Intro
- 1:00Tigera
- 2:50Plugs
- 3:55Team
- 4:10Lessons from history
- 9:55Today vs Kubernetes
- 11:45Lessons from the past
- 12:15Encapsulation vs Overlay
- 13:42Learning from the past
- 14:25Virtual Gateway
- 16:00Neutron Stack
- 17:28Troubleshooting
- 17:40Microservices
- 17:58Overlay
- 20:19Parameters Firewall
- 21:47Solution for organisations
- 23:56Networking problem
- 24:26The 7layer stack
- 25:52Connectivity to Kubernetes
- 31:07Service Mesh
- 35:55Questions
- 38:18Wrap up
related talks
33mNavigating the Container Jungle
38mKubernetes Networking Infrastructure Offload
25mApplication Networking on Kubernetes, where are we now?
32mUsing Open-Source Software to Secure Cloud-Native Applications
40mKubernetes Networking Panel: Collaborate on the Spec, Compete on Execution
34mUnderstanding the Kubernetes Networking Layer
15mSimplify Kubernetes Connectivity
40mCloud, Kubernetes, and Service Networking - Taming the Turtles