kubernetes / community

Kubernetes community content
Apache License 2.0
11.98k stars 5.17k forks source link

[Developer Guide Audit] Scheduling #5237

Open mrbobbytables opened 4 years ago

mrbobbytables commented 4 years ago

Documentation is the go-to reference for contributors. Parts of the developer guide have been cited as vastly out of date (e.g. referencing VERY outdated versions of docker). We are asking each SIG that owns a portion of the developer guide to audit their devel guide documentation.

This does not have to include updating it. (although if you want to, please go ahead 😄 )

If you could, update this issue with items that are out of date or you think should be added to the scheduling portion of the devel guide.

Assigning to leads, but please feel free to re-assign and delegate. /assign @Huang-Wei @ahg-g


Parent Tracking Issue: #5229 /sig scheduling /sig contributor-experience /area developer-guide /milestone v1.20

Huang-Wei commented 4 years ago

Thanks Bob for raising this. The docs and source code pointers are really dated, need a polish.

I will see if any volunteer is interested first, so /help

cc/ @adtac in case you want to incorporate https://github.com/kubernetes/kubernetes/issues/91120 into folder https://github.com/kubernetes/community/tree/master/contributors/devel/sig-scheduling.

k8s-ci-robot commented 4 years ago

@Huang-Wei: This request has been marked as needing help from a contributor.

Please ensure the request meets the requirements listed here.

If this request no longer meets these requirements, the label can be removed by commenting with the /remove-help command.

In response to [this](https://github.com/kubernetes/community/issues/5237): >Thanks Bob for raising this. The docs and source code pointers are really dated, need a polish. > >I will see if any volunteer is interested first, so >/help > >cc/ @adtac in case you want to incorporate https://github.com/kubernetes/kubernetes/issues/91120 into folder https://github.com/kubernetes/community/tree/master/contributors/devel/sig-scheduling. Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
adtac commented 4 years ago

sure, I can help with this. I'll open a PR to move the scheduler plugins README to this repo first.

mrbobbytables commented 4 years ago

Awesome, thank you!

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

damemi commented 3 years ago

/remove-lifecycle stale

ingvagabund commented 3 years ago

Will update both https://github.com/kubernetes/community/blob/master/contributors/devel/sig-scheduling/scheduler.md and https://github.com/kubernetes/community/blob/master/contributors/devel/sig-scheduling/scheduler_algorithm.md

mrbobbytables commented 3 years ago

Thanks!

ingvagabund commented 3 years ago

Google docs replacing both docs: https://docs.google.com/document/d/1t2QoASmg_BssFczl8n7UNTDWKgncMSrLTX802fQ0lK8/edit?usp=sharing. Still WIP, we can still borrow bits from the existing docs and put it into the new one.

ingvagabund commented 3 years ago

FYI @ahg-g @Huang-Wei @alculquicondor @damemi ^^

alculquicondor commented 3 years ago

/assign @ingvagabund

Thanks

damemi commented 3 years ago

Google docs replacing both docs: https://docs.google.com/document/d/1t2QoASmg_BssFczl8n7UNTDWKgncMSrLTX802fQ0lK8/edit?usp=sharing. Still WIP, we can still borrow bits from the existing docs and put it into the new one.

@ingvagabund that is an excellent detailed document. I started doing something similar a while back, but have not had time to work on it: https://docs.google.com/document/d/1O78c38_NZcIb0ISJUqzh4u1uHspi6kgm/edit

Please feel free to pick any sections or details from that doc as you see fit to add here :)

fejta-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale

mrbobbytables commented 3 years ago

/remove-lifecycle stale /lifecycle frozen