Epic Goal

Some of the underlying components provided by the Multicluster Global Hub (MCGH) will be needed to support a Global Policy View dashboard.

Why is this important?

Onboarding of the MCGH repos will allow dependent squads to iterate code that delivers capability to customers with multiple hubs - these customers require a single view of fleet compliance.

Scenarios

As an MCGH engineer, I need to build and deliver code alongside the ACM hub operator deliverable.

As an MCGH engineer, as I work in the code to achieve a Technical Preview, I need to be able to quickly iterate features and incorporate customer feedback between iterations. 

As an MCGH engineer, I would like to be able to release feature function as Technical Preview, independently of ACM.

As a customer, I would like to be able to install a Technical Preview release as a red hat marketplace operator.

As a customer, I will l need to be able to install the Technical preview operator in a disconnected environment.

Acceptance Criteria

Red Hat catalog operator

Disconnected

Grafana component

Policy view dashboards

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. ACM-2018

Open questions:

1. How much back breaking work is this on ACM CICD?

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>