Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
sched: controller: set scheduler priority
So far the scheduler priority is set to default which is 0 this is risky especially when the preemtion of pods is needed to fit more important pods. The NRS is important enough to deserve the most critical priority class system-node-critical which is the same priority for the kube-scheduler. We need this priority set always regardless how many replicas are set for the scheduler, and especially if we look to optimize the HA of the scheduler. We choose system-node-critical over system-cluster-critical because we don't want to allow SS preemption by higher-priority pods. If it was set to system-cluster-critical and an event is triggered that requires pod eviction, which would be for scheduling system-node-critical workloads, the SS would be at risk of being evicted. although this would be very rare and the evicted pod will be rescheduled, there is no convincing reason not to make it node-critical. addresses openshift-kni#974 Signed-off-by: Shereen Haj <[email protected]>
- Loading branch information