Add documentation for preemption #618
Conversation
Change-Id: I75cb8023e75f22c44c8271be52033c0d41026666
k8s-ci-robot
added
the
kind/documentation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
cncf-cla: yes
|
Fixes #576 |
| Workloads from other ClusterQueues in the cohort that are using more than | ||
| their nominal quota. Possible values are: |
There was a problem hiding this comment.
| Workloads from other ClusterQueues in the cohort that are using more than | |
| their nominal quota. Possible values are: | |
| Workloads from other ClusterQueues that are using more than | |
| their nominal quota in the cohort. The possible values are: |
There was a problem hiding this comment.
Why move "in the cohort"? The ClusterQueues belong to the cohort.
Changed the other part.
| - `LowerPriority`: if the pending workload fits within the nominal | ||
| quota of its ClusterQueue, only preempt workloads in the cohort that have | ||
| lower priority than the pending Workload. | ||
| - `Any`: if the pending workload fits within the nominal quota of its |
There was a problem hiding this comment.
| - `Any`: if the pending workload fits within the nominal quota of its | |
| - `Any`: if the pending Workload fits within the nominal quota of its |
|
|
||
| Note that an incoming Workload can preempt Workloads both within the | ||
| ClusterQueue and the cohort. Kueue implements heuristics to preempt as few | ||
| Workloads as possible, prefering Workloads with these characteristics: |
There was a problem hiding this comment.
| Workloads as possible, prefering Workloads with these characteristics: | |
| Workloads as possible, prioritizing Workloads with these characteristics: |
If you decide to keep preferring, fix the typo :)
There was a problem hiding this comment.
😂 thanks
I kept the word "preferring". I think "prioritizing" can be confusing given that we talk about priority below.
| Workloads from other ClusterQueues in the cohort that are using more than | ||
| their nominal quota. Possible values are: |
There was a problem hiding this comment.
Why move "in the cohort"? The ClusterQueues belong to the cohort.
Changed the other part.
| - `LowerPriority`: if the pending workload fits within the nominal | ||
| quota of its ClusterQueue, only preempt workloads in the cohort that have | ||
| lower priority than the pending Workload. | ||
| - `Any`: if the pending workload fits within the nominal quota of its |
|
|
||
| Note that an incoming Workload can preempt Workloads both within the | ||
| ClusterQueue and the cohort. Kueue implements heuristics to preempt as few | ||
| Workloads as possible, prefering Workloads with these characteristics: |
There was a problem hiding this comment.
😂 thanks
I kept the word "preferring". I think "prioritizing" can be confusing given that we talk about priority below.
k8s-ci-robot
added
tide/merge-method-squash
|
/lgtm |
k8s-ci-robot
added
the
do-not-merge/hold
k8s-ci-robot
added
the
lgtm
|
/hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Follow up to #514
Which issue(s) this PR fixes:
Fixes #576
Special notes for your reviewer:
I'm using v1beta1 in this PR, but updates to the rest of the documentation will come in a separate PR.