Epic Goal

• We should be able to build the tekton-kueue  like other components in openshift-pipelines
• Onboard tekton-kueue on operator, With OSP operator kueue should be installed by default (If  Kueue operator is installed)

Why is this important?

Scenarios

1. ...

Other Considerations

<Call out anything explicitly as Out of Scope?>
<Call out internal and external dependencies?>
<Are there any known previous works?>
<Any unanswered questions?>

Definition of Ready

• The epic has been broken down into stories. Stories have been scoped.
• The epic has been stack ranked.

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Integration tests have been completed.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested on OpenShift either upstream or downstream on a local build
• Documentation:
  • User documentation or release notes have been written.
• Build:
  • Code has been successfully built and integrated into the main repository / project
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing
• Acceptance:
  • Product Manager or stakeholder has reviewed and accepted the work.