Epic Goal

• MicroShift cluster instance should have a unique cluster-id, like OpenShift clusters

Why is this important?

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

Requirements

1. Upon initial installation/startup, a globally unique ID shall be created.
2. This ID shall not be modified/changed throughout the lifetime of the cluster (e.g. during upgrades/rollback)
3. Special care must be taken for ostree based installation - if the same image is instantiated multiple times on multiple devices, the resulting cluster must have different IDs (meaning the cluster ID must not be created during image generation, but at initial installation/startup).
4. The cluster ID must be displayed on "microshift version" and its corresponding API access
5. The cluster ID must be part of every sosreport.

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• No user documentation is required.

Dependencies (internal and external)

1. None

Open questions::

1. Can we re-used the ID generation mechanismen from OpenShift?

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>