community/sig-node
Jordan Buchman a3a0cf288b
Change sig-networking to sig-network
2018-08-14 15:11:42 -06:00
..
OWNERS Add sig labels and use aliases in OWNERS files 2017-10-27 09:34:18 -07:00
README.md Change sig-networking to sig-network 2018-08-14 15:11:42 -06:00

README.md

Node Special Interest Group

Meetings

Leadership

Chairs

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

Contact

Subprojects

The following subprojects are owned by sig-node:

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.

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 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

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-network. As you can see, this is a very cross-functional team!