Run multiple Scheduling Profiles

[alculquicondor]

Enhancement Description

• One-line enhancement description (can be used as a release note): Let the scheduler run multiple scheduler profiles associated to a scheduler name.
• Kubernetes Enhancement Proposal: https://git.k8s.io/enhancements/keps/sig-scheduling/1451-multi-scheduling-profiles
  • Main repo issue: Scheduler with multiple plugin configurations kubernetes#85737
• Primary contact (assignee): @alculquicondor
• Responsible SIGs: sig-scheduling
• Enhancement target (which target equals to which milestone):
  • Alpha release target (1.18)
  • Beta release target (1.19)
  • Stable release target (1.21)

/sig scheduling

[alculquicondor]

/assign

[palnabarun]

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]

/stage alpha

[alculquicondor]

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

[palnabarun]

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

[palnabarun]

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]

/milestone v1.18

[palnabarun]

@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]

Thanks @palnabarun, I just sent #1483 for review

[palnabarun]

Awesome @alculquicondor! :)

[palnabarun]

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

[palnabarun]

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

[palnabarun]

@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]

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

[palnabarun]

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]

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

[palnabarun]

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

[VineethReddy02]

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]

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

[alculquicondor]

kubernetes/website#21437 WIP docs

[msedzins]

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]

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]

Correct, it is finalized for 1.19

[kikisdeliveryservice]

/milestone clear

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

[kikisdeliveryservice]

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]

Correct 1.21 is accurate. This is tied to #785

[fejta-bot]

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

[alculquicondor]

/remove-lifecycle stale

Probably going to graduate to GA in 1.22, though

[fejta-bot]

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

[zvonkok]

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

[alculquicondor]

Updated the description with it

[fejta-bot]

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

[fejta-bot]

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]

@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.