-
Notifications
You must be signed in to change notification settings - Fork 5.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add a charter for SIG Scheduling #2462
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,68 @@ | ||
# SIG Scheduling 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 Scheduling is responsible for the components that make Pod placement decisions. | ||
We build Kubernetes schedulers and scheduling features for Pods. We design and | ||
implement features that allows users to customize placement of Pods on the nodes | ||
of a cluster. These features include those that improve reliability of workloads, | ||
more efficient use of cluster resources, and/or enforces placement policies. | ||
|
||
### In scope | ||
|
||
SIG [readme] | ||
|
||
#### Code, Binaries and Services | ||
|
||
- Scheduling related features (e.g. Node Affinity) | ||
- Kube-scheduler performance and scalability (with [sig-scalability](../sig-scalability)) | ||
- Kube-scheduler reliability (problem detection and remediation) | ||
- Pod scheduling APIs (with [sig-api-machinery](../sig-api-machinery)) | ||
- Node resource management (with [sig-node](../sig-node)) | ||
- Cluster resource management (with [sig-node](../sig-node)) | ||
- Pod scheduling policies (with [sig-auth](../sig-auth)) | ||
|
||
**This is NOT** a list of specific code locations, | ||
or projects. For those refer to [SIG Subprojects][sig-subprojects]. | ||
|
||
#### Cross-cutting and Externally Facing Processes | ||
|
||
- Kube-scheduler [test grid] and [perf dashboard] | ||
|
||
### Out of scope | ||
|
||
- network management ([sig-network](../sig-network)) | ||
- persistent storage management ([sig-storage](../sig-storage)) | ||
- enforcement of resource quota and other admission policies ([sig-api-machinery](../sig-api-machinery)) | ||
|
||
## 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 | ||
|
||
|
||
[test grid]: https://k8s-testgrid.appspot.com/sig-scheduling#Summary | ||
[perf dashboard]: http://perf-dash.k8s.io/ | ||
[readme]: https://github.com/kubernetes/community/tree/master/sig-scheduling | ||
[sig-governance]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/sig-governance.md | ||
[sig-subprojects]: https://github.com/kubernetes/community/blob/master/sig-scheduling/README.md#subprojects | ||
[Kubernetes Charter README]: https://github.com/kubernetes/community/blob/master/committee-steering/governance/README.md |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: please link to the README.md file here as well for the sig. i think the template had said the sigs.yaml but i have yet to see a stable link work there.
https://github.com/kubernetes/community/blob/master/sig-node/charter.md#in-scope
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
gives an example that had settled on with brian.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
done.