Goal

• Allow users of hosted clusters to gain insights into their workloads through metrics exposed by kubernetes components (kube apiserver, kube scheduler, kube controller manager).

Why is this important?

• Control plane metrics are not only useful for SRE'ing the control plane but also for monitoring the behavior of workloads. Administrators of hosted clusters currently do not have a good view into the control plane and how their workloads are impacting it.
• We currently expose the kube apiserver metrics via service monitor in the data plane. However, because this servicemonitor only scrapes the single kube apiserver endpoint, metrics such as counters will vary depending on which instance of the apiserver is serving the metrics request at time of scraping.
• There is no visibility into scheduler or controller manager metrics.

Scenarios

Acceptance Criteria

• Dev - Has a valid enhancement if necessary
• CI - MUST be running successfully with tests automated
• QE - covered in Polarion test plan and tests implemented
• Release Technical Enablement - Must have TE slides
• ...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. …

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Technical Enablement <link to Feature Enablement Presentation>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Enhancement merged: <link to meaningful PR or GitHub Issue>
• 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>