-
Notifications
You must be signed in to change notification settings - Fork 280
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
Implementation of KEP-3589: uniformly filter manageJobsWithoutQueueNames by namespace #3712
Conversation
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
7630192
to
11e7309
Compare
unit and existing integration tests now passing. I don't quite understand the
ideally, we'd add additional integration tests that verified the new feature across all the integrations, but I ran out of time today. Could wait for a followup PR if necessary due to 0.10 deadline. |
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 did not review the entire codes. I just left a comment how to resolve CI errors.
I think we are good to move the release for tomorrow or EOW. |
1. parse label selector during startup and used cached result 2. guard all uses with feature gate
Co-authored-by: Yuki Iwai <yuki.iwai.tz@gmail.com>
/lgtm |
LGTM label has been added. Git tree hash: a7b213485338e5debf15a13714c587eca8336d90
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dgrove-oss, mimowo 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 |
/kind feature |
/release-note-edit
|
What type of PR is this?
/feature
What this PR does / why we need it:
Implements core feature of KEP-3589 by filtering default suspension of newly created jobs by a namespace selector.
Which issue(s) this PR fixes:
Part of #3589
Special notes for your reviewer:
Does this PR introduce a user-facing change?