Panel: Are We There Yet? Native Kubernetes Networking for Telecom Workloads
Panelat Cloud Native Telco Day Europe 2025 · on Tuesday, 2025-04-01· at 12:55· Level 3 | ICC Capital Suite 10-12·
summary
Kubernetes gains a concrete path for multi-networking by treating network interfaces as schedulable devices: the community layers dynamic resource allocation (DRA) drivers that can attach interfaces, return status (IP and iface name), and surface capacity claims like CAP-5075. Current practice still uses Network Attachment Definition (NAD)/multus hacks and vendor-specific CNIs; two DRA network drivers are in development and native attach is expected to reach GA around 1.34, but services, network policy semantics and cross-cluster portability remain unresolved.
AI-written summary · about
chapters (12)
- 0:00Panel introduction
- 1:24Multi-networking use cases
- 3:58Current solutions fragmentation
- 5:02Kubernetes multi-networking timeline
- 10:03Kubernetes native networking status
- 11:48Multi-networking challenges
- 15:39Need for Kubernetes native solution
- 20:00Dynamic resource allocation
- 25:22Multi-networking usability timeline
- 26:48Multi-networking ecosystem readiness
- 29:17Where to discuss multi-networking
- 31:24Closing remarks
related talks
35mPanel: Kubernetes Networking: Present and Future
31mBreaking the Single-Network Barrier: A Cross-Domain Look at…
40mKubernetes Networking Panel: Collaborate on the Spec, Compete on Execution
27mUncharted Waters: Dynamic Resource Allocation for Networking
37mPanel Discussion: Cloud Native Networking State of the Union
46mMulti - Networking Kubernetes Containers with CNI
31mMayday! CNI Overboard!
26mAdvanced Network Capability for NFV on Kubernetes