Epic Goal

The goal of this epic is to define test cases on ACM addons in imported MCE clusters.

Why is this important?

In the current ACM documentation which describes how to import MCEs into an ACM hub to discover, import and manage hosted clusters https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.11/html/clusters/cluster_mce_overview#hosted-import-mce, it documents this limitation

Important: Do not enable any other Red Hat Advanced Cluster Management add-ons for the imported multicluster engine operator. 

Technically it is possible to enable other ACM addons in the imported MCE clusters. 

While cluster-proxy, managed-serviceaccount, and work-manager addons need to be installed in a different namespace to avoid conflict with MCE's addons for self-managed local-cluster, other ACM addons can be installed normally because MCE clusters do not have those ACM addons for its local-cluster.

Scenarios

As a cluster admin or cluster service provider, I want to import MCEs hosting hosted control planes into ACM and manage the hosted clusters. I also want to enable ACM addons to manage the MCEs as well.

Acceptance Criteria

...

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