Skip to content
KEP Brain

KEP-2458keps/sig-scheduling/2458-node-resource-score-strategy

Preferred Fit Strategy

implementablebetasig-schedulinglatest v1.221 open finding
The default scheduler includes three score plugins (NodeResourcesLeastAllocated, NodeResourcesMostAllocated and RequestedToCapacityRatio) that implement different strategies for preferred resource allocation. Those plugins are mutually exclusive. This KEP proposes to deprecate those plugins and combine them under one Score plugin, the same one used for filt… Full summary

The default scheduler includes three score plugins (NodeResourcesLeastAllocated, NodeResourcesMostAllocated and RequestedToCapacityRatio) that implement different strategies for preferred resource allocation. Those plugins are mutually exclusive. This KEP proposes to deprecate those plugins and combine them under one Score plugin, the same one used for filtering (namely NodeResourcesFit), and add a ScoringStrategy parameter to NodeResourcesFit plugin config that allows users to select which exact scoring strategy to run. <!-- This section is incredibly important for producing high-quality, user-focused documentation such as release notes or a development roadmap. It should be possible to collect this information before implementation begins, in order to avoid requiring implementors to split their attention between writing release notes and implementing the feature itself. KEP editors and SIG Docs should help to ensure that the tone and content of the Summary section is useful for a wide audience. A good summary is probably at least a paragraph in length. Both in this section and below, follow the guidelines of the [documentation style guide]. In particular, wrap lines to a reasonable length, to make it easier for reviewers to cite specific portions, and to minimize diff churn on updates. [documentation style guide]: https://github.com/kubernetes/community/blob/master/contributors/guide/style-guide.md -->

Facts

Authors
@ahg-g
Approvers
@huang-wei
PRR approvers
@wojtek-tbeta
Tracking issue
#2458(opens GitHub in a new tab) closedcompletedclosed 2021-11-18 04:26 UTCmilestone v1.22sig/schedulingstage/betalifecycle/stale
Milestones
beta v1.22stable v1.24
Participating SIGs
none
Feature gates
none
Created / last updated
2021-02-08 / none
Loading decisions and status history

Keyboard shortcuts

Everywhere

?
Show or hide this list
/
Focus the question box on Ask, otherwise the page search
Ctrl Kor⌘ K
Focus the KEP search in the top bar
t
Switch the theme (system, light, dark)
Esc
Close a dialog, a search list or a menu

Go to a page

Press g, then the letter

g h
Home
g a
Ask
g e
Explore
g u
Audit
g m
Memory
g b
About

Ask

Enter
Send the question
Shift Enter
New line in the question
Esc
Cancel the running question

Search lists

KEP search and Explore search

↓or↑
Move through the results
HomeorEnd
First or last result (Explore)
Enter
Open the highlighted result, or KEP-n when the query is a number

KEP page

o
Open the KEP on GitHub
y
Open kep.yaml on GitHub
a
Ask about this KEP
←or→
Previous or next tab, when a tab is focused

Findings table

With a finding row focused (Tab into the table or click a row)

jork
Next or previous finding
EnterorSpace
Expand or collapse the finding
o
Open the finding's KEP page
d
Draft the fix as an issue text (nothing is posted)
]or[
Next or previous page of findings

Shortcuts pause while you type in a field. Press ? or Esc to close.