diff options
| -rw-r--r-- | sig-scheduling/annual-report-2021.md | 105 |
1 files changed, 56 insertions, 49 deletions
diff --git a/sig-scheduling/annual-report-2021.md b/sig-scheduling/annual-report-2021.md index 0cf9e6c4..2f5d1c03 100644 --- a/sig-scheduling/annual-report-2021.md +++ b/sig-scheduling/annual-report-2021.md @@ -4,15 +4,17 @@ 1. What work did the SIG do this year that should be highlighted? - - - - - - + - Efficient re-queueing of pods, significantly cutting the number of failed scheduling cycles + - Improvements to preemption performance + - Simplified plugin configuration in component config + - Scheduler simulator: https://github.com/kubernetes-sigs/kube-scheduler-simulator 2. What initiatives are you working on that aren't being tracked in KEPs? - - - - - - + - Performance improvements and benchmarking + - Code refactorings and cleanups + - Enhancements to node resource -based scoring (see [101946](https://github.com/kubernetes/kubernetes/pull/101946) and [101822](https://github.com/kubernetes/kubernetes/pull/101822)) + 3. KEP work in 2021 (1.x, 1.y, 1.z): @@ -23,45 +25,47 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files --> - Stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.stable + - [2249 - Multi-scheduling Profiles](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1451-multi-scheduling-profiles) - 1.22 + - [1845 - Prioritization on Volume Capacity](https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1845-prioritization-on-volume-capacity) - 1.22 - Beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.beta + - [2249 - Namespace Selector for Pod Affinity](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2249-pod-affinity-namespace-selector) - 1.22 + - [1923 - Prefer Nominated Node](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/1923-prefer-nominated-node) - 1.22 + - [2458 - Resource Fit Scoring Strategy](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2458-node-resource-score-strategy) - 1.22 + - [2891 - Simplified Scheduler Config](https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/2891-simplified-config/kep.yaml) - 1.22 + - [785 - Scheduler Component Config API](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/785-scheduler-component-config-api) - 1.23 + - [2926 - Job Mutable Scheduling Directives](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/2926-job-mutable-scheduling-directives) - 1.23 - Alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) - $milestone.alpha + - None - Pre-alpha - - [$kep-number - $title](https://git.k8s.io/community/$link/README.md) + - None ## Project health 1. What areas and/or subprojects does your group need the most help with? Any areas with 2 or fewer OWNERs? (link to more details) - - - - - - + - https://github.com/kubernetes-sigs/kube-scheduler-simulator is short of reviewers/owners. 2. What metrics/community health stats does your group care about and/or measure? - - - - - - + - Diversity + - Number of contributors + - Meetings attendance + 3. Does your [CONTRIBUTING.md] help **new** contributors engage with your group specifically by pointing to activities or programs that provide useful context or allow easy participation? - - + - It looks up-to-date 4. If your group has special training, requirements for reviewers/approvers, or processes beyond the general [contributor guide], does your [CONTRIBUTING.md] document those to help **existing** contributors grow throughout the [contributor ladder]? - - + - Nothing special. 5. Does the group have contributors from multiple companies/affiliations? - - + - Yes 6. Are there ways end users/companies can contribute that they currently are not? If one of those ways is more full time support, what would they work on and why? @@ -71,12 +75,12 @@ In future, this will be generated from kubernetes/enhancements kep.yaml files ## Membership -- Primary slack channel member count: -- Primary mailing list member count: -- Primary meeting attendee count (estimated, if needed): -- Primary meeting participant count (estimated, if needed): -- Unique reviewers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> -- Unique approvers for SIG-owned packages: <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Primary slack channel member count: 2529 +- Primary mailing list member count: 586 +- Primary meeting attendee count (estimated, if needed): 10 +- Primary meeting participant count (estimated, if needed): 5 +- Unique reviewers for SIG-owned packages: 6 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> +- Unique approvers for SIG-owned packages: 4 <!-- in future, this will be generated from OWNERS files referenced from subprojects, expanded with OWNERS_ALIASES files --> Include any other ways you measure group membership @@ -87,17 +91,20 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` --> -New in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +New in 2021: +- [kube scheduler simulator](https://github.com/kubernetes-sigs/kube-scheduler-simulator) - -Retired in $YYYY: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) +Retired in 2021: +- None - Continuing: -- [$subproject-name](https://git.k8s.io/community/$sig-id#$subproject-name) -- +- [Descheduler](https://github.com/kubernetes-sigs/descheduler) +- [Scheduler Plugins](https://github.com/kubernetes-sigs/scheduler-plugins) +- [Cluster Capacity](https://github.com/kubernetes-sigs/cluster-capacity) +- [Poseidon](https://github.com/kubernetes-sigs/poseidon) +- [KubeBatch](https://github.com/kubernetes-sigs/kube-batch) ## Working groups @@ -106,32 +113,32 @@ In future, this will be generated from delta of sigs.yaml from $YYYY-01-01 to $Y Manually visible via `git diff HEAD@{$YYYY-01-01} HEAD@{$YYYY-12-31} -- $sig-id/README.md` --> -New in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +New in 2021: +- [Structured Logging](https://github.com/kubernetes/community/tree/master/wg-structured-logging) -Retired in $YYYY: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) + +Retired in 2021: +- None - Continuing: -- [$wg-name](https://git.k8s.io/community/$wg-id/) ([$YYYY report](https://git.k8s.io/community/$wg-id/annual-report-$YYYY.md)) -- +- [Policy](https://github.com/kubernetes/community/tree/master/wg-policy) +- [Multitenancy](https://github.com/kubernetes/community/tree/master/wg-multitenancy) ## Operational Operational tasks in [sig-governance.md]: -- [ ] [README.md] reviewed for accuracy and updated if needed -- [ ] [CONTRIBUTING.md] reviewed for accuracy and updated if needed +- [X] [README.md] reviewed for accuracy and updated if needed +- [X] [CONTRIBUTING.md] reviewed for accuracy and updated if needed (or created if missing and your contributor steps and experience are different or more in-depth than the documentation listed in the general [contributor guide] and [devel] folder.) -- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed -- [ ] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed -- [ ] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed -- [ ] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - - - - +- [x] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed +- [X] SIG leaders (chairs, tech leads, and subproject owners) in [sigs.yaml] are accurate and active, and updated if needed +- [X] Meeting notes and recordings for 2021 are linked from [README.md] and updated/uploaded if needed +- [x] Did you have community-wide updates in 2021 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: + - [2021 KubeCon EU: SIG-Scheduling Intro & Deep Dive](https://sched.co/iE7P) + - [2021 KubeCon NA: SIG-Scheduling Intro & Deep Dive](https://sched.co/lV8m) [CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md [contributor ladder]: https://git.k8s.io/community/community-membership.md |