-
Notifications
You must be signed in to change notification settings - Fork 228
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
Extend visibility ClusterQueue PendingWorkloads endpoint #1362
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
Hi @PBundyra. 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. |
/assign @mimowo |
@PBundyra: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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. |
@PBundyra: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
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. |
/ok-to-test |
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.
Just some nits
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.
Generally LGTM, remaining question about the conversion. I think potential changing the types could be handled outside of the this PR.
Oh, I see why the e2e tests are failing, because the workload name is actually derived from the job name according to: https://github.com/kubernetes-sigs/kueue/blob/1ecd79f748af2617111d0bfa1ca848f9e172f4d7/pkg/controller/jobframework/workload_names.go#L44C8-L44C8. Can we call this function from within e2e tests? If not, maybe we need to fetch the workloads (per job), with GET, and assert on the names. |
I didn't see this comment earlier, and I've suppressed checking the Name. Do you think it's necessary to check it, as we already do it in unit tests? |
I think it is ok to skip the check, given that it is done in unit tests + the other properties of the workload identify it in the e2e tests. |
LGTM. please squash |
/lgtm |
LGTM label has been added. Git tree hash: fbbca4a5043c9117f1845c88b3dff479ae423150
|
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.
My first pass. I have yet to see the implementation.
Still LGTM |
/lgtm canel |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, PBundyra 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 |
/lgtm cancel |
LGTM, please squash |
…ts, add unit tests, change query parameters types: int -> int32
I consider the comments addressed. |
LGTM label has been added. Git tree hash: 5b35eb1b0e54d7773ec8675a6d7b5eee39cb552a
|
/release-note-edit
|
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
This PR continues the development of KEP#168-2
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?