Merge pull request #2065 from derekwaynecarr/sig-node-charter

[RFC] SIG-Node initial charter
This commit is contained in:
k8s-ci-robot 2018-08-23 19:44:21 -07:00 committed by GitHub
commit e340fb5685
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 91 additions and 12 deletions

View File

@ -77,19 +77,23 @@ Monitor these for Github activity if you are not a member of the team.
<!-- BEGIN CUSTOM CONTENT -->
## Goals
Topics include, but are not limited to:
The following topics fall under scope of this SIG.
* Kubelet related features (e.g. Pod lifecycle)
* Node level performance and scalability (with [sig-scalability](../sig-scalability))
* Node reliability
* Node lifecycle management (with [sig-cluster-lifecycle](../sig-cluster-lifecycle))
* Container runtimes: docker, [rkt](../sig-rktnetes), etc.
* Images, package management
* Resource management (with [sig-scheduling](../sig-scheduling))
* Issues related to monitoring (with [sig-instrumentation](../sig-instrumentation))
* Node level security and Pod isolation (with [sig-auth](../sig-auth))
* Kernel interactions (to a limited extent)
* ...
- Kubelet and its features
- Pod API and Pod behaviors (with [sig-architecture](../sig-architecture))
- Node API (with [sig-architecture](../sig-architecture))
- Node controller
- Node level performance and scalability (with [sig-scalability](../sig-scalability))
- Node reliability (problem detection and remediation)
- Node lifecycle management (with [sig-cluster-lifecycle](../sig-cluster-lifecycle))
- Container runtimes
- Device management
- Image management
- Node-level resource management (with [sig-scheduling](../sig-scheduling))
- Hardware discovery
- Issues related to node, pod, container monitoring (with [sig-instrumentation](../sig-instrumentation))
- Node level security and Pod isolation (with [sig-auth](../sig-auth))
- Host OS and/or kernel interactions (to a limited extent)
We also work closely with [sig-storage](../sig-storage) and [sig-network](../sig-network). As you can see, this is a very cross-functional team!
<!-- END CUSTOM CONTENT -->

75
sig-node/charter.md Normal file
View File

@ -0,0 +1,75 @@
# SIG Node Charter
This charter adheres to the conventions described in the [Kubernetes Charter README] and uses
the Roles and Organization Management outlined in [sig-governance].
## Scope
SIG Node is responsible for the components that support the controlled
interactions between pods and host resources. We manage the lifecycle of pods
that are scheduled to a node. We focus on enabling a broad set of workload
types, including workloads with hardware specific or performance sensitive requirements. We maintain
isolation boundaries between pods on a node, as well as the pod and the host. We
aim to continuously improve node reliability.
### In scope
SIG [readme]
#### Code, Binaries and Services
- Kubelet and its features
- Pod API and Pod behaviors (with [sig-architecture](../sig-architecture))
- Node API (with [sig-architecture](../sig-architecture))
- Node controller
- Node level performance and scalability (with [sig-scalability](../sig-scalability))
- Node reliability (problem detection and remediation)
- Node lifecycle management (with [sig-cluster-lifecycle](../sig-cluster-lifecycle))
- Container runtimes
- Device management
- Image management
- Node-level resource management (with [sig-scheduling](../sig-scheduling))
- Hardware discovery
- Issues related to node, pod, container monitoring (with [sig-instrumentation](../sig-instrumentation))
- Node level security and Pod isolation (with [sig-auth](../sig-auth))
- Host OS and/or kernel interactions (to a limited extent)
#### Cross-cutting and Externally Facing Processes
- CRI [validation] and [testing policy]
- Node [test grid] and [perf dashboard]
### Out of scope
- network management ([sig-network](../sig-network))
- persistent storage management ([sig-storage](../sig-storage))
## Roles and Organization Management
This sig adheres to the Roles and Organization Management outlined in [sig-governance]
and opts-in to updates and modifications to [sig-governance].
### Additional responsibilities of Chairs
- Technical leads seeded by legacy SIG chairs from existing subproject owners
### Additional responsibilities of Tech Leads
None
### Deviations from [sig-governance]
None
### Subproject Creation
SIG Technical Leads
[validation]: https://github.com/kubernetes/community/blob/master/contributors/devel/cri-validation.md
[testing policy]: https://github.com/kubernetes/community/blob/master/contributors/devel/cri-testing-policy.md
[test grid]: https://k8s-testgrid.appspot.com/sig-node#Summary
[perf dashboard]: http://node-perf-dash.k8s.io/#/builds
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md
[readme]: https://github.com/kubernetes/community/tree/master/sig-node
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md