Epic Goal

Build an optional operator for installing and managing kueue stack.

 
Why is this important? (mandatory)

As a openshift admin who wants to run batch job on openshift i need a job queuing feature, which is a key to run batch workloads at scale in both on-premises and cloud environments. The main goal of job queueing is to manage access to a limited pool of resources shared by multiple tenants. Job queueing decides which jobs should wait, which can start immediately, and what resources they can use. So that i can deploy my AI/Ml or HPC type application on Openshift
 
Scenarios (mandatory) 

1.  Deploy Kueue and create queues for queuing jobs with limited resources

 
Dependencies (internal and external) (mandatory)

• Production done through CPaaS

Contributing Teams(and contacts) (mandatory) 

Our expectation is that teams would modify the list below to fit the epic. Some epics may not need all the default groups but what is included here should accurately reflect who will be involved in delivering the epic.

• Development - Jan Chaloupka
• Documentation - Andrea Hoffer
• QE - Rama Kasturi Narra
• PX - 
• Others -

Acceptance Criteria (optional)

• upstream repository is created
• cpass configuration is in place
• cpass jenkins instaces is properly configured (e.g. honeybadger)
• advisory is properly populated
• CI testing is in place

Done - Checklist (mandatory)

• CI Testing -  Basic e2e automationTests are merged and completing successfully
• Documentation - Content development is complete.
• QE - Test scenarios are written and executed successfully.
• Technical Enablement - Slides are complete (if requested by PLM)
• Engineering Stories Merged
• All associated work items with the Epic are closed
• Epic status should be “Release Pending”