Real-Time Network Traffic Monitoring for KubeVirt VMs Using OVN...
summary
Real-time packet mirroring is implemented by adding VF representer netdevs into OVS and offloading rules to the NIC via switchdev so VM traffic is copied on-host without touching the VM. Management is Kubernetes-native using a PortMirroring CR that creates mirrors, on-demand scalable functions (SFs) and OVN/OVS rules. Mirroring stays local to the host, uses hardware offload so CPU impact is minimal, supports up to ~256 VFs (SFs consume ~75% of a VF), and has limits: no partial-packet capture or sampling and some hardware/legal constraints.
AI-written summary · about
chapters (14)
- 0:00Real-time VM traffic monitoring
- 1:47GPU-bound VM network traffic
- 3:54Legacy SR-IOV and veth interfaces
- 5:21Switchdev SR-IOV for high-performance
- 7:49Host-based vs switch-based monitoring
- 9:11Legacy SR-IOV limitations
- 11:26Switchdev SR-IOV with VF representers
- 13:36OVS port mirroring for visibility
- 16:04Scalable Functions for mirroring
- 19:15OVN automated mirroring rules
- 20:58Kubernetes-native PortMirroring CRD
- 22:41Limitations and legal considerations
- 24:04Hardware-offloaded monitoring
- 24:46Q&A
related talks
37mHigh Performance Networking with Kubevirt
19mAdvanced Network management with oVirt and OVN
33mMulti-tenant K8s Networking with Kube-OVN
24mDeep Network Traffic Observability with Pktvisor and Prometheus
32mTo InfiniBand and Beyond!
26mRun your Kubernetes cluster on OpenStack in Production
21mMirrorNet: High-fidelity and Scalable Network Emulation for Software-defined WAN
19mThe Easy Button to Kubernetes Networking with Open vSwitch