Epic Goal

User is able to import local-cluster with a different name rather than local-cluster

Why is this important?

This is a customer requirement and also requirement from cluster service in ARO

Scenarios

1. User disable local management when installing MCE/ACM
2. User import local cluster with the local cluster lable
3. Addons can function correctly.

Acceptance Criteria

User is able to import local-cluster with a different name rather than local-cluster

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.