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.

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.

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

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

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

• 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: Paco Xu 徐俊杰 (@pacoxu)

The following working groups are sponsored by sig-node:

• WG Batch
• WG Device Management
• WG Policy
• WG Serving
• WG Structured Logging

The following subprojects are owned by sig-node:

• Owners:
  • kubernetes/kubernetes/test/e2e/common
  • kubernetes/kubernetes/test/e2e/common/node
  • 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

• Owners:
  • kubernetes/cri-api
  • kubernetes/kubernetes/staging/src/k8s.io/cri-api
  • kubernetes/kubernetes/staging/src/k8s.io/cri-api/pkg

• Owners:
  • kubernetes/cri-client
  • kubernetes/kubernetes/staging/src/k8s.io/cri-client

• Owners:
  • kubernetes-sigs/cri-tools

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

• Owners:
  • kubernetes/kubernetes/cmd/kubelet
  • kubernetes/kubernetes/pkg/kubelet
  • kubernetes/kubernetes/pkg/probe
  • kubernetes/kubernetes/pkg/security/apparmor
  • kubernetes/kubernetes/staging/src/k8s.io/component-helpers/node

• Owners:
  • kubernetes/api/node
  • kubernetes/kubernetes/staging/src/k8s.io/api/node

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

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

• Owners:
  • kubernetes-sigs/dra-example-driver
  • kubernetes-sigs/noderesourcetopology-api
  • kubernetes/kubernetes/pkg/controller/resourceclaim
  • kubernetes/kubernetes/pkg/scheduler/framework/plugins/dynamicresources
  • kubernetes/kubernetes/staging/src/k8s.io/dynamic-resource-allocation
  • kubernetes/kubernetes/staging/src/k8s.io/kubelet/pkg/apis/dra
  • kubernetes/kubernetes/test/e2e/dra
  • kubernetes/kubernetes/test/e2e/testing-manifests/dra

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

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!