Epic Goal

• Integrate the MicroShift Cluster ID into ACM

https://redhat-internal.slack.com/archives/C038Q2JK525/p1704698588708929 

Why is this important?

• We need to be able to identify & distinguish different clusters, e.g. for support cases, fleet management, telemetry etc. 

Scenarios

• ClusterClaim produced for MicroShift Cluster ID, in the same way as standard OCP
• ManagedCluster label produced for MicroShift Cluster ID, in the same way as standard OCP
• acm_managed_cluster_info metric integrates the MicroShift Cluster ID
• ACM UI displays the MicroShift Cluster ID in all applicable locations, in the same way as standard OCP

Acceptance Criteria

• All scenarios complete
• QE test automation on all scenarios

Dependencies (internal and external)

1. https://docs.google.com/document/d/1NSMae9RcBfELdU4hMw-aNQm4SGuKm-F2jsa6ueBWVnE/edit 

Previous Work (Optional):

1. ...

Open questions:

1. When will this be available in MicroShift?
   • Currently listed as a 4.16 candidate:  https://issues.redhat.com/browse/OCPSTRAT-1073 

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.