Feature Overview (aka. Goal Summary)  

Provide support for LocalQueueDefaulting in RHBoK (Kueue).

Kueue provides a LocalQueueDefaulting feature that improves the user experience by providing a mechanism for defaulting the local-queue label on newly created jobs on a per-namespace level. The feature is guarded by a feature gate which is alpha level in Kueue 0.11 and beta level (enabled by default) in Kueue 0.12.  There is no additional configuration required (beyond being at a minimum level of Kueue 0.12)

Goals (aka. expected user outcomes)

For deployments of Kueue where quota enforcement is desired (all jobs in selected namespace are managed by Kueue), LocalQueueDefaulting can be used to improve the end-user experience and enable cluster admins to configure user namespaces so that all created jobs will have a local-queue label.

Requirements (aka. Acceptance Criteria):

Support for LocalQueueDefaulting in RHBoK

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>