Batch job admission and flexible resource allocation

[davidopp]

Feature Description

• One-line feature description (can be used as a release note): Batch job admission and flexible resource allocation
• Primary contact (assignee): @k82cn, @foxish
• Responsible SIGs: @kubernetes/sig-scheduling-feature-requests @kubernetes/sig-apps-feature-requests
• Design proposal link (community repo): high-level architecture doc (currently under review/discussion/iteration) here; detailed design doc to be forthcoming once there is iteration and agreement on the high level design
• Reviewer(s) - (for LGTM) recommend having 2+ reviewers (at least one from code-area OWNERS file) agreed to review. Reviewers from multiple companies preferred: @davidopp, @erictune, @foxish, @k82cn, @timothysc
• Approver (likely from SIG/area to which feature belongs): @davidopp, @erictune, @timothysc
• Initial target stage (alpha/beta/stable) and release (x.y): unclear what, if anything, will be finished in time for 1.7, but it would be alpha in any event

ref/ kubernetes/kubernetes#36716

Note: This feature is intimately related to #268.

[davidopp]

I put the 1.7 label on this but realistically we will just be working on it during 1.7 (starting with getting consensus on the design) and it's unclear what from this, if anything, will actually ship in 1.7.

[k82cn]

/assign @k82cn, @foxish

[davidopp]

I'm going to move this to next-milestone since we don't anticipate having any code for it in Kubernetes 1.7. (But @k82cn is working in his own repo on it.)

[doprdele]

Any chance this will make it into 1.8? Also I can't see the design document. Was it removed from gdocs?

[k82cn]

@doprdele , we have an incubator project for this feature at https://github.com/kubernetes-incubator/kube-arbitrator . It's built out of core.

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

Prevent issues from auto-closing with an /lifecycle frozen comment.

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

[foxish]

/lifecycle frozen

[nehagup]

I would like to take up this project as a part of Gsoc'18. Are there any pre-requisites?

[k82cn]

@nehagup , I think you need to submit application (refer to https://summerofcode.withgoogle.com/how-it-works for more detail). If any more question, please poke me at slack :)

[VineethReddy02]

Hello!!!
I would like to work in batch scheduling for GSOC this year. I am familiar with golang and docker. How can i begin with this project and where can i find resources regarding this project ??

[k82cn]

As we incubated this feature in https://github.com/kubernetes-incubator/kube-arbitrator , and we will upgrade it feature by feature. so I'm going to close this one :)