Pipelinerun queuing using Kueue #8622
Labels
area/roadmap
Issues that are part of the project (or organization) roadmap (usually an epic)
kind/feature
Categorizes issue or PR as related to a new feature.
kind/tep
Categorizes issue or PR as related to a TEP (or needs a TEP).
Comments
|
This issue can be assigned to me. |
|
Thanks for the feature request @gbenhaim. The status of the TEP you linked is "proposed", which means it is not yet fully fleshed out and has not been accepted for implementation. The proposal, design details, evaluation, and other related sections would need to be completed and the TEP moved to "implementable" status before it could be picked up for implementation. You can find more details about the TEP process in https://github.com/tektoncd/community/blob/main/process/tep-process.md Typically discussion would happen as review comments on a PR to update the TEP document. Feel free to ask any questions you may have about the process here, on Slack, or join one of the working group calls. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature request
Provide Pipelinerun queuing using Kueue.
Kueue is a k8s native queuing and quota management framework. Kueue is extendable, it can support additional providers using external integration.
Use case
Use case are outlined in https://github.com/tektoncd/community/blob/main/teps/0132-queueing-concurrent-runs.md#summary
The text was updated successfully, but these errors were encountered: