Skip to content

SIG-Scheduling annual report 2025#8824

Open
sanposhiho wants to merge 3 commits intokubernetes:masterfrom
sanposhiho:patch-3
Open

SIG-Scheduling annual report 2025#8824
sanposhiho wants to merge 3 commits intokubernetes:masterfrom
sanposhiho:patch-3

Conversation

@sanposhiho
Copy link
Member

Which issue(s) this PR fixes:

Fixes #8776

/cc @macsko @dom4ha @BenTheElder

@k8s-ci-robot k8s-ci-robot added the area/annual-reports Issues or PRs related to the annual reports label Feb 6, 2026
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sanposhiho

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. approved Indicates a PR has been approved by an approver from all required OWNERS files. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Feb 6, 2026
@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Feb 6, 2026
- [ ] [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

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

@sanposhiho
Copy link
Member Author

@macsko @dom4ha I know it's very rough at the moment, especially we could add more to 1. What work did the SIG do this year that should be highlighted?, but ptal anyways

Copy link
Member

@dom4ha dom4ha left a comment

Choose a reason for hiding this comment

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

A few that comes to my mind

sanposhiho and others added 2 commits February 7, 2026 19:40
Co-authored-by: Dominik Marciński <gmidon@gmail.com>
@sanposhiho sanposhiho requested a review from dom4ha February 7, 2026 06:41

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

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

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

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.

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

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

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

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

- 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

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

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

Choose a reason for hiding this comment

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

Ok, thanks

@macsko
Copy link
Member

macsko commented Feb 16, 2026

Content lgtm

@dom4ha
Copy link
Member

dom4ha commented Feb 16, 2026

/hold once you're ready
/lgtm

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 16, 2026
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Feb 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. area/annual-reports Issues or PRs related to the annual reports cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. size/S Denotes a PR that changes 10-29 lines, ignoring generated files.

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

2025 Annual Report: SIG Scheduling

7 participants