Node Special Interest Group

Meetings

• Regular SIG Meeting: Tuesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone.
  • Meeting notes and Agenda.
  • Meeting recordings.

Leadership

Chairs

The Chairs of the SIG run operations and processes governing the SIG.

• Dawn Chen (@dchen1107), Google
• Derek Carr (@derekwaynecarr), Red Hat

Contact

• Slack
• Mailing list
• Open Community Issues/PRs

Subprojects

The following subprojects are owned by sig-node:

• cri-o
  • Owners:
    • https://raw.githubusercontent.com/kubernetes-sigs/cri-o/master/OWNERS
• cri-tools
  • Owners:
    • https://raw.githubusercontent.com/kubernetes-sigs/cri-tools/master/OWNERS
• frakti
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/frakti/master/OWNERS
• kubelet
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/kubernetes/master/cmd/kubelet/OWNERS
    • https://raw.githubusercontent.com/kubernetes/kubernetes/master/pkg/kubelet/OWNERS
• node-feature-discovery
  • Owners:
    • https://raw.githubusercontent.com/kubernetes-sigs/node-feature-discovery/master/OWNERS
• node-problem-detector
  • Owners:
    • https://raw.githubusercontent.com/kubernetes/node-problem-detector/master/OWNERS
• rktlet
  • Owners:
    • https://raw.githubusercontent.com/kubernetes-incubator/rktlet/master/OWNERS

GitHub Teams

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-node-api-reviews	link	API Changes and Reviews
@kubernetes/sig-node-bugs	link	Bug Triage and Troubleshooting
@kubernetes/sig-node-feature-requests	link	Feature Requests
@kubernetes/sig-node-pr-reviews	link	PR Reviews
@kubernetes/sig-node-proposals	link	Design Proposals
@kubernetes/sig-node-test-failures	link	Test Failures and Triage

Goals

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!