SIG-network: Updates and Future Directions

The SIG-network community in Kubernetes has been working on improving networking aspects of the ecosystem, including pod networking, cluster networking, service abstractions, and network policies. Recent improvements include multi-protocol services, disabling different types of lb ports, and pod lifecycle improvements. The network policy working group has also started discussing a potential version two of the API. The SIG has also started looking at kube-proxy maintenance and a new architecture called kube-proxy next-gen.

• SIG-network covers all networking aspects of the Kubernetes ecosystem
• Recent improvements include multi-protocol services, disabling different types of lb ports, and pod lifecycle improvements
• The network policy working group is discussing a potential version two of the API
• The SIG is looking at kube-proxy maintenance and a new architecture called kube-proxy next-gen

The SIG has been working on improving the functionality of load balancer services by allowing multiple protocols to be supported as part of the load balancer service. This improvement depends on the particular cloud provider, so users should check the port status on their service object. The SIG has also been discussing a potential version two of the network policy API, which would cover issues such as no more defaults and extensibility to other selectors.

This session will be a deep-dive into recent changes in networking in Kubernetes. The talk will provide an overview of current and future projects, including APIs and interfaces (Service, Endpoint[Slice], DNS, Gateway, NetworkPolicy), infrastructure (kube-proxy, IPv4/6 dual-stack. Attendees to this session will come away with a good understanding of the areas covered by sig-network and what the future directions will be.