-
Notifications
You must be signed in to change notification settings - Fork 268
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
Introduce an on-demand API endpoint for fetching pending workloads in a cluster queue #1251
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. |
8b16e49
to
02245af
Compare
b68b309
to
bb7b586
Compare
/assign @mimowo |
/ok-to-test |
/test pull-kueue-test-e2e-main-1-25 |
b587b3f
to
8e2fad8
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.
Couple nits to make the e2e test more readable
This failure looks related: "https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_kueue/1251/pull-kueue-test-e2e-main-1-26/1727335355239108608". I suspect this is the issue with the mechanism to evict the sampleJob1. Maybe we should actually go with the 5s approach as here, and a couple other preexiting tests. Then, we can have a follow up issue to improve execution time of the e2e tests more holistically. |
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 overall. @PBundyra Please squash the commits and mark the addressed comments as resolved.
f53eb35
to
c70071c
Compare
Co-authored-by: Yuki Iwai <[email protected]> Co-authored-by: Aldo Culquicondor <[email protected]> Co-authored-by: Michał Woźniak <[email protected]>
c70071c
to
b37c7ab
Compare
/lgtm |
LGTM label has been added. Git tree hash: 64097d68b953254803348f3c34794f1e7de49fd5
|
/hold cancel |
Co-authored-by: Yuki Iwai <[email protected]> Co-authored-by: Aldo Culquicondor <[email protected]> Co-authored-by: Michał Woźniak <[email protected]>
/release-note-edit
|
Co-authored-by: Yuki Iwai <[email protected]> Co-authored-by: Aldo Culquicondor <[email protected]> Co-authored-by: Michał Woźniak <[email protected]>
What type of PR is this?
/kind feature
/kind api-change
What this PR does / why we need it:
Part of the KEP#168-2
Which issue(s) this PR fixes:
Part of #168
Special notes for your reviewer:
In order to test it, create pending workloads and then send requests:
kubectl get --raw /apis/visibility.kueue.x-k8s.io/v1alpha1/clusterqueues/<CQ-NAME>/pendingworkloads
Does this PR introduce a user-facing change?