Epic Goal

• We want the MCE deployment to configure the `local-cluster` for self management by default.

Why is this important?

• We want the MCE operator deployment to be consistent with the ACM hub deployment.

Scenarios

1. As a cluster admin I want to deploy MCE operator on my OCP for cluster lifecycle scenarios.
2. As a cluster admin I want to make use of cluster lifecycle features against my local-cluster itself.
3. As a cluster admin I want the deploy of MCE operator to default to enable hub self management just as the ACM hub operator does today.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• deploy MCE operator has the same default local-cluster hub management configuration as ACM

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 - Downstream documentation merged: <link to meaningful PR>