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-8387 -----

What is the nature and description of the request?

Integrate and enable the Admission Fair Sharing feature from Kueue into RHBOK.

This mechanism ensures fair workload admission when multiple resource consumers (LocalQueues) feed into a single shared resource pool (ClusterQueue). It prioritizes workloads from LocalQueues based on their historical resource usage, giving preference to those that have consumed fewer resources over time. This is achieved through usage tracking, a configurable decay function, and an immediate Entry Penalty upon workload admission.

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

The Konflux platform uses a single ClusterQueue for all tenants, creating a high risk of resource starvation (the "noisy neighbor" problem). This feature is needed to meet the following requirements:

• Enforce Multi-Tenant Fairness (Business Critical): Implement a robust, usage-based mechanism to ensure an equitable distribution of shared cluster resources among all tenants over time.

• Improve Service Predictability: Guarantee that all tenants receive a reasonable and predictable share of execution capacity, thereby reducing workload latency variance and preventing long-term starvation.

• Enable Scalable Governance: Provide a dynamic governance model that adapts to historical usage, simplifying resource management compared to complex, static quotas.

List any affected packages or components

RHBOK / Kueue Operator: The logic managing Kueue deployment and configuration must be updated.

Assited-By: Gemini
 ------------------------------------------------------

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