Epic Goal

• Make it possible for customers to disable the Cluster Monitoring operator by leveraging the OCPPLAN-9638 Composable OpenShift capability.

Note: MON-3152 tracks the individual workstreams.

Why is this important?

• For Managed OpenShift on AWS (ROSA) with HyperShift, we get metrics from the control plane, so we don't need the cluster monitoring capabilities.
• Customers with existing / preferred monitoring solutions want to have as small of an OpenShift resource footprint as possible.

Scenarios

1. This feature must consider the different deployment footprints including self-managed and managed OpenShift, connected vs. disconnected (restricted and air-gapped), implications for auto scaling, chargeback/showback use scenarios, etc.
2. Disabled configuration must persist throughout cluster lifecycle including upgrades.

Acceptance Criteria

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

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions::

1. …

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>