-
Notifications
You must be signed in to change notification settings - Fork 275
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
add docs for workloadPriority #1170
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Hi @Gekko0114. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Hi @alculquicondor , @tenzen-y , |
/assign @alculquicondor |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, can you add a concept for the WorkloadPriority to https://github.com/kubernetes-sigs/kueue/tree/f6d9f1e7c4efefba1d67825c2b80e73a17840bdf/site/content/en/docs/concepts?
/ok-to-test |
8d6848c
to
25e107f
Compare
Sure, added a concept. |
@@ -103,4 +103,5 @@ creating a corresponding Workload object for it. | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you update the Priority
section in this file as well?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
updated
About #1's scenario, the `workloadPriorityClass` is used for the `workload's priority`. On the other hand, the `priorityClass` is used for the `pod's priority`. | ||
About #2's scenario, the `workloadPriorityClass` is used for the `workload's priority`. On the other hand, `workloadPriorityClass` is not used for `pod's priority`. | ||
About #3' scenario, the `PriorityClass` is used for the `workload's priority` and `pod's priority`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, it would be better to explain what happens if the job implement the JobWithPriorityClass
interface.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tenzen-y this might be too developer focused and a user cannot do too much about it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was also concerned about what you say. However, actually, which priorities are used depends on the interface.
For example, we can set three priorities (.spec.runPolicy.priorityClass
, .spec.labels.kueue.x-k8s.io/priority-class
, and .spec.mpiReplicaSecs[*].template.spec.priorityClassName
) on the MPIJob.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or, instead of mentioning the interface, raise MPIJob as a specific case.
@alculquicondor Any better ideas?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your comments! Added the explanation related to JobWithPriorityClass
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like how Hiroyuki phrased it :)
/assign @trasc |
About #1's scenario, the `workloadPriorityClass` is used for the `workload's priority`. On the other hand, the `priorityClass` is used for the `pod's priority`. | ||
About #2's scenario, the `workloadPriorityClass` is used for the `workload's priority`. On the other hand, `workloadPriorityClass` is not used for `pod's priority`. | ||
About #3' scenario, the `PriorityClass` is used for the `workload's priority` and `pod's priority`. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tenzen-y this might be too developer focused and a user cannot do too much about it.
|
||
## Workload's priority values are always mutable | ||
|
||
Workload's `Priority` field is always mutable because it might be useful for the preemption. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this something relevant for a user?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think so, I added an example
8734ffb
to
53d961f
Compare
53d961f
to
4d91beb
Compare
58dde38
to
6822fd7
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
leaving /lgtm
on @alculquicondor
6822fd7
to
05c2f0f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
LGTM label has been added. Git tree hash: 4549ab081455effaaa613e8f0078acc81f21fe52
|
By default kueue will take the PriorityClassName of the first PodSet having one set, | ||
however the integration of the CRD with Kueue can implement | ||
[`JobWithPriorityClass interface`](https://github.com/kubernetes-sigs/kueue/blob/e162f8508b503d20feb9b31fd0b27d91e58f2c2f/pkg/controller/jobframework/interface.go#L81-L84) | ||
to change this behavior. You can read the code for each job integration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I guess that's what we have today :(
If you have the time, please update the documentation for MPIJob and other kubeflow CRDs to explain how we obtain the priority class for each.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, Gekko0114 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 |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
add docs for workloadPriority
Which issue(s) this PR fixes:
Fixes #1157
Does this PR introduce a user-facing change?