-
Notifications
You must be signed in to change notification settings - Fork 284
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
Single instance admission check. #1635
Conversation
Skipping CI for Draft Pull Request. |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
/test all |
12e3dff
to
182fc18
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.
First pass to make progress, but I think this should not be configurable
26bb442
to
0a36eb1
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.
Minor test question / ask. The code LGTM.
However, I still think this could be simpler for us (in code), and to users if we have just "MultipleMultiKueueAdmissionChecks" as the reason for being inactive, and not make this thing configurable, because as pointed out, this is MultiKueue specific. I think seeing "MultipleSingleInstanceControllerChecks" would be unclear to users.
/assign @tenzen-y @alculquicondor
The release note should be something that is easy to understand for an end-user. |
0a36eb1
to
bf79060
Compare
bf79060
to
a1006f4
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 with the caveat that it is still surfaced at the API level, in status. I think we could hardcode this entirely, but don't want to block it.
I see, I don't recall this discussion though. Anyway, I will defer the decision for API reviewers / approvers in Kueue. IMO making such decisions on PRs without a KEP is tricky, because it requires reverted order of reviews - first by api approvers, then other reviewers (at least for the field). |
I fully agree with you. As much as possible, I'd like to have the dedicated KEP, but if @trasc thinks that discussion points are self-evident, we can discuss in the issue. Although, I guess that it would be better to create small KEP or update existing admission-check KEP. |
To decrease the impact on the API we can use a condition instead of adding a new status field. It's a bit less clear in my opinion but it could do the job. @alculquicondor @mimowo @tenzen-y WDYT? |
I agree with having a hardcoded list. |
The hard-coded list needs to be in cache or passed to cache and needs to contain the name of the multikueue admission check controller. The cache implementation should be agnostic in regards of the existence of a specific admission check controller. |
Why the cache? isn't the workload reconcilier enough? Passing the list of admission checks as an argument seems reasonable. |
Having two multikueue AC set in a ClusterQueue is a ClusterQueue configuration issue. |
Oops, sorry, I meant to say the Clusterqueue reconciler. But ok, I can understand that the logic needs to be in the cache. |
7a309ed
to
abd7250
Compare
abd7250
to
4973cdf
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.
ProvisioningRequest should also be unique, although that can be done in a follow up
/approve
4406915
to
f086d3c
Compare
/lgtm |
LGTM label has been added. Git tree hash: d9a577d92a48bd9811c87078cb46b79aac8b67dc
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alculquicondor, trasc 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 |
* Add support for single instance admission check. * Fix tests after rebase. * Review Remarks
* Add support for single instance admission check. * Fix tests after rebase. * Review Remarks
What type of PR is this?
/kind feature
What this PR does / why we need it:
multikueue
managed AdmissionCheck to be added to one ClusterQueue.Which issue(s) this PR fixes:
Relates to #693
Special notes for your reviewer:
Does this PR introduce a user-facing change?