Value Statement

A cluster admin needs to manually import a hosted cluster by either clicking on the "import" buttons on the hosted cluster UI page or by creating a ManagedCluster CR with the correct hosted cluster name. The the admin also creates a KlusterletAddonConfig CR to enable ACM addons for the hosted cluster.

In order to reduce the manual steps and also make the user experience similar to creating a classic standalone OpenShift cluster via Hive, the addon agent should auto-import a hosted cluster when its hosted control plane (the kube API server) becomes available. 

Definition of Done for Engineering Story Owner (Checklist)

• A new hosted cluster is automatically imported.
• All addons are enabled by default.
• All addons should be running when the hosted cluster's workers are available.

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [x] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [x] Create an informative documentation issue using the [Customer
  Portal_doc_issue template]. https://issues.redhat.com/browse/ACM-6607
• [x] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.