-
Notifications
You must be signed in to change notification settings - Fork 458
KEP: MultiKueue external custom Job support #2458
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
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: mszadkow The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hi @mszadkow. 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-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-kueue canceled.
|
a6227d9 to
10fc776
Compare
|
/ok-to-test |
|
@dgrove-oss is this something that interests you and do you have any thoughts on the proposal? |
| } | ||
| } | ||
| ``` | ||
|
|
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.
Please expand on:
- which subcomponents of MK each external controller is implementing (even if provided by a framework)
- how does a configuration for multiple of these controllers look like from the ClusterQueue point of view.
dgrove-oss
left a comment
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.
The integration test scenario seemed reasonable to me.
Providing a mechanism to register an external controller and have it coordinate with the builtin components about which GVKs each is responsible seems right.
There was not sufficient detail for me as a MultiKueue outsider to understand how the pieces fit together and what I'd need to do to add an external custom Job. Is this KEP also supposed to cover external Job adapters too?
Yes, it's supposed to enable the easy creation of them. I agree that the proposal needs more detail. |
|
ACK |
|
/retitle [WIP] KEP: MultiKueue external custom Job support |
ec73442 to
80ef47d
Compare
|
/retest |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
|
/remove-lifecycle stale |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
|
/remove-lifecycle rotten |
|
The Kubernetes project currently lacks enough contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
| ## Design Details | ||
|
|
||
| Provide a way to integrate external controllers to manage Jobs in the Kueue. | ||
| MulikueueCluster API needs to be modified to ensure that one multikueue cluster is only managed by one admission check controller. |
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.
Why this limitation is required?
|
Is this something actively being worked on? If not, I can take this over as we have some use-cases at Apple that can benefit from this approach. |
|
@ravisantoshgudimetla I am working on this. Either this or #5981 should be done soon. |
|
The Kubernetes project currently lacks enough active contributors to adequately respond to all PRs. This bot triages PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
|
PR needs rebase. 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-sigs/prow repository. |
|
/close As per: #2405 (comment) |
|
@mimowo: Closed this PR. 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-sigs/prow repository. |
What type of PR is this?
/kind documentation
What this PR does / why we need it:
New KEP that explains the way to introduce MultiKueue external custom Job support.
Which issue(s) this PR fixes:
Fixes #2349
Special notes for your reviewer:
Does this PR introduce a user-facing change?