Uploaded image for project: 'Red Hat Advanced Cluster Management'
  1. Red Hat Advanced Cluster Management
  2. ACM-11166

[RFE] Support auto detection of MicroShift's cluster ID

XMLWordPrintable

    • [RFE] Support auto detection of MicroShift's cluster ID
    • False
    • None
    • False
    • Green
    • To Do
    • ACM-9267 - [RFE] Support auto detection of MicroShift's cluster ID
    • ACM-9267[RFE] Support auto detection of MicroShift's cluster ID
    • 0% To Do, 0% In Progress, 100% Done

      OCP/Telco Definition of Done
      https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
      Epic Template descriptions and documentation.
      https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
      ACM-wide Product Requirements (Top-level Epics)
      https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

      *<--- Cut-n-Paste the entire contents of this description into your new
      Epic --->*

      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:

      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.

            qhao@redhat.com Qing Hao
            qhao@redhat.com Qing Hao
            Hui Chen Hui Chen
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: