Skip to content

Priority/preemption #268

Closed
Closed
@davidopp

Description

@davidopp

Feature Description

  • One-line feature description (can be used as a release note): A mechanism for imposing a total order on pods, that determines which pods run and which go pending when the cluster is overcomitted, implemented through a priority scheme, preemption of running pods by the default scheduler, having kubelet eviction order take the priority into account, and modifications to the quota mechanism to take priority into account.
  • Primary contact (assignee): @bsalamat
  • Responsible SIGs: @kubernetes/sig-scheduling-feature-requests, @kubernetes/sig-node-feature-requests
  • Design proposal link (community repo): high-level architecture doc (currently under review/discussion/iteration) here; detailed design doc for first chunk is in Design proposal for adding priority to Kubernetes API community#604
  • 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, @derekwaynecarr, @erictune, @k82cn, @timothysc, @wojtek-t
  • Approver (likely from SIG/area to which feature belongs): @davidopp
  • Initial target stage (alpha/beta/stable) and release (x.y): for 1.7 we anticipate having the detailed design, API (alpha), and implementation of kubelet eviction ordering (alpha); some implementation work for the other pieces will hopefully have begun but will not be in 1.7

ref/ kubernetes/kubernetes#22212
cc/ @dchen1107

Note: this feature is intimately related to #269.

Metadata

Metadata

Assignees

Labels

kind/featureCategorizes issue or PR as related to a new feature.sig/nodeCategorizes an issue or PR as relevant to SIG Node.sig/schedulingCategorizes an issue or PR as relevant to SIG Scheduling.stage/betaDenotes an issue tracking an enhancement targeted for Beta statustracked/noDenotes an enhancement issue is NOT actively being tracked by the Release Team

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions