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

Run multiple Scheduling Profiles #1451

Closed
alculquicondor opened this issue Jan 14, 2020 · 52 comments
Closed

Run multiple Scheduling Profiles #1451

alculquicondor opened this issue Jan 14, 2020 · 52 comments
Assignees
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. stage/beta Denotes an issue tracking an enhancement targeted for Beta status tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team

Comments

@alculquicondor
Copy link
Member

alculquicondor commented Jan 14, 2020

Enhancement Description

/sig scheduling

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

alculquicondor commented Jan 14, 2020

/assign

@k8s-ci-robot k8s-ci-robot added 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 Jan 14, 2020
@palnabarun
Copy link
Member

palnabarun commented Jan 15, 2020

Hey there @alculquicondor -- 1.18 Enhancements shadow here. I wanted to check in and see if you think this Enhancement will be graduating to alpha in 1.18?

The current release schedule is:

  • Monday, January 6th - Release Cycle Begins
  • Tuesday, January 28th EOD PST - Enhancements Freeze
  • Thursday, March 5th, EOD PST - Code Freeze
  • Monday, March 16th - Docs must be completed and reviewed
  • Tuesday, March 24th - Kubernetes 1.18.0 Released

To be included in the release,

  1. The KEP PR must be merged
  2. The KEP must be in an implementable state
  3. The KEP must have test plans and graduation criteria.

If you would like to include this enhancement, once coding begins please list all relevant k/k PRs in this issue so they can be tracked properly. 👍

We'll be tracking enhancements here: http://bit.ly/k8s-1-18-enhancements

Thanks! :)

@palnabarun palnabarun added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Jan 15, 2020
@palnabarun
Copy link
Member

palnabarun commented Jan 15, 2020

/stage alpha

@k8s-ci-robot k8s-ci-robot added the stage/alpha Denotes an issue tracking an enhancement targeted for Alpha status label Jan 15, 2020
@alculquicondor
Copy link
Member Author

alculquicondor commented Jan 15, 2020

Hi @palnabarun. I believe we can graduate to alpha in 1.18. There is already general consensus in kubernetes/kubernetes#85737

@palnabarun
Copy link
Member

palnabarun commented Jan 15, 2020

Thank you @alculquicondor for the update. I will update the tracking sheet accordingly.

@palnabarun
Copy link
Member

palnabarun commented Jan 15, 2020

Please do note that before the Enhancements Freeze on January 28th, the KEP PR should be merged, the KEP should be in an implementable state and have test plans and graduation criteria.

@palnabarun
Copy link
Member

palnabarun commented Jan 15, 2020

/milestone v1.18

@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 15, 2020
@palnabarun palnabarun 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 Jan 15, 2020
@palnabarun
Copy link
Member

palnabarun commented Jan 21, 2020

@alculquicondor Just a friendly reminder, we are just 7 days away from the Enhancement Freeze (Tuesday, January 28th).

The KEP is still in provisional state and is missing test plans and graduation criteria.

@alculquicondor
Copy link
Member Author

alculquicondor commented Jan 21, 2020

Thanks @palnabarun, I just sent #1483 for review

@palnabarun
Copy link
Member

palnabarun commented Jan 21, 2020

Awesome @alculquicondor! :)

@palnabarun
Copy link
Member

palnabarun commented Jan 21, 2020

As an added note, I am updating the issue comment with the KEP PR.

@palnabarun
Copy link
Member

palnabarun commented Jan 26, 2020

Hi @alculquicondor, just a friendly reminder, we are just 2 days away from the Enhancement Freeze (3 PM Pacific Time, Tuesday, January 28th).

@palnabarun
Copy link
Member

palnabarun commented Jan 28, 2020

@alculquicondor I see that your KEP PR has been merged and satisfies all criteria for making it past the Enhancements Freeze.

I am going ahead and switching the status to Tracked.

@palnabarun
Copy link
Member

palnabarun commented Jan 28, 2020

Also, FYI, whenever you start working on this, please reference the k/k and docs PR's here for us to track.

@palnabarun
Copy link
Member

palnabarun commented Feb 5, 2020

Hi @alculquicondor, just a friendly reminder that the Code Freeze will go into effect on Thursday 5th March.

Can you please link all the k/k PRs or any other PRs which should be tracked for this enhancement?

Thank You :)

@alculquicondor
Copy link
Member Author

alculquicondor commented Feb 5, 2020

Will do. I'm actively working on this, but I don't have open PRs yet.

@palnabarun
Copy link
Member

palnabarun commented Feb 5, 2020

@alculquicondor Thank you for the update. Let us know here when you have PRs that we should track.

@VineethReddy02
Copy link

VineethReddy02 commented Feb 5, 2020

Hello, @alculquicondor, I'm 1.18 docs lead.
Does this enhancement work planned for 1.18 require any new docs (or modifications to existing docs)? If not, can you please update the 1.18 Enhancement Tracker Sheet (or let me know and I'll do so)
If so, just a friendly reminder we're looking for a PR against k/website (branch dev-1.18) due by Friday, Feb 28th, it can just be a placeholder PR at this time. Let me know if you have any questions!

@alculquicondor
Copy link
Member Author

alculquicondor commented Feb 5, 2020

We will have docs. I will send the PR next week :)

@alculquicondor
Copy link
Member Author

alculquicondor commented Jun 2, 2020

kubernetes/website#21437 WIP docs

@msedzins
Copy link

msedzins commented Jun 16, 2020

Hi, @alculquicondor

This is a follow-up to the communication that went out to k-dev today. There has been a revision to the release schedule of v1.19 as follows.

Thursday, July 9th: Week 13 - Code Freeze
Thursday, July 16th: Week 14 - Docs must be completed and reviewed
Tuesday, August 25th: Week 20 - Kubernetes v1.19.0 released
Thursday, August 27th: Week 20 - Release Retrospective

You can find the revised Schedule in the sig-release Repo

Please let me know if you have any questions. 🖖

@msedzins
Copy link

msedzins commented Jul 8, 2020

Hi @alculquicondor, from what I can see all k/k PRs for this enhancement has been already merged so it's ready for Code freeze deadline which happens July 9th.
Please let me know if you think otherwise and there are any risks for that enhancement to be included in v.1.19.

@alculquicondor
Copy link
Member Author

alculquicondor commented Jul 8, 2020

Correct, it is finalized for 1.19

@kikisdeliveryservice kikisdeliveryservice removed the tracked/yes Denotes an enhancement issue is actively being tracked by the Release Team label Sep 11, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 11, 2020

/milestone clear

(removing this enhancement issue from the v1.19 milestone as the milestone is complete)

@k8s-ci-robot k8s-ci-robot removed this from the v1.19 milestone Sep 11, 2020
@kikisdeliveryservice
Copy link
Member

kikisdeliveryservice commented Sep 13, 2020

Hi @alculquicondor

Enhancements Lead here. I see that this is planned to graduate in 1.21? Can you confirm that this is still correct and that you aren't graduating in 1.20?

Thanks!
Kirsten

@alculquicondor
Copy link
Member Author

alculquicondor commented Sep 14, 2020

Correct 1.21 is accurate. This is tied to #785

@kikisdeliveryservice kikisdeliveryservice added the tracked/no Denotes an enhancement issue is NOT actively being tracked by the Release Team label Sep 14, 2020
@fejta-bot
Copy link

fejta-bot commented Dec 13, 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 Dec 13, 2020
@alculquicondor
Copy link
Member Author

alculquicondor commented Dec 14, 2020

/remove-lifecycle stale

Probably going to graduate to GA in 1.22, though

@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 Dec 14, 2020
@fejta-bot
Copy link

fejta-bot commented Mar 14, 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 Mar 14, 2021
@zvonkok
Copy link

zvonkok commented Mar 15, 2021

@alculquicondor Do you have a valid link for your KEP?

@alculquicondor
Copy link
Member Author

alculquicondor commented Mar 15, 2021

Updated the description with it

@fejta-bot
Copy link

fejta-bot commented Apr 14, 2021

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

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

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 Apr 14, 2021
@fejta-bot
Copy link

fejta-bot commented May 14, 2021

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented May 14, 2021

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

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

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. stage/beta Denotes an issue tracking an enhancement targeted for Beta 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

9 participants