sig-node

Node Special Interest Group

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.

Meetings

Joining the mailing list for the group will typically add invites for the following meetings to your calendar.

• Main SIG Meeting: Tuesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone.
  • Meeting notes and Agenda.
  • Meeting recordings.
• Weekly CI/Triage Meeting: Wednesdays at 10:00 PT (Pacific Time) (weekly). Convert to your timezone.
  • Meeting notes and Agenda.

Leadership

Chairs

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

• Sergey Kanzhelev (@SergeyKanzhelev), Google
• Mrunal Patel (@mrunalp), Red Hat

Technical Leads

The Technical Leads of the SIG establish new subprojects, decommission existing subprojects, and resolve cross-subproject technical issues and decisions.

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

Contact

• 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
• Steering Committee Liaison: Tim Pepper (@tpepper)

Working Groups

The following working groups are sponsored by sig-node:

• WG Batch
• WG Multitenancy
• WG Policy
• WG Structured Logging

Subprojects

The following subprojects are owned by sig-node:

ci-testing

• Owners:
  • kubernetes/kubernetes/test/e2e/common
  • kubernetes/kubernetes/test/e2e/node
  • kubernetes/kubernetes/test/e2e_node
  • kubernetes/test-infra/config/jobs/kubernetes/sig-node
  • kubernetes/test-infra/config/testgrids/kubernetes/sig-node
  • kubernetes/test-infra/jobs/e2e_node
• Contact:
  • Mailing List

cri-api

• Owners:
  • kubernetes/cri-api

cri-tools

• Owners:
  • kubernetes-sigs/cri-tools

kernel-module-management

• Owners:
  • kubernetes-sigs/kernel-module-management

kubelet

• Owners:
  • kubernetes/kubernetes/cmd/kubelet
  • kubernetes/kubernetes/pkg/kubelet

node-api

• Owners:
  • kubernetes/api/node

node-feature-discovery

• Owners:
  • kubernetes-sigs/node-feature-discovery-operator
  • kubernetes-sigs/node-feature-discovery

node-problem-detector

• Owners:
  • kubernetes/node-problem-detector
  • kubernetes/test-infra/config/jobs/kubernetes/node-problem-detector
• Contact:
  • Slack: #node-problem-detector

resource-management

• Owners:
  • kubernetes/kubernetes/staging/src/k8s.io/dynamic-resource-allocation
  • kubernetes-sigs/dra-example-driver
  • kubernetes/noderesourcetopology-api

security-profiles-operator

• Owners:
  • kubernetes-sigs/security-profiles-operator
• Contact:
  • Slack: #security-profiles-operator

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!