KEP-1451keps/sig-scheduling/1451-multi-scheduling-profiles
Multi Scheduling Profiles
As workloads in clusters become more heterogeneous, it is natural that they have different scheduling needs. We propose making the scheduler run different framework plugin configurations, which we will call profiles and will be associated to a scheduler name. Pods can choose to be scheduled under a particular configuration by setting the scheduler name asso… Full summary
As workloads in clusters become more heterogeneous, it is natural that they have different scheduling needs. We propose making the scheduler run different framework plugin configurations, which we will call profiles and will be associated to a scheduler name. Pods can choose to be scheduled under a particular configuration by setting the scheduler name associated to it in its pod spec. They will continue to be scheduled under the default configuration if they don't specify a scheduler name (i.e. .spec.schedulerName). The scheduler will continue to schedule one pod at a time.
Facts
- Authors
- @alculquicondor@ahg-g
- Approvers
- @huang-wei
- Reviewers
- @huang-wei@liggitt
- PRR approvers
- @wojtek-tbeta
- Tracking issue
- #1451(opens GitHub in a new tab) closedcompletedclosed 2021-05-14 14:36 UTCsig/schedulingstage/betalifecycle/rotten
- Milestones
- alpha v1.18beta v1.19stable v1.22
- Participating SIGs
- none
- Feature gates
- none
- Created / last updated
- 2020-01-14 / none
Loading decisions and status history