Epic Goal

ROSA is a managed offering, that can be hosted on Hypershift. We need to ensure that

• OpenShift GitOps can be installed and used by customers of Hypershift-hosted ROSA
• Any differences to the standard OpenShift GitOps functionality or installation is well documented
• OpenShift GitOps documentation is made available under the CI/CD section of the ROSA documentation structure.
• Pre-requistes and hardware requirements and any other special conditions required for deploying OpenShift GitOps must be clearly spelt out in the documentation.
• If any Tech Preview feature is not applicable to ROSA use case, explicitly mention it in the documentation.

Why is this important?

Customers of ROSA should be able to install and use OpenShift GitOps similarly to how they can do it with self-hosted, self-managed OCP.

Scenarios

1. OpenShift GitOps Installation using Operator Hub on a ROSA (HCP) cluster.
2. Create an ArgoCD instance and configure it on a ROSA (HCP) cluster.
3. Run upstream ArgoCD E2E tests against the ROSA (HCP) cluster.

Other Considerations 

Both ROSA classic and hosted control plane (HCP) options should be considered for this epic.

Definition of Ready

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

• …