Epic Goal

• Enhance the MultiClusterHub/MultiClusterEngine CR to allow for toggling on/off features that are installed by the operator

Why is this important?

• Users may want a smaller footprint and don't want to use all of the features provided by ACM. Combats FUD about size of ACM

Scenarios

1. I just want Cluster Management and Search
2. I just want Observability and Search
3. I just want Policy
4. To name but a few...

Acceptance Criteria

Include pushing metrics to RH telemetry, so we can track how these features are being toggled.

• 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. MCE is an extreme version of this

Open questions::

1. If we get to a comparable size, do we rename MCE to ACM Clusters as an example.

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>