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

Prioritizing nodes based on volume capacity #1845

Open
cofyc opened this issue Jun 3, 2020 · 33 comments
Open

Prioritizing nodes based on volume capacity #1845

cofyc opened this issue Jun 3, 2020 · 33 comments
Assignees
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@cofyc
Copy link
Member

cofyc commented Jun 3, 2020

Enhancement Description

Please to keep this description up to date. This will help the Enhancement Team track efficiently the evolution of the enhancement

ref: kubernetes/kubernetes#83323
ref: volume topology scheduling design proposal

@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Jun 3, 2020
@cofyc
Copy link
Member Author

cofyc commented Jun 3, 2020

/sig storage
/sig scheduling

@k8s-ci-robot k8s-ci-robot added sig/storage Categorizes an issue or PR as relevant to SIG Storage. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jun 3, 2020
@cofyc
Copy link
Member Author

cofyc commented Jun 3, 2020

/assign

@fejta-bot
Copy link

fejta-bot commented Sep 7, 2020

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-testing, kubernetes/test-infra and/or fejta.
/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 Sep 7, 2020
@cofyc
Copy link
Member Author

cofyc commented Sep 7, 2020

/lifecycle fronzen

@msau42
Copy link
Member

msau42 commented Sep 25, 2020

/remove-lifecycle stale
@cofyc do you plan to target an implementation in 1.20?

@k8s-ci-robot k8s-ci-robot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Sep 25, 2020
@cofyc
Copy link
Member Author

cofyc commented Sep 26, 2020

/remove-lifecycle stale

@cofyc do you plan to target an implementation in 1.20?

yes

@msau42
Copy link
Member

msau42 commented Sep 26, 2020

Thanks!

@kubernetes/sig-release can we track this?

@xing-yang xing-yang added this to the v1.20 milestone Sep 26, 2020
@kikisdeliveryservice kikisdeliveryservice added the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 27, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 27, 2020

Thanks!

@kubernetes/sig-release can we track this?

Done!

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 29, 2020

Hi @msau42 @cofyc

Enhancements Lead here, there is no alpha graduation criteria, can you please add as it's not clear what will be delivered? Also can you please clarify in the test plans whether you intend to implement all of those for alpha? or will some come later?

The graduation criteria listed for all phases seems rather vague as well, if you could provide more detail please do.

Note : Enhancements Freeze is October 6th and by that time all KEPs must have test plans & graduation criteria.

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 30, 2020

Hi @cofyc @msau42

Thanks for the PR! It clearly updates the graduation criteria! As a reminder it will need to merge by October 6th

Thanks
Kirsten

Update: it merged!!! yay!

@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Oct 11, 2020

Hey there Hi @cofyc @msau42 👋

Since your Enhancement is scheduled to be in 1.20, please keep in mind the important upcoming dates:
Friday, Nov 6th: Week 8 - Docs Placeholder PR deadline
Thursday, Nov 12th: Week 9 - Code Freeze

As a reminder, please link all of your k/k PR as well as docs PR to this issue so we can track them.

Thanks!
Kirsten

@eagleusb
Copy link
Member

eagleusb commented Oct 22, 2020

Hello @cofyc 👋, 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo.

This PR can be just a placeholder at this time and must be created before Nov 6th

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

@cofyc
Copy link
Member Author

cofyc commented Oct 23, 2020

Hello @cofyc 👋, 1.20 Docs shadow here.

Does this enhancement work planned for 1.20 require any new docs or modification to existing docs?
If so, please follows the steps here to open a PR against dev-1.20 branch in the k/website repo.

This PR can be just a placeholder at this time and must be created before Nov 6th

Also take a look at Documenting for a release to get yourself familiarize with the docs requirement for the release.

Thank you!

Thanks!

@eagleusb
Copy link
Member

eagleusb commented Nov 2, 2020

Hey @cofyc 👋

The docs placeholder deadline is almost here.

Please make sure to create a placeholder PR against the dev-1.20 branch in the k/website before the deadline.

Also, please keep in mind the important upcoming dates:

As a reminder, please link all of your k/k PR as well as docs PR to this issue for the release team to track.

Thanks !

@cofyc
Copy link
Member Author

cofyc commented Nov 3, 2020

@eagleusb PTAL kubernetes/website#24858

@cofyc
Copy link
Member Author

cofyc commented Nov 9, 2020

@msau42 @xing-yang can you move this KEP to the 1.21 milestone?
I've submitted a PR: kubernetes/kubernetes#96347 but may not finish the tests before the code freeze.

@xing-yang xing-yang modified the milestones: v1.20, v1.21 Nov 9, 2020
@jrsapi
Copy link

jrsapi commented Mar 4, 2021

Greetings @cofyc,

A friendly reminder that Code freeze is 5 days away, March 9th EOD PST
Any enhancements that are NOT code complete by the freeze will be removed from the milestone will require an exception to be added back.
Please also keep in mind that if this enhancement requires new docs or modification to existing docs, you'll need to follow the steps in the Open a placeholder PR doc to open a PR against k/website repo by March 16th EOD PST.
Thanks!

@cofyc
Copy link
Member Author

cofyc commented Mar 9, 2021

Hey @cofyc just to confirm the Enhancements team is currently tracking kubernetes/kubernetes#96347 as the sole k/k PR for inclusion in the 1.21 release. Code Freeze is March 9th as a quick reminder. Please let me know if there are any other in-flight PR(s) we should be tracking against.

kubernetes/kubernetes#99594 API changes PR is WIP.

It's close to the deadline and we don't have time to review API changes. API PR (kubernetes/kubernetes#99594) is delayed to the next release cycle.

@annajung annajung added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Mar 9, 2021
@annajung annajung removed this from the v1.21 milestone Mar 9, 2021
@cofyc
Copy link
Member Author

cofyc commented Mar 11, 2021

hi, @annajung
the main PR (kubernetes/kubernetes#96347) was merged. The new API field is optional. Can you add this feature back to the track list and v1.21 milestone?

@annajung
Copy link
Member

annajung commented Mar 11, 2021

Hi @cofyc, ah sorry, I misunderstood. I thought you meant the enhancement is deferred to the next cycle. will add this back to the tracking sheet. sorry for the confusion!

@annajung annajung added tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team and removed tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team labels Mar 11, 2021
@annajung annajung added this to the v1.21 milestone Mar 11, 2021
@JamesLaverack JamesLaverack added tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team and removed tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team labels Apr 25, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Jul 26, 2021

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

@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 Jul 26, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Aug 26, 2021

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR 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 Aug 26, 2021
@msau42
Copy link
Member

msau42 commented Aug 26, 2021

/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 Aug 26, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Nov 24, 2021

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle stale
  • Mark this issue or PR as rotten with /lifecycle rotten
  • Close this issue or PR 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 Nov 24, 2021
@k8s-triage-robot
Copy link

k8s-triage-robot commented Dec 24, 2021

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

This bot triages issues and PRs 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 or PR as fresh with /remove-lifecycle rotten
  • Close this issue or PR 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 Dec 24, 2021
@cofyc
Copy link
Member Author

cofyc commented Dec 24, 2021

/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 Dec 24, 2021
@cofyc
Copy link
Member Author

cofyc commented Dec 24, 2021

/lifecycle frozen

@k8s-ci-robot k8s-ci-robot added the lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. label Dec 24, 2021
@rhockenbury
Copy link

rhockenbury commented Oct 1, 2022

/milestone clear

@k8s-ci-robot k8s-ci-robot removed this from the v1.21 milestone Oct 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. sig/storage Categorizes an issue or PR as relevant to SIG Storage. stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team
Projects
None yet
Development

No branches or pull requests