- Regular SIG Meeting: Tuesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone.
The Chairs of the SIG run operations and processes governing the SIG.
- Dawn Chen (@dchen1107), Google
- Derek Carr (@derekwaynecarr), Red Hat
The following subprojects are owned by sig-node:
- cri-containerd
- cri-o
- cri-tools
- frakti
- kubelet
- node-feature-discovery
- node-problem-detector
- rktlet
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.
The google groups contain the archive of Github team notifications. Mentioning a team on Github will CC its group. Monitor these for Github activity if you are not a member of the team.
Team Name | Details | Google Groups | Description |
---|---|---|---|
@kubernetes/sig-node-api-reviews | link | link | API Changes and Reviews |
@kubernetes/sig-node-bugs | link | link | Bug Triage and Troubleshooting |
@kubernetes/sig-node-feature-requests | link | link | Feature Requests |
@kubernetes/sig-node-pr-reviews | link | link | PR Reviews |
@kubernetes/sig-node-proposals | link | link | Design Proposals |
@kubernetes/sig-node-test-failures | link | link | Test Failures and Triage |
Topics include, but are not limited to:
- Kubelet related features (e.g. Pod lifecycle)
- Node level performance and scalability (with sig-scalability)
- Node reliability
- Node lifecycle management (with sig-cluster-lifecycle)
- Container runtimes: docker, rkt, etc.
- Images, package management
- Resource management (with sig-scheduling)
- Issues related to monitoring (with sig-instrumentation)
- Node level security and Pod isolation (with sig-auth)
- Kernel interactions (to a limited extent)
- ...
We also work closely with sig-storage and sig-networking. As you can see, this is a very cross-functional team!