Feature Overview (aka. Goal Summary)  

An elevator pitch (value statement) that describes the Feature in a clear, concise way.  Complete during New status.

 ----- copied from RFE-8388 -----
Background:

We (Openshift Pipelines Team) adding multicluster functionality in Tekton/Openshift Pipelines which enables Tekton Pipelines to provide a central user experience for orchestrating PipelineRun across multiple clusters for horizontal scalability.

Current Status:

• Successfully completed POC with upstream Kueue (MultiKueue)

• Identified that upstream Kueue didn't support custom jobs

• Contributed external custom job support to MultiKueue as part of KEP 2349

• Verified multicluster functionality works as expected with OpenShift Pipelines

Current Blocker:

Red Hat Kueue Operator does not yet support the new multicluster features required for OpenShift Pipelines MultiCluster functionality.

Requirements:

Detailed requirements have been documented and shared with Red Hat Kueue Team:  

https://docs.google.com/document/d/19J-Cf7fwbbQxDyiH2hWj2Q9lRnNVUSLBQlKfsjZUCDc/edit?tab=t.nbeqecd9ayld#heading=h.vs8rr7i86atp

Impact:

The absence of this functionality in Red Hat Kueue Operator is currently blocking OpenShift Pipelines from supporting MultiCluster capabilities.

Next Steps:

• Red Hat Kueue Team has requested creation of an epic for planning purposes

• Need to prioritize implementation of multicluster support in Red Hat Kueue Operator

Dependencies:

• Red Hat Kueue Team implementation timeline
• Upstream Kueue MultiKueue features (already implemented)

cc rh-ee-csalinas rh-ee-kbaig gbenhaim rh-ee-ntatinen 
 ------------------------------------------------------

<your text here>

Goals (aka. expected user outcomes)

The observable functionality that the user now has as a result of receiving this feature. Include the anticipated primary user type/persona and which existing features, if any, will be expanded. Complete during New status.

<your text here>

Requirements (aka. Acceptance Criteria):

A list of specific needs or objectives that a feature must deliver in order to be considered complete.  Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc.  Initial completion during Refinement status.

 This Feature was generated in OCPSTRAT via acceptance of RFE-8388. Ensure the stated Acceptance Criteria below will fulfill the needs specified in the RFE.

<enter general Feature acceptance here>

Anyone reviewing this Feature needs to know which deployment configurations that the Feature will apply to (or not) once it's been completed.  Describe specific needs (or indicate N/A) for each of the following deployment scenarios. For specific configurations that are out-of-scope for a given release, ensure you provide the OCPSTRAT (for the future to be supported configuration) as well.

Use Cases (Optional):

Include use case diagrams, main success scenarios, alternative flow scenarios.  Initial completion during Refinement status.

<your text here>

Questions to Answer (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin.  Initial completion during Refinement status.

<your text here>

Out of Scope

High-level list of items that are out of scope.  Initial completion during Refinement status.

<your text here>

Background

Provide any additional context is needed to frame the feature.  Initial completion during Refinement status.

<your text here>

Customer Considerations

Provide any additional customer-specific considerations that must be made when designing and delivering the Feature.  Initial completion during Refinement status.

<your text here>

Documentation Considerations

Provide information that needs to be considered and planned so that documentation will meet customer needs.  If the feature extends existing functionality, provide a link to its current documentation. Initial completion during Refinement status.

<your text here>

Interoperability Considerations

Which other projects, including ROSA/OSD/ARO, and versions in our portfolio does this feature impact?  What interoperability test scenarios should be factored by the layered products?  Initial completion during Refinement status.

<your text here>