Feature Overview (aka. Goal Summary)  

Customer used to OpenShift observability want to see similar metrics from MicroShift, so they can re-use existing monitoring dashboards and rules and monitor more metrics.

Goals (aka. expected user outcomes)

The goal is for user to enable  k8s usual/additional metric exporters, namely  node-exporter, metric-exporter, kube-state-metrics

Requirements (aka. Acceptance Criteria):

1. Customers need to be able to opt in for the additional metrics. Either by installing an addition rpm package, or by configuring microshift to enable the additional metrics. Each additional exporter should be enabled individually. 
2. The following additional metric exporter need to be supported:
   1. node-exporter
   2. metric-server
   3. kube-state-metrics
3. If the metric exporter has some configuration options (e.g. which actual metrics to expose), that needs to be available (e.g. via config map or config file)
4. Metrics are exposed via the usual ways (e.g Services) so that they can be scraped by other tooling (e.g. a locally running otel collector, or a remote prometheus database)
5. Metrics need to be provided by re-using existing openshift components / images. 

Questions to Answer (Optional):

none

Out of Scope

This is only about exposing these additional metrics. How they are shipped to an endpoint (otel collector, remote prometheus) is out of scope. 

Background

See linked RFE

Customer Considerations

See linked RFE

Documentation Considerations

The new additional options need to be documented / added to the existing microshift observability documentation.

Interoperability Considerations

none