Add kerthcet and sanposhiho as SIG scheduling approvers

[alculquicondor]

What type of PR is this?

/kind documentation

What this PR does / why we need it:

/sig scheduling
Add @kerthcet and @sanposhiho as approvers for SIG Scheduling.

They have both been long standing contributors to kube-scheduler.

They have grown to produce high quality code and KEPs and provide meaningful reviews. They are also leading newer contributors to do bugfixes and refactoring.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

I propose that they stay as reviewers for a while. Once we grow the reviewers team, I hope Kensei and Kant can dedicate to their approver role.

Does this PR introduce a user-facing change?

NONE

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[alculquicondor]

/hold
for @ahg-g and @Huang-Wei

[Huang-Wei]

+100.

@kerthcet and @sanposhiho has been served in sig-scheduling for a while. They have demonstrated comprehensive understanding in the whole scheduler codebase, and led design and impl. of various KEPs and impactful PR and issue fixes. Super glad to have them in this sig, and hope they can keep the momentum!

@kerthcet and @sanposhiho, could you compile a review/pr/kep list (statistically) and comment below? You can refer to some other maintainer's proposal PR or https://github.com/kubernetes/community/blob/master/community-membership.md#approver.

[sanposhiho]

Thanks @alculquicondor for bringing this up. I greatly appreciate the support from everyone so far.
I'm really honored to be listed there. I'd like to do my best to contribute even more here in the future with this chance.

could you compile a review/pr/kep list (statistically) and comment below?

Sure.

• I've been a reviewer since May 2022 (ref)
• 44 merged PRs (ref), 6 opened PRs (ref)
• 56 reviewing (ref)
  • Also, see https://docs.google.com/document/d/1miVfTUcj26uc2--l6xjt3Xabln81GrckbEN9WkwPQTg/edit# for more details. (Thanks @alculquicondor for editing them!)
• 2 KEP authored: KEP-3022, KEP-3633

[kerthcet]

Thanks all for your kindness and guidances, sig scheduling is such a cohesive community, so glad to be part of it. I'll devote myself to help the community become better, whatever the quality of codebase, helping new contributors, introducing exciting features, anything benefit to the healthy of the community.

And I will be careful with critical changes and make sure another approver will be involved in.

Here're some contributions I made to the specific sig-scheduling community following the approver requirements:

• Reviewer of the codebase for at least 3 months:
  • I've been a reviewer since June 17th, 2022
• Primary reviewer for at least 10 substantial PRs to the codebase
  • I have reviewed totally 96 PRs up to now, including like:
    • Migrated pkg/scheduler/framework/runtime to use contextual logging
    • scheduler_perf: update throughputCollector
    • scheduler: Update cached Pod any time to make sure the Pod's status is up-to-date
    • Fix a bug that out-of-tree plugin is misplaced when using scheduler v1beta3 config
    • Implement MinDomains on Pod Topology Spread
    • Improve performance of NodeResourcesFit scoring
    • feat(NodeVolumeLimits): return Skip in PreFilter
    • Migrated pkg/scheduler/framework/plugins/podtopologyspread to contextual logging
    • Migrated pkg/scheduler/framework/plugins/noderesources to contextual logging
    • fix pod created failed when resource request is 0
    • ...
• Reviewed or merged at least 30 PRs to the codebase
  • Beside reviewing, I have merged totally 75 PRs up to now, including like KEPs, features, bugfixees, cleanups, some of them:
    • Improve integration test performance in scheduler
    • Add NodeInclusionPolicy to TopologySpreadConstraint in PodSpec
    • Refactor schedulingCycle and bindingCycle in scheduler
    • Graduate component config to stable in kube-scheduler
    • nodeAffinity filtered nodes should be excluded when calculating skew
    • ...

I also help to maintain two sub-projects kueue and kube-scheduler-wasm-extension the same time.

Thanks again for all your support.

[ahg-g]

+1; Thanks @kerthcet and @sanposhiho for your contributions and commitment to the project.

[alculquicondor]

/hold cancel
/assign @dims

[dims]

@Huang-Wei @ahg-g @alculquicondor need some approve/lgtm(s) from you all

[alculquicondor]

/approve

[dims]

/approve

[alculquicondor]

/hold cancel
/lgtm

[k8s-ci-robot]

@alculquicondor: you cannot LGTM your own PR.

In response to this:

/hold cancel
/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[Huang-Wei]

/lgtm
/approve

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: 01db4c73187e17cb06c255f0c80d7092cdc11cc5

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alculquicondor, dims, Huang-Wei

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [dims]

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