KEP-902keps/sig-scheduling/902-non-preempting-priorityclass
Add NonPreempting Option For PriorityClasses
PriorityClasses are a GA feature as on 1.14, which impact the scheduling and eviction of pods. Pods are be scheduled according to descending priority. If a pod cannot be scheduled due to insufficient resources, lower-priority pods will be preempted to make room. This proposal makes the preempting behavior optional for a PriorityClass, by adding a new field… Full summary
PriorityClasses are a GA feature as on 1.14, which impact the scheduling and eviction of pods. Pods are be scheduled according to descending priority. If a pod cannot be scheduled due to insufficient resources, lower-priority pods will be preempted to make room. This proposal makes the preempting behavior optional for a PriorityClass, by adding a new field to PriorityClasses, which in turn populates PodSpec. If a pod is waiting to be scheduled, and it does not have preemption enabled, it will not trigger preemption of other pods.
Facts
- Approvers
- @bsalamat@huang-wei
- Reviewers
- @k82cn@huang-wei@wgliang
- PRR approvers
- @wojtek-tstable
- Tracking issue
- #902(opens GitHub in a new tab) closedcompletedclosed 2022-08-07 14:40 UTCmilestone v1.24sig/schedulingstage/stablelifecycle/stalekind/api-change
- Milestones
- alpha v1.15beta v1.19stable v1.24
- Participating SIGs
- none
- Feature gates
- NonPreemptingPriority
- Created / last updated
- 2019-03-17 / none