USER STORIES:

What are we attempting to achieve? You might need to duplicate this a few times.

As Red Hat
We want ARO to be as close as possible to OCP ("OpenShift is OpenShift is OpenShift" - as sales would say)
So that we can sell a hybrid cloud platform

As maintainers of ARO
We want to deliver on the vision of our business
So that we align our work with revenue and goals of our leadership

As a customer using ARO
I want a consistent experience across ARO and OCP
So that I don't have to worry when I issue upgrades or using features in one platform or the other

ACCEPTANCE CRITERIA:

• Close existing gaps around E2E testing for openshift/ARO-Installer, specifically:
  • Add E2E testing for changes in openshift/ARO-Installer on pull requests and merge
  • Add E2E testing for nightly OCP builds with openshift/ARO-Installer daily
• Act as a POC for mirroring images into ACR for ARO
• Create confidence in ARO installs to introduce a blocking job for Openshift in the future

BREADCRUMBS:

Where can SREs look for additional information? Mark with "N/A" if these items do not exist yet so Functional Teams know they need to create them.

• ADR: https://docs.google.com/document/d/1UtHw-kVj6LyD4hJ0_LAC-oMwqKZ1cAnw0C3V5POcLys/edit
• Design Doc: https://docs.google.com/document/d/1_cT4C6yfzUNLQUfKL9MbhJ4xYpqRd8t1ZSFqCjyth6Y/edit#heading=h.bupciudrwmna
• Wiki: N/A
• Similar Work PRs: N/A
• Subject Matter Experts: Lisa, Tanmay, Hilliary, Brendan, OCP Engineering
• PRD: N/A
• *OCP Dependencies: https://issues.redhat.com/browse/ARO-6035

NOTES: