20ae0d0ec5
|
||
|---|---|---|
| .. | ||
| OWNERS | ||
| README.md | ||
| annual-report-2020.md | ||
| annual-report-2021.md | ||
| annual-report-2022.md | ||
| annual-report-2023.md | ||
| charter.md | ||
| role-sig-chair.md | ||
README.md
Network Special Interest Group
Covers networking in Kubernetes.
The charter defines the scope and governance of the Network Special Interest Group.
Meetings
Joining the mailing list for the group will typically add invites for the following meetings to your calendar.
- Gateway API Meeting (Americas): Mondays at 15:00 PT (Pacific Time) (weekly). Convert to your timezone.
- Gateway API Meeting (Europe): Tuesday (starting September 10th 2024)s at 08:00 PT (Pacific Time) (monthly). Convert to your timezone.
- Network Policy API Meeting: Tuesdays at 9:00 PT (Pacific Time) (bi-weekly). Convert to your timezone.
- SIG Network Ingress NGINX Meeting: Thursdays at 8:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- SIG Network Meeting: Thursdays at 09:00 PT (Pacific Time) (biweekly). Convert to your timezone.
- SIG Network Multi-Network Meeting: Wednesdays at 08:00 PT (Pacific Time) (weekly). Convert to your timezone.
Leadership
Chairs
The Chairs of the SIG run operations and processes governing the SIG.
- Michael Zappa (@mikezappa87), Microsoft
- Shane Utt (@shaneutt), Red Hat
- Tim Hockin (@thockin), Google
Technical Leads
The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.
- Antonio Ojea (@aojea), Google
- Dan Winship (@danwinship), Red Hat
- Tim Hockin (@thockin), Google
Emeritus Leads
- Casey Davenport (@caseydavenport)
- Dan Williams (@dcbw)
Contact
- Slack: #sig-network
- Mailing list
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/sig-network-api-reviews - API Changes and Reviews
- @kubernetes/sig-network-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-network-feature-requests - Feature Requests
- @kubernetes/sig-network-misc - General Discussion
- @kubernetes/sig-network-pr-reviews - PR Reviews
- @kubernetes/sig-network-proposals - Design Proposals
- @kubernetes/sig-network-test-failures - Test Failures and Triage
- Steering Committee Liaison: Maciej Szulik (@soltysh)
Working Groups
The following working groups are sponsored by sig-network:
Subprojects
The following subprojects are owned by sig-network:
cluster-proportional-autoscaler
cluster-proportional-vertical-autoscaler
external-dns
- Owners:
- Contact:
- Slack: #external-dns
gateway-api
- Owners:
- Contact:
- Slack: #sig-network-gateway-api
ingress
- Owners:
iptables-wrappers
knftables
- Owners:
kube-dns
- Owners:
multi-network
network-policy
- Owners:
- Contact:
- Slack: #sig-network-policy-api
node-ipam-controller
pod-networking
Areas of Responsibility
SIG Network is responsible for the following Kubernetes subsystems:
- DNS
- Ingress
- Network plugins / CNI
- Network Policy
- Services / kube-proxy
SIG Network is responsible for a number of issues and PRs. A summary can be found through GitHub search:
Documents
Archive
The following are larger efforts which are now archived and historical. They are no longer active, but are kept in an archived state for posterity and maybe be useful as reference materials.
KPNG
"Kube Proxy Next Generation (KPNG)" was an effort to evaluate the potential for a new kube-proxy with an emphasis on modularity and adaptability. Through the project we explored alternatives to our historical kube-proxy architecture and gained a lot of community members through interest in it. The project was very large in scope, and was archived in 2024 after agreement that the community was no longer able to continue focus on it, but it remains important prior art for any future attempts to revise kube-proxy.