<p>I'm working on an application that launches K8S Job (dockerised computer science batchs applications) and I want to prioritizes their launchs.</p>
<p>I don't want to use preemption because all jobs have to be done and I want to be sure that the scheduling order is maintained.</p>
<p>When I read this doc: <a href="https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#non-preempting-priority-class" rel="nofollow noreferrer">https://kubernetes.io/docs/concepts/scheduling-eviction/pod-priority-preemption/#non-preempting-priority-class</a>
It seems that, in non preempting cases, high priority pods can be scheduled after low priority ones if K8S doesn't have the necessary resources at the time.
In case of high priority Jobs are the most demanding, this kind of pods will never be scheduled.</p>
<p>How can I have a control of that decisions?</p>
<p>Thanks!</p>

<p>As you need to use only Non preemptive refer to this <a href="https://stackoverflow.com/a/62135156/19230181">SO</a> and <a href="https://tutorialwing.com/preemptive-or-non-preemptive-priority-scheduling/" rel="nofollow noreferrer">Doc</a> which helps you in understanding the usage of this non preemptive class.</p>
