Skip to content

annual-report-2025.md

Latest commit

 

History

History
208 lines (165 loc) · 11.4 KB

annual-report-2025.md

File metadata and controls

208 lines (165 loc) · 11.4 KB
Raw

2025 Annual Report: SIG Network

Current initiatives and Project Health

  1. What work did the SIG do this year that should be highlighted?

  • DRANET

    • DRANET is a Kubernetes Network Driver that uses Dynamic Resource Allocation (DRA) to deliver high-performance networking for demanding applications in Kubernetes.
    • DRANET has reached v1.0.1

  • Gateway API Inference Extensions (GIE)

    • Reached v1.0 milestone!
    • Shipped important features: LoRA Syncer, Flow Control, Standalone EPP
    • Latest release v1.3.1

  • Gateway API

  • Network Policy

    • Work continues on finalizing a cluster administrator oriented API:
      • APIs AdminNetworkPolicy and BaselineNetworkPolicy are now combined into a single ClusterNetworkPolicy resource.
      • Finalized Beta candidate API for ClusterNetworkPolicy.
      • Three working ecosystem implementations of the API

  • External DNS

    • Shipped five releases in 2025: v0.16, v0.17, v0.18, v0.19, v0.20
    • Latest release v0.20.0

  • IP Masq Agent

  • Cluster Proportional Autoscaler

  • Multi-Network

    • Work continues on the API definition using DRA as the integration point.

  • Ingress-NGINX

    • Project is being [retired][nginx-retirement] due to challenges with security vulnerabilities and sufficient maintainership.
    • By the end of March 2026, maintenance will be halted, and the project will be retired. Existing deployments of Ingress NGINX will not be broken. Existing project artifacts such as Helm charts and container images will remain available. [nginx-retirement]: https://kubernetes.io/blog/2025/11/11/ingress-nginx-retirement/

  • InGate

    • InGate is being retired (early 2026). SIG Network and the Security Response Committee recommend that all users begin migration to Gateway API or another Ingress controller immediately.

  • Blixt

    • Blixt was an experimental load balancer using eBPF and written in Rust. The project was an experimental sandbox and had no plans to ever be a shipping product. It has now been retired.
  1. 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:

  • Network Policy APIs can use end user feedback to help us graduate towards Beta and GA.

  • Multi-Network would like to refine their set of use cases with feedback from users and the community. There are pieces of a reference implementation of the multi-network API that would benefit from more contributors.

  • 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
    • Agentic and AI workstreams would benefit from feedback and implementations from the community to validate design decisions.
  • DRANET
    • DRANET welcomes additional implementations and feedback from the community for different high-performance networking drivers.
  1. Did you have community-wide updates in 2025 (e.g. KubeCon talks)?

Blog posts:

Talks:

  1. KEP work in 2025 (v1.33, v1.34, v1.35):

Subprojects

New in 2025:

  • kindnet
  • kube-agentic-networking
  • kubernetes-network-drivers
  • wg-ai-gateway

Continuing:

  • cluster-proportional-autoscaler
  • cluster-proportional-vertical-autoscaler
  • external-dns
  • gateway-api
  • gateway-api-inference-extension
  • ingate
  • ingress
  • iptables-wrappers
  • knftables
  • kube-dns
  • multi-network
  • network-policy
  • node-ipam-controller
  • pod-networking

Working groups

New in 2025:

  • AI Gateway
  • Node Lifecycle

Retired in 2025:

  • Policy

Continuing:

  • Device Management
  • Serving
  • Structured Logging

Operational

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 2025 are linked from README.md and updated/uploaded if needed