Did you know that CNI itself isn’t Kubernetes specific? Container Network Interface (CNI) is an API providing a networking solution for containers on Linux and it’s Kubernetes agnostic. Those who deploy network-centric workloads want richer interactions between their workloads and the networking that underpins them. These people are Kubernetes people, and they’re looking for K8s-native ways to interact with CNI. Developers want to perform monitoring, have up-to-date metadata, and interact with CNI configurations. If we don’t have a lingua franca between CNI and K8s we take away commonality between networking implementations and endanger customers with vendor lock-in, and add confusion for admins who have to unravel science experiments. Today CNI sits at a crossroads. There’s SIG-Network’s initiative for k8s multi-networking, Multus CNI’s ability to speak both K8s & CNI, and CNI on the precipice of defining 2.0. Help us save CNI and explore the possibilities for its future.
Daniel is a Principal Software Engineer at the Red Hat’s Office of the CTO. He’s been involved in several networking projects, such as Kuryr-Kubernetes (a CNI plugin which enables native Neutron-based networking in Kubernetes), MetalLB and recently he’s been tackling Edge and... Read More →
30 something year old developer from Portugal, based in Madrid, Spain. Main interests are SDN / NFV, functional programming, containers, and virtualization.
Friday June 16, 2023 3:45pm - 4:20pm CEST
D105 | Talks
Create a custom schedule.
Take it with you on mobile.
Get listed in the directory.
