Skip to content
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.

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

[Scheduler] Update out-of-date devel docs #7300

Open
kerthcet opened this issue May 17, 2023 · 9 comments
Open

[Scheduler] Update out-of-date devel docs #7300

kerthcet opened this issue May 17, 2023 · 9 comments
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@kerthcet
Copy link
Member

Describe the issue

Some documentation under contributors/devel/sig-scheduling is out-of-date, we should update them. e.g. https://github.com/kubernetes/community/blob/master/contributors/devel/sig-scheduling/scheduler_queues.md

/sig scheduling

@k8s-ci-robot k8s-ci-robot added the sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. label May 17, 2023
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle stale
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

@k8s-ci-robot k8s-ci-robot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 20, 2024
@k8s-triage-robot
Copy link

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

  • After 90d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

  • Mark this issue as fresh with /remove-lifecycle rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

@k8s-ci-robot k8s-ci-robot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 19, 2024
@kerthcet
Copy link
Member Author

/remove-lifecycle rotten

@k8s-ci-robot k8s-ci-robot removed the lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. label Feb 20, 2024
@Surajkumar98012
Copy link

hey i am new to open source but i want to contribute in this , can you guide me what to do

@kerthcet
Copy link
Member Author

kerthcet commented Apr 3, 2024

Do you familiar with kube scheduler, if not, this is a little hard for you because the doc is about the mechanism under the scheduler.

@Surajkumar98012
Copy link

yeah, I am familiar with Kube scheduler, I learnt about this when I am deep dive into the k8s architecture.

@kerthcet
Copy link
Member Author

kerthcet commented Apr 3, 2024

Basically, we have several changes to the scheduling queue:

  • unschedulingQ -> unschedulingPods
  • queueingHint introduced in the recent releases(beta but disabled by default)
  • changed some metrics
  • changed the background periodical flushing time

I think what we want to do here is just make the document updated with the latest changes.

@Surajkumar98012
Copy link

Got it,
let me try, what I can do about it

@Surajkumar98012
Copy link

so, I think I need to compare it and update it with latest changes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
Status: Needs Triage
Development

No branches or pull requests

4 participants