*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

Allow multiple agents to co-exist

Why is this important?

Between MCE and ROSA-HCP, there is becoming a high probability of having multiple agents attached to the same cluster. We need to this to work and NOT cause a collision that causes the cluster to be offline from management

Scenarios

1. I want to import a ROSA-HCP cluster into ACM
2. I want to install MCE on a ManagedCluster so I can provision Hosted Control Planes
3. I want to import an MCE into an ACM

Acceptance Criteria

1. A managedCluster with MCE can be managed by an ACM
2. A ROSA-HCP cluster can be managed by an ACM

Dependencies (internal and external)

1. ROSA-HCP OCM-2135 is complete
2. ACM agents start to deploy in the non-standard namespace by default

Previous Work (Optional):

1. The ability to deploy the ACM agent and Addons to a user defined namespace(s)

Open questions:

1. Should we change the default namespace from open-cluster-management-agent and open-clsuter-management-agent-addons to <ACM_CLUSTER_NAME>-agent and <ACM_CLUSTER_NAME>-agent-addons
2. Should we automatically import MCE clusters into ACM (THIS IS OUT OF SCOPE TO COMPLETE IN THIS EPIC, but we should decide whether we want to do this)

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 - 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.

Slack Channel

#acm-8859-default-namespace