Value Statement

reasons to use RHACM and OpenShift-Pipelines together

1. Configure OpenShift-Pipelines using ACM Policies (Operator-Policy, dependencies, use central-configuration and reference it from ManagedCluster)
2. Policy as Code usings RHACM ArgoCD Integration
3. use Gatekeeper to block creation, deletion of certain Tasks, Pipelines etc...
4. Use RHACM UI to check OpenShift-Pipelines and integrated search to troubleshoot failures
5. Use ACM Policies to detect stuck pipeline runs
6. Have a MultiCluster Dashboard for Pipelines on all Cluster
7. backup restore stateful Pipelines

Most important usecase:

Call Tekton from ACM-Actions (OpenShift Virtulization-Integration)

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.