SIG Node is responsible for the components that support the controlled interactions between pods and host resources.
The charter defines the scope and governance of the Node Special Interest Group.
- 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
- Slack: #sig-node
- Mailing list
- Open Community Issues/PRs
- GitHub Teams:
- @kubernetes/sig-node-api-reviews - API Changes and Reviews
- @kubernetes/sig-node-bugs - Bug Triage and Troubleshooting
- @kubernetes/sig-node-feature-requests - Feature Requests
- @kubernetes/sig-node-pr-reviews - PR Reviews
- @kubernetes/sig-node-proposals - Design Proposals
- @kubernetes/sig-node-test-failures - Test Failures and Triage
The following subprojects are owned by sig-node:
- Owners:
- Owners:
- Owners:
- Owners:
- Contact:
- Slack: #node-problem-detector
The following topics fall under scope of this SIG.
- Kubelet and its features
- Pod API and Pod behaviors (with sig-architecture)
- Node API (with sig-architecture)
- Node controller
- Node level performance and scalability (with sig-scalability)
- Node reliability (problem detection and remediation)
- Node lifecycle management (with sig-cluster-lifecycle)
- Container runtimes
- Device management
- Image management
- Node-level resource management (with sig-scheduling)
- Hardware discovery
- Issues related to node, pod, container monitoring (with sig-instrumentation)
- Node level security and Pod isolation (with sig-auth)
- Host OS and/or kernel interactions (to a limited extent)
We also work closely with sig-storage and sig-network. As you can see, this is a very cross-functional team!