Epic Goal

Run a supported form of ACM with Policy and HyperShift addon deployment. This would also include registering the local HCP clusters to the ACM

Why is this important?

• SD does not need to rewrite their policies to use a different flow (assumes the policies are needed)
• Consistent with ROSA-HCP
• Use what we sell.

Scenarios

Deploy ACM on the Management Cluster. This cluster is expected to host 80 control planes.  ACM would automatically import those HCP's and register them for use with the local policies.  HyperShift Operator Addon would deploy and interface with the the HyperShift controllers, but the version would continue to be orchestrated externally from the HyperShift team.

Acceptance Criteria

ACM deploys on AKS:

1. HyperShift operator correctly deploys
2. Policies are functioning
3. HCP's are being imported into ACM

Dependencies (internal and external)

1. HyperShift operator works on AKS

Previous Work (Optional):

1. Next gen control plane (partitioning out the ACM components)

Open questions:

1. Can this be done by adding OLM to AKS, should we install without OLM.

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement (ONLY FOR ARO)
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.