Epic Goal

• Replace CMO's prometheus-adapter deployment with metrics-server as the provider for the metrics.k8s.io APIService
• OpenShift gets an operator that deploys and reconciles metrics-server and related resources
•  explore if a capability that reflects what this operators make sense, see also https://github.com/openshift/enhancements/blob/master/enhancements/installer/component-selection.md 

Why is this important?

• For autoscaling OpenShift needs an resource metrics implementation. Currently this depends on CMO's Prometheus stack
• Some users would like to opt-out of running a fully fledged Prometheus stack, see https://issues.redhat.com/browse/MON-3152

Scenarios

1. A cluster admin decides to not deploy a full Monitoring stack, autoscaling must still work.

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. https://github.com/jan--f/cluster-monitoring-operator/tree/metrics-server 

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>