Goals

Kueue is a Kubernetes native framework for managing queues and quotas for Job like resources - https://kueue.sigs.k8s.io/docs/overview/

Users can benefit from having a queue for Pipelineruns. The benefits are listed in the upstream TEP-0132 - https://github.com/tektoncd/community/blob/main/teps/0132-queueing-concurrent-runs.md

In order to support an extension of Kueue for Pipelineruns, PAC should be able 

to co-exist with Kueue, that means PAC should stop (when configured) changing the the spec.status field of a pipelinerun, since the Kueue extension for Tekton will manage it.

At the same time, reporting to SCM should still be handled by PAC. Reporting should keep working for events such as: the pipeline was created, pending, started, finished (with success or failure).

Requirements

• • (Optional) Use Cases

https://github.com/tektoncd/community/blob/main/teps/0132-queueing-concurrent-runs.md

Out of scope

<Defines what is not included in this story>

Dependencies

< Link or at least explain any known dependencies. >

Background, and strategic fit

< What does the person writing code, testing, documenting need to know? >

Assumptions

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Customer Considerations

< Are there specific customer environments that need to be considered (such as working with existing h/w and software)?>

Documentation Considerations

< What educational or reference material (docs) is required to support this product feature? For users/admins? Other functions (security officers, etc)? >

What does success look like?

< Does this feature have doc impact? Possible values are: New Content, Updates to existing content, Release Note, or No Doc Impact?>

QE Contact

< Are there assumptions being made regarding prerequisites and dependencies?>

< Are there assumptions about hardware, software or people resources?>

Impact

< If the feature is ordered with other work, state the impact of this feature on the other work>

Related Architecture/Technical Documents

<links>

Done Checklist

• Acceptance criteria are met
• Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
• User Journey automation is delivered
• Support and SRE teams are provided with enough skills to support the feature in production environment