Network QoS Support for Kubernetes Applications
summary
Kubernetes lacks traffic shaping when using CNI, so a simple CNI plugin using Linux tc implements both ingress and egress rate limiters with burst support and attaches limits via pod annotations. The implementation is upstreamed to the CNI community and is integrating with SIG‑Network. Demo uses iperf and shows per‑pod limits (examples: 30 KB/s and 10 KB/s bursts) enforced across the default path of four gateways, and the limiter works in the test setup.
AI-written summary · about
chapters (14)
- 0:00Start
- 0:52Kubernetes Networking Overview
- 3:24CNI: Container Network Interface
- 4:55Why Need Network QoS Support
- 8:07Basic Network QoS Implementations
- 9:07QoS within a Network Element
- 13:04QoS in Linux with TC and Filters
- 15:27Linux TC Sample Commands
- 17:40CNI Bandwidth Plugin
- 19:28Sample Config of Bandwidth Plugin
- 21:53Integrating With Kubernetes
- 23:35Workflow of Limit Pod's Bandwidth
- 24:32KBS Support Traffic Shaping in v1.12
- 25:24Demo
related talks
36mNetwork-aware Scheduling in Kubernetes
33mKubernetes Networking: How to Write a CNI Plugin From Scratch
36mNetwork Bandwidth-Aware Kubernetes Cluster
08mA Time sensitive Network CNI plugin for Embedded and Edge
36mNetwork Bandwidth-Aware Kubernetes Cluster
40mKubernetes Networking Panel: Collaborate on the Spec, Compete on Execution
37mKubernetes and the CNI: Where We Are and What's Next - Casey Callendrello, CoreOS
35mNext-level Kubernetes Networking with Cilium - Nico Meisenzahl and Philip Welz