- What work did the SIG do this year that should be highlighted?
-
Governance and leadership changes
-
Casey Davenport (@caseydavenport) and Dan Williams (@dcbw) stepped down as Chairs, Shane Utt (@shaneutt) and Mike Zappa (@mikezappa87) became new Chairs (joining Tim Hockin (@thockin), who remained a Chair)
-
Dan Winship (@danwinship) and Antonio Ojea (@aojea) became SIG Network's first Tech Leads.
-
-
Gateway API
The Gateway API reached v1.0 and is now GA!. Specifically, the
Gateway
,GatewayClass
, andHTTPRoute
APIs are now v1, with several other APIs also being added or updated in the experimental channel. Also, the old validation webhook is now deprecated in favor of CEL-based validation. See the v1.0.0 release notes for full details.
-
NetworkPolicy API Working Group
The Network Policy API WG mainly focused on the maintenance and new feature development regarding our two major APIs, AdminNetworkPolicy and BaselineAdminNetworkPolicy. This also included a few talks at KubeCon NA 2023 in Chicago:
- Network Policy API: Intro and Project Update
- AdminNetworkPolicy: A New Kubernetes-Native API for Comprehensive Cluster-Wide Network Security
Additionally, major features such as Egress Traffic Control, FQDN Selectors and Network Tenancy all made great progress during the year and we are excited to deliver them here in 2024.
On top of the APIs and Features, we introduced the Policy-Assistant tool which allows users to have a better overview of how all of the native Kubernetes APIs interact on real clusters.
- Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?
The Network Policy API group is always looking for more people to get involved. Whether that's trying out our APIs, updating docs, or helping our with NPEP design, we are hugely appreciative of all help. Please checkout our website for even more information.
Historically, SIG Network as a whole has not been great at onboarding new contributors, but contributions are definitely welcome. (There has recently been a flurry of new-contributor effort around the new nftables kube-proxy backend.)
We also continue to have problems with Windows networking, where most of the people who regularly attend SIG Network meetings know very little about Windows (and most of the people who regularly attend SIG Windows meetings know very little about networking). If you know a lot about Windows container networking (or want to learn) and want to get involved, it would be greatly appreciated.
- Did you have community-wide updates in 2023 (e.g. KubeCon talks)?
We gave a SIG update at KubeCon EU: SIG Network: Intro and Updates.
- KEP work in 2023 (v1.27, v1.28, v1.29):
-
Alpha
-
Beta
-
Stable
- 1669 - Proxy Terminating Endpoints - v1.28
- 2595 - Expanded DNS Configuration - v1.28
- 2681 - Field status.hostIPs added for Pod - v1.30
- 3178 - Cleaning up IPTables Chain Ownership - v1.28
- 3453 - Minimize iptables-restore input size - v1.28
- 3458 - Remove transient node predicates from KCCM's service controller - v1.30
- 3668 - Reserve Nodeport Ranges For Dynamic And Static Port Allocation - v1.29
- 3705 - Cloud Dual-Stack --node-ip Handling - v1.30
- 3726 - standard-application-protocols - v1.27
(This list is auto-generated and has reminded us that we should probably update our list of subprojects...)
Continuing:
- cluster-proportional-autoscaler
- cluster-proportional-vertical-autoscaler
- external-dns
- gateway-api
- ingress
- iptables-wrappers
- kpng
- kube-dns
- network-policy
- pod-networking
(This list is also auto-generated and is even less accurate than the above list...)
Retired in 2023:
- Multitenancy
Continuing:
- IoT Edge
- 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 2023 are linked from README.md and updated/uploaded if needed