Covers networking in Kubernetes.
The charter defines the scope and governance of the Network Special Interest Group.
- Regular SIG Meeting: Thursdays at 14:00 PT (Pacific Time) (biweekly). Convert to your timezone.
The Chairs of the SIG run operations and processes governing the SIG.
- Casey Davenport (@caseydavenport), Tigera
- Dan Williams (@dcbw), Red Hat
- Tim Hockin (@thockin), Google
The following subprojects are owned by sig-network:
- external-dns
- Owners:
- Contact
- Slack: #external-dns
- ingress
- kube-dns
- network-policy
- pod-networking
- services
The below teams can be mentioned on issues and PRs in order to get attention from the right people. Note that the links to display team membership will only work if you are a member of the org.
Team Name | Details | Description |
---|---|---|
@kubernetes/sig-network-api-reviews | link | API Changes and Reviews |
@kubernetes/sig-network-bugs | link | Bug Triage and Troubleshooting |
@kubernetes/sig-network-feature-requests | link | Feature Requests |
@kubernetes/sig-network-misc | link | General Discussion |
@kubernetes/sig-network-pr-reviews | link | PR Reviews |
@kubernetes/sig-network-proposals | link | Design Proposals |
@kubernetes/sig-network-test-failures | link | Test Failures and Triage |
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: