Scheduling Framework

[bsalamat]

Feature Description

• One-line feature description (can be used as a release note): Implement a scheduling framework where many of the existing and future features of the existing scheduler can be written as plug-ins for the scheduler.
• Primary contact (assignee): @bsalamat
• Responsible SIGs: scheduling
• Design proposal link (KEP): https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md
• Link to e2e and/or unit tests:
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @k82cn @misterikkit
• Approver (likely from SIG/area to which feature belongs): @k82cn @bsalamat
• Feature target (which target equals to which milestone):
  • Alpha release target (x.y) 1.15
  • Beta release target (x.y) 1.17
  • Stable release target (x.y)

This is a long term project and requires many changes to the existing scheduler. In order to ensure quality and reliability of the scheduler, we plan to build the features gradually and in steps. The first extension points are targeted for 1.13. We will add more extension points in the future releases. We will prioritize the addition of the extension points based on need for them.

/sig scheduling

[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

[mlmhl]

/remove-lifecycle stale

[claurence]

@bsalamat Hello - I’m the enhancement’s lead for 1.14 and I’m checking in on this issue to see what work (if any) is being planned for the 1.14 release. Enhancements freeze is Jan 29th and I want to remind that all enhancements must have a KEP - I don't see a relevant KEP for this issue can you drop the link to the KEP? Thanks

[bsalamat]

KEP for this enhancement is found at: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/20180409-scheduling-framework.md

[kacole2]

I'm the Enhancement Lead for 1.15. Is this feature going to be graduating alpha/beta/stable stages in 1.15? Please let me know so it can be tracked properly and added to the spreadsheet.

Once coding begins, please list all relevant k/k PRs in this issue so they can be tracked properly.

[justaugustus]

/assign @bsalamat

[bsalamat]

@kacole2 Yes, this feature is going to be alpha in 1.15.
One PR which was merged a while back is referenced above is: kubernetes/kubernetes#70227
Another PR which will be merged soon: kubernetes/kubernetes#75848
I would expect to see a number of more PRs in the new future. I will make sure that they reference this issue.

[kacole2]

/milestone v1.15
/stage alpha

[kacole2]

@bsalamat, After reviewing your KEP, it's currently in a draft state. It must be "implementable" to be included in 1.15. In addition, it's missing test plans and graduation criteria which is required information per the KEP Template. Please update the KEP to include the required information before the Kubernetes 1.15 Enhancement Freeze date of 4/30/2019.

[bsalamat]

@kacole2 Thanks for the reminder. I just sent #1026 to add test plans, graduation criteria, and change status to 'implementable'.

[ahg-g]

/remove-lifecycle stale

[kikisdeliveryservice]

Hi @ahg-g

Enhancements Lead here. Are there any plans to graduate this to beta in 1.20?

Thanks!
Kirsten

[ahg-g]

Hi kikisdeliveryservice@, this feature is not guarded by a feature flag and there is really no notion of versions for this api yet. We may declare this as implemented and graduated in 1.20 and close this issue.

[kikisdeliveryservice]

Thanks @ahg-g ! For now I will track this enhancement and just keep us updated 👍

Best,
Kirsten

[kikisdeliveryservice]

Hi @ahg-g

Any update as to whether this is going to get marked as implemented? I see that you got some agreement on doing so, but want to check.

Thanks
Kirsten

[ahg-g]

I opened an issue for discussion: kubernetes/kubernetes#95037 there doesn't seem to be any objection so far, I will wait few more days and then send a PR to change the KEP to implemented.

[kikisdeliveryservice]

Thanks for the update @ahg-g !!

[ahg-g]

PR for marking this as implemented: #2054

[kikisdeliveryservice]

The above PR merged marking 624 as implemented in 1.19.

Please feel free to close this issue.

Thanks @ahg-g !!

[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

[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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[ahg-g]

/close

This is done.

[k8s-ci-robot]

@ahg-g: Closing this issue.

In response to this:

/close

This is done.

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.