Network Machinery: A United-Front for Network Troubleshooting with CRDs
summary
Proposes a set of Kubernetes CRDs — NetworkTrafficShaper, NetworkConnectivityTest, NetworkMonitor/Control and module validators — that encode troubleshooting actions and results so operators can declare tests and remediation. Demonstrates a network connectivity test CRD doing L3 pings and L4 port checks, injecting 100% packet loss and 200 ms delay via a NetworkTrafficShaper CRD, and an OVS + sFlow demo that raises alerts at thresholds (demo uses 30–100 frames/sec) and programs Open vSwitch flows to block traffic, and the prototype works end-to-end.
AI-written summary · about
chapters (23)
- 0:00Introduction
- 0:15Agenda
- 0:47Network Landscape
- 4:44CRDS
- 5:43Networking Plugins
- 6:35Network Machinery
- 7:30Network Troubleshooting Resources
- 9:04Use Cases
- 10:42Traffic Shaping
- 11:07Demo
- 18:54Network Monitoring
- 19:17OpenFlow
- 23:55Demonstration
- 25:16Configuration Map
- 26:08Demon Step
- 26:50Start Network Monitor
- 27:38Configure Flows
- 28:55Flows Demo
- 31:25Network Notification
- 33:34Recap
- 33:50Network Module Validation
- 34:41Summary
- 35:32Outro
related talks
58mTelco; Networking; Architecture; How to debug; Tips and Tricks
31mCloud Native Network Observability: Treating Routers like Kubernetes Resources
24mAutomating the Deployment of DPDK-based Network Functions on Kubernetes with Fault Tolerance
34mIt's Not Always the Network (But Here's How to Prove It): Kubernetes Packet...
44mHow to Test SDN, or Software‑Defined Networks?
47mNetwork operations management and governance
26mTroubleshooting Kubernetes CRDs is too damn hard
14mMonitoring Network Traffic in Kubernetes