Epic Goal

• Collab with https://issues.redhat.com/browse/GITOPS-1349 to have a consistent story of RBAC and between RHACM and Gitops-Operator.
  The default ArgoCD on the ACM hub can be populated with all new clusters automatically. Then OCP GitOps subscription can be deployed to them by ACM policy or the default ArgoCD(via ApplicationSet). 
•  Appropriate Roles for Application Instances of ArgoCD can be propagated down (ACM Policy or default ArgoCD) to specific clusters (via GitOps)
•  All the Apps that are deployed by the different ArgoCD's both local and remote to the hub, become available to the admin's in ACM's UI to view and monitor.

So there are lots of options and approaches available.

Why is this important?

• We need to have a good demo on that

Scenarios

1. ...

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>