- What work did the SIG do this year that should be highlighted?
This year we have several highlights from our various sub-projects, these are the major themes and releases:
- External DNS
- Two new reviewers were added this year as the project continues to grow
- Shipped important maintenance release v0.15.x
- Created webhook provider to enable providers running out of tree. Our goal is to move all providers out of tree.
- Ingress NGINX
- Shipped a large number of
v1.x.xpatch and minor releases all the way fromv1.8.xto v1.12.0
- Shipped a large number of
- InGate
- Project just started at the end of 2024 and is starting to plan the roadmap.
- Multi-Network
- Moved away from core development to CRD based addon approach
- Work started on supporting Dynamic Resource Allocation (DRA)
- Network Policy
- Working on getting
AdminNetworkPolicy(ANP) andBaselineAdminNetworkPolicy(BANP) APIs toBeta- Two new implementations joined us this year in supporting the APIs
- Delivered features: FQDN Selectors, Policy Assistant CLI, and Tenancy API
- Work started on Service Account Selectors, and Dry-Run Mode
- Working on getting
- Gateway API
- Delivered GRPCRoute, ParentReference Port, Service Mesh Support and Conformance Profiles and Reports as GA in release v1.1
- Delivered HTTPRoute Timeouts, Gateway Infrastructure Labels, and Backend Protocol Support as GA in release v1.2
- Shipped two releases of our ingress2gateway utility: v0.2.0, v0.3.0
- Shipped our first release of our gwctl utility: v0.1.0
- Gateway API Inference Extensions (GIE)
- Shipped our first release v0.1.0
- Major performance improvement: Reduced output token latency by [15%-60%] when kv cache is close to saturation
- Three new implementations have joined us to help us support the API and move it forward
- IP Masq Agent
- Shipped important maintenance release v2.12.0
- Cluster Proportional Autoscaler
- Shipped important maintenance release v1.9.x
- Blixt
- Started a major rewrite of the control-plane and added L4 Gateway API Support (TCPRoute, UDPRoute)
- Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
While there are no SIG Network projects which couldn't benefit from more help and contributions, the following is a list of specific projects where there are known blockers (or otherwise critical needs) where more contributions, feedback, or implementation support is the key to "unblocking" them:
- InGate is a new project just getting started creating a Gateway API implementation, and needs contributors to join and get to the first release.
- Network Policy could use more implementations to join and support some of our newer APIs (e.g. AdminNetworkPolicy) to help them graduate towards GA.
- MultiNetwork has started anew with CRD based development and is in need of use cases and implementations to join to get to the first release.
- Gateway API
- has a large number of features which are not yet standard which could use implementations to join us to help us graduate those towards GA.
- has two CLI utilities which need more users and implementations to get involved to provide feedback: ingress2gateway, gwctl
- [Gateway API Inference Extension] is a new project which provides AI/ML inference routing and load-balancing features. It is in need of more implementations to bring use cases and and contribute in order to help graduate the APIs towards GA.
- If you're interested in DRA for networking, we started a new CNI driver this year which could use more contributors: cni-dra-driver
- Did you have community-wide updates in 2024 (e.g. KubeCon talks)?
Blog Posts:
Talks:
- Network Policy: The future of Network Policy (Kubecon EU)
- How many network policies can I create? (Kubecon EU)
- Gateway API "Beyond GA" (Kubecon EU)
- Configuring your Service Mesh with Gateway API (Kubecon EU)
- SIG Network Intro & Updates (Kubecon NA)
- Securing the Future of Ingress-NGINX (Kubecon NA)
- Gateway API: What's new, what's next? (Kubecon NA)
- Unlocking the Gateway: A Practical Guide from Ingress to Gateway API (Kubecon NA)
- How to move from Ingress to Gateway API with minimal Hassle (Kubecon NA)
- Live with Gateway API 1.2 (Kubecon NA)
- With Great Flexibility Comes Great Complexity: Inspect your Gateway API Configuration (Kubecon NA)
- CNI Updates & Direction (Kubecon NA)
Webinars:
- KEP work in 2024 (v1.30, v1.31, v1.32):
-
Alpha
-
Beta
-
Stable
- 2681 - Field status.hostIPs added for Pod - v1.30
- 3458 - Remove transient node predicates from KCCM's service controller - v1.30
- 3705 - Cloud Dual-Stack --node-ip Handling - v1.30
- 3836 - Kube-proxy improved ingress connectivity reliability - v1.31
- 1860 - Make Kubernetes aware of the load balancer behaviour - v1.32
- 2433 - Topology Aware Hints - v1.33
New in 2024:
- gateway-api-inference-extension
- ingate
- knftables
- multi-network
- node-ipam-controller
Continuing:
- cluster-proportional-autoscaler
- cluster-proportional-vertical-autoscaler
- external-dns
- gateway-api
- ingress
- iptables-wrappers
- kube-dns
- network-policy
- pod-networking
Retired in 2024:
- kpng
New in 2024:
- Device Management
- Serving
Retired in 2024:
- IoT Edge
Continuing:
- Policy
- Structured Logging
Operational tasks in sig-governance.md:
- README.md reviewed for accuracy and updated if needed
- CONTRIBUTING.md reviewed for accuracy and updated if needed
- Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed
- Subprojects list and linked OWNERS files in sigs.yaml reviewed for accuracy and updated if needed
- SIG leaders (chairs, tech leads, and subproject leads) in sigs.yaml are accurate and active, and updated if needed
- Meeting notes and recordings for 2024 are linked from README.md and updated/uploaded if needed