annual-report-2021.md

2021 Annual Report: SIG Scheduling

Current initiatives

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 and 101822)

3. KEP work in 2021 (1.x, 1.y, 1.z):

• Stable
  • 2249 - Multi-scheduling Profiles - 1.22
  • 1845 - Prioritization on Volume Capacity - 1.22
• Beta
  • 2249 - Namespace Selector for Pod Affinity - 1.22
  • 1923 - Prefer Nominated Node - 1.22
  • 2458 - Resource Fit Scoring Strategy - 1.22
  • 2891 - Simplified Scheduler Config - 1.22
  • 785 - Scheduler Component Config API - 1.23
  • 2926 - Job Mutable Scheduling Directives - 1.23
• Alpha
  • None
• Pre-alpha
  • 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?

Membership

• 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
• Unique approvers for SIG-owned packages: 4

Include any other ways you measure group membership

Subprojects

New in 2021:

• kube scheduler simulator

Retired in 2021:

• None

Continuing:

• Descheduler
• Scheduler Plugins
• Cluster Capacity
• Poseidon
• KubeBatch

Working groups

New in 2021:

• Structured Logging

Retired in 2021:

• None

Continuing:

• Policy
• 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 (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: - 2021 KubeCon EU: SIG-Scheduling Intro & Deep Dive - 2021 KubeCon NA: SIG-Scheduling Intro & Deep Dive