Skip to content

SIG-Scheduling annual report 2025 #8824

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.

Sign up for GitHub

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

Open
sanposhiho wants to merge 3 commits into
base: master
Choose a base branch
from
+19 −10
Open

SIG-Scheduling annual report 2025 #8824

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
83213a7
SIG-Scheduling annual report 2025
sanposhiho Feb 6, 2026
f7d1199
Update sig-scheduling/annual-report-2025.md
sanposhiho Feb 7, 2026
aadd5ce
more highlighted works
sanposhiho Feb 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 19 additions & 10 deletions sig-scheduling/annual-report-2025.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,14 +12,24 @@
- Governance and leadership changes
-->

- Started Workload Aware Scheduling (aka WAS) initiative
- First implementation of gang scheduling
- Active support for DRA
- Improvements to scheduling performance
- New Chairs and Tech leads

2. Are there any areas and/or subprojects that your group needs help with (e.g. fewer than 2 active OWNERS)?

Copy link
Member Author

@sanposhiho sanposhiho Feb 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@vincentdephily @ingvagabund

Should I put cluster-capacity?

Copy link
Contributor

@ingvagabund ingvagabund Feb 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cluster capacity has been in the maintenance mode for some time. K8s rebases only. There are currently no new features on our roadmap. The current maintenance capacity is sufficient. Thank you for asking.

Copy link
Member Author

@sanposhiho sanposhiho Feb 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, thanks

- [scheduler-plugins](https://github.com/kubernetes-sigs/scheduler-plugins/)
Copy link
Member Author

@sanposhiho sanposhiho Feb 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Huang-Wei I put scheduler-plugins here, unless you don't think we shuold?

Copy link
Member

@Huang-Wei Huang-Wei Feb 12, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yup, it's good to put it here. For current phase, we're short of active maintainers but overall it's good - I do regular release cuttings.
Probably when Workload becomes the atomic scheduling unit, scheduler-plugins will become more active, and let's evaluate how to engage more active maintainers by then.

- [kwok](https://github.com/kubernetes-sigs/kwok)
Copy link
Member Author

@sanposhiho sanposhiho Feb 11, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@wzshiming
I put kwok here, unless you don't think we should?

Copy link
Contributor

@jackfrancis jackfrancis Feb 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cc @elmiko who may have some thoughts and/or referrals of folks who could help out

Copy link
Contributor

@elmiko elmiko Feb 17, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

apologies for the late reply, nothing is coming to my mind immediately. this lgtm

- [kube-scheduler-simulator](https://github.com/kubernetes-sigs/kube-scheduler-simulator/)
- [kube-scheduler-wasm-extension](https://github.com/kubernetes-sigs/kube-scheduler-wasm-extension)

3. Did you have community-wide updates in 2025 (e.g. KubeCon talks)?

<!--
Examples include links to email, slides, or recordings.
-->
- [Kubecon NA maintainer session](https://sched.co/27NlU)
- [Kubecon EU maintainer session](https://sched.co/1td1i)


4. KEP work in 2025 (v1.33, v1.34, v1.35):
<!--
Expand All @@ -30,7 +40,6 @@
Please raise an issue in kubernetes/community, if the KEP metadata is correct but the generated list is incorrect.
-->

<!--
- Alpha
- [4671 - Gang Scheduling](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4671-gang-scheduling) - v1.35
- [4815 - DRA Partitionable Devices](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4815-dra-partitionable-devices) - v1.33
Expand All @@ -54,7 +63,7 @@
- [3094 - Take taints/tolerations into consideration when calculating PodTopologySpread skew](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3094-pod-topology-spread-considering-taints) - 1.33
- [3633 - Introduce MatchLabelKeys and MismatchLabelKeys to PodAffinity and PodAntiAffinity](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3633-matchlabelkeys-to-podaffinity) - v1.33
- [3902 - Decouple TaintManager from NodeLifeCycleController](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/3902-decoupled-taint-manager) - v1.34
- [4247 - Per-plugin callback functions for efficient requeueing in the scheduling queue](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4247-queueinghint) - v1.34 -->
- [4247 - Per-plugin callback functions for efficient requeueing in the scheduling queue](https://github.com/kubernetes/enhancements/tree/master/keps/sig-scheduling/4247-queueinghint) - v1.34

## [Subprojects](https://git.k8s.io/community/sig-scheduling#subprojects)

Expand Down Expand Up @@ -87,12 +96,12 @@
## 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
- [ ] Other contributing docs (e.g. in devel dir or contributor guide) reviewed for accuracy and updated if needed
Copy link
Member Author

@sanposhiho sanposhiho Feb 6, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have an issue, but couldn't work on that until now..
#8289

- [ ] Subprojects list and linked OWNERS files in [sigs.yaml] reviewed for accuracy and updated if needed
- [ ] SIG leaders (chairs, tech leads, and subproject leads) in [sigs.yaml] are accurate and active, and updated if needed
- [ ] Meeting notes and recordings for 2025 are linked from [README.md] and updated/uploaded if needed
- [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 leads) in [sigs.yaml] are accurate and active, and updated if needed
- [x] Meeting notes and recordings for 2025 are linked from [README.md] and updated/uploaded if needed


[CONTRIBUTING.md]: https://git.k8s.io/community/sig-scheduling/CONTRIBUTING.md
Expand Down