annual-report-2022.md

2022 Annual Report: SIG Scheduling

Current initiatives

1. What work did the SIG do this year that should be highlighted?

   • Improvements to PodTopologySpread API: adding more knobs to control spreading behavior (introducing minDomains and matchLabelKey).
   • Adding more hooks to simplify integrations with external schedulers (mutable pod scheduling directives, pod scheduling readiness)

2. What initiatives are you working on that aren't being tracked in KEPs?

   • Performance improvements.
   • Code refactorings and cleanups.
   • Kueue, a k8s-native job scheduling and queueing controller, a new subproject sponsored by the sig.
   • scheduler-plugins, repository for out-of-tree scheduler plugins.

3. KEP work in 2022 (v1.24, v1.25, v1.26):

• beta:
  • 3022 - Tuning the number of domains in PodTopologySpread - v1.25
  • 3094 - Take taints/tolerations into consideration when calculating PodTopologySpread skew - v1.25
• stable:
  • 1258 - Default Pod Topology Spread - v1.24
  • 1923 - Prefer Nominated Node - v1.24
  • 2249 - Namespace Selector for Pod Affinity - v1.24
  • 785 - Scheduler Component Config API - v1.25
  • 902 - Add NonPreempting Option For PriorityClasses - v1.24

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)

   • Increase the number of reviewers (call for reviewers)

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: 3050
• Primary mailing list member count: 655
• 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 2022:

• kueue
• kwok

Retired in 2022:

• poseidon

Continuing:

• cluster-capacity
• descheduler
• kube-batch
• kube-scheduler-simulator
• scheduler
• scheduler-plugins

Working groups

New in 2022:

• Batch

Continuing:

• Multitenancy
• Policy
• Structured Logging

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 2022 are linked from README.md and updated/uploaded if needed
• Did you have community-wide updates in 2022 (e.g. community meetings, kubecon, or kubernetes-dev@ emails)? Links to email, slides, or recordings: - 2022 KubeCon NA: SIG-Scheduling Intro & Deep Dive - 2022 KubeCon EU: SIG-Scheduling Intro & Deep Dive -