Value Statement

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

• 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

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

Definition of Done for Engineering Story Owner (Checklist)

• ...

Development Complete

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

Tests Automated

• [ ] 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

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] 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.