Story (Required)

Create clusterpools for OpenShift Pipelines to use OpenSHift CI

Background (Required)

We detected that following repositories:
openshift-pipelines/task-openshift
openshift-pipelines/task-maven
openshift-pipelines/task-buildpacks
openshift-pipelines/task-git
openshift-pipelines/task-containers
openshift-pipelines/operator
 
are using our openshift-ci cluster pools. We would like you to shift away from them as it is generating additional cost for core openshift organization. We would like it to happen in the next 60 days (transition period). You can supply your own cluster pools. If you have questions please do not hesitate to contact us. Feel free to cc additional people as we may miss people who are directly responsible for making such decisions. To see announcement of this initiative please visit aos-leads mailing list (Further actions on scaling OCP CI and estimating CI costs accurately (Cluster Pools)) or slack channel.

https://redhat-internal.slack.com/archives/CBN38N3MW/p1710341230696809

Out of scope

<Defines what is not included in this story>

Approach (Required)

<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>

Dependencies

<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>

Acceptance Criteria (Mandatory)

<Describe edge cases to consider when implementing the story and defining tests>

<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

Legend

Unknown

Verified

Unsatisfied

Done Checklist

• Code is completed, reviewed, documented and checked in
• Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
• Continuous Delivery pipeline(s) is able to proceed with new code included
• Customer facing documentation, API docs etc. are produced/updated, reviewed and published
• Acceptance criteria are met