Multi-network Community Sync Meeting for 20250903

The video features a discussion about standardizing multi-networking in Kubernetes communities, comparing different implementations like User Defined Networks (UDN) and pod network approaches 0:01. Key participants share their experiences with different network topologies (layer 2, layer 3, and local net) and the challenges of creating a standardized API that works across implementations 3:19.

Key Takeaways:
• User Defined Networks (UDN) provide an opinionated API addressing the poor user experience of Network Attachment Definitions (NADs) which use JSON blobs 3:19
• Different implementations support various network topologies including layer 2 (flat network), layer 3 (with router), and local net (un-natted) 5:41
• There's a fundamental difference in approaches between cluster-scoped networks (infrastructure representation) and namespace-scoped networks (tenant-based isolation) 21:01
• Collaboration between multiple communities (OVN, Cilium, Calico) is needed to create a standardized multi-networking solution 33:49

The discussion highlights the complexity of creating a unified API for multi-networking in Kubernetes while balancing different implementation needs and maintaining backward compatibility 40:01.

Sources:

• 0:01 Introduction to multi-networking community sync
• 3:19 Explanation of User Defined Networks vs NADs
• 5:41 Network topologies discussion
• 21:01 Cluster-scoped