Epic Goal

Enable the RHACM add-on in ROSA cluster so customers can install a Self Managed instance of ACM on the ROSA instance. 

Why is this important?

This enables customers to purchase RHACM via the AWS cloud Marketplace.  As part of the hybrid cloud spend project (Stratosphere), we are going to sell self managed RHACM at an hourly rate.

Scenarios

1. User navigates to the AWS marketplace and purchases RHACM.
2. The RH system is notified of the entitlement
3. The user can then got to any ROSA instance and install the RHACM add-on.
4. Once the add-on is installed the customer will use ACM in a self managed mode.
5. As clusters are added to the RHACM domain, metrics are collected and processed by the RH Subscription Watch service.
6. The usage is then reported back to AWS and the customer is charged within their AWS account.

Acceptance Criteria

RHACM is present in the add-ons view in ROSA.

RHACM can be installed via the add-on.

RHACM is submitting the correct core usage of the fleet to SubW.

SubW is calculating the correct value and submitting to AWS. 

Dependencies (internal and external)

1. SubW will need to calculate the core count from the cluster list returned by the RHACM metric managed-cluster-info. 

Previous Work (Optional):

1. https://issues.redhat.com/browse/ACM-2638

Open questions:

None

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>