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-8347 -----
1. Proposed title of this feature request

Expose Upstream Version Metadata in Kueue

2. What is the nature and description of the request?

This RFE requests that the OpenShift Operator for Kueue expose standardized metadata, specifically their upstream component version. This provides a consistent and programmatic way to identify the exact version of the upstream project being used.

3. Why does the customer need this? (List the business requirements here)

In OpenShift AI, the version of the component used is exposed as part of the RHOAI CRs status. It would probably be useful to have some similar mechanism for OpenShift operator that are provisioning additional components such as Kueue so that the RHOAI Operator can consume such information and report it to the users.

See:

• https://issues.redhat.com/browse/RHOAISTRAT-327
• https://github.com/opendatahub-io/kueue/blob/stable-2.x/config/component_metadata.yaml

4. List any affected packages or components.

• OpenShift Kueue Operator
   ------------------------------------------------------

<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-8347. 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>