Epic Goal

As an ACM user, administrator of the fleet, I would like to import ROSA HCP clusters and manage them.

Why is this important?

Enable customers to leverage ACM for fleet management of all types of OpenShift offerings, be they managed or self-managed.

Scenarios

Import an existing ROSA HCP,

Effectively view the cluster details in ACM UI,

DO NOT offer to change cluster version channels and perform cluster update action of ROSA HCP.

Acceptance Criteria

The ManagedCluster resource clusterClaim should know that this is a ROSA type of cluster:

• name: product.open-cluster-management.io
    value: ROSA

Therefore once we know this is a ROSA, we would not offer the upgrade capabilities in the UI.

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://redhat-internal.slack.com/archives/C027TN14SGJ/p1694617455221009

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>