Epic Goal

A cluster administrator needs to either create a ManagedCluster CR or click on "Import cluster" on the hosted cluster details UI page to import the hosted cluster. This epic is to recognize a specific label in the HostedCluster CR to trigger the hypershift addon agent to auto-import the cluster by creating the ManagedCluster CR automatically.

Why is this important?

It is an extra manual step for users to import a hypershift hosted cluster compared to hive-provisioned cluster which is auto-imported. This epic improves user experience of creating and managing a hypershift hosted cluster.

Scenarios

A cluster admin creates a hypershift hosted cluster on any of the supported cloud or virtualization platforms. When the hosted cluster's API server becomes available, the hosted cluster is auto-imported into MCE.

Acceptance Criteria

1.  If we are to auto-import by default:

• • Ideally we need to make sure cluster creation is not impacted.
  • That metrics are correctly reported (observability as part of ACM telemetry that a managed cluster is deployed in HCP, and what provider was used)
  • That we contain the setup (klusterlet in the cp) in the rest of our self-managed testing.

       2. A global configuration should be available to opt-out the auto-import.

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>