Epic Goal

• The console team has refactored the Monitoring pieces into an optional plugin for the console. CMO should deploy the needed resources for this.
  Initially we can just create static resources like the logging view plugin has and simply deploy these through CMO.
  The image will be created by ART based on https://github.com/openshift/monitoring-plugin. All we need to do is pass the image reference to CVO via https://github.com/openshift/cluster-monitoring-operator/blob/master/manifests/image-references.

Why is this important?

• Monitoring console pages should be visible when CMO is present.

Scenarios

1. ...

Acceptance Criteria

• Console plugin is deployed by CMO.

Dependencies (internal and external)

https://github.com/openshift/monitoring-plugin

Previous Work (Optional):

1. https://issues.redhat.com/browse/OU-34
2. Example resource for a similar logging plugin: https://github.com/openshift/logging-view-plugin/blob/main/logging-view-plugin-resources.yml

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>