Epic Goal

As a User of Advanced Cluster Management, I have access to the native OCP Console Observability UI via the ACM console for multicluster observability backed by MCO metrics storage

As a Fleet Administrator of an Advanced Cluster Management Hub, I can enable ACM Observability UI through the MCO Custom Resource so that I avoid having to install the Cluster Observability Operator Indepenedently.

Why is this important?

ACM-3225 will ship ACM specific Observability UI components that mount to the ACM Console view. Currently, the dev preview version of this feature is enabled by installing COO (Cluster Observability Operator) in the hub directly. COO packages the OCP Observability UI Operator, which is reponsible for managing these components and mounting them to the ACM console. 

The aim of this epic is to simplify the delivery of these ACM/CNV specific Observability UI features so that a user does not have to install COO independently from ACM and MCO. This will be achieved by installing COO as an operand onto the hub via the Multi-cluster Observability Operator Addon (MCOA). This is done by adding an OLM subscription to the operator for a given version, and configuring it after it has completed installation.

This is important because MCO is aiming to be a single-step install for backend storage components, collectors in spoke clusters and UI components used to query the respective Observability persistence layers (logs/metrics/traces). 

Acceptance Criteria

• [Dev Preview] A feature flag is exposed via the MCO capabilities field users are able to specify if they would like the built-in ACM Console Observability UI to be visible
• [Dev Preview] When the feature flag is enabled, users are able to view the ACM Alerting UI and Observability UI plugins.
• When the feature flag is enabled, COO is installed on the hub and configured to create and mount the ACM Console Observability UI components.
  • This includes any UI Plugin CR's that are required to toggle the ACM specific Observability UI Plugins 
  • This also includes configuring datasources (e.g. ACM alertmanager for alerting UI, ACM Thanos for UI Plugins etc.) 
• The Observability UI components use the legacy Metrics persistence stack (Observatorium Operator + Metrics Collector) for querying (adaptation to the new MCOA based metrics stack will come at a later date).

Non-goals: 

• Perses is not in scope for this epic, but will be a further operand inside of the Cluster Observability Operator. This epic will provide a conduit for providing perses dashboards via the ACM console.

Dependencies (internal and external)

1. ACM-3225

Open questions:

1. …