-
Epic
-
Resolution: Unresolved
-
Normal
-
None
-
None
-
None
-
Add NodePool Size/Replicas to Telemetry
-
BU Product Work
-
False
-
None
-
False
-
Not Selected
-
To Do
-
OCPSTRAT-1004 - Expand HCP Metrics To inform Adoption
-
-
100% To Do, 0% In Progress, 0% Done
-
Hypershift Sprint 251, Hypershift Sprint 252, Hypershift Sprint 253, Hypershift Sprint 254, Hypershift Sprint 255, Hypershift Sprint 256, Hypershift Sprint 257, Hypershift Sprint 258, Hypershift Sprint 259, Hypershift Sprint 260, Hypershift Sprint 261, Hypershift Sprint 262, Hypershift Sprint 263
-
0
-
0
-
0
Overview
Today we have hypershift_hostedcluster_nodepools as a metric exposed to provide information on the # of nodepools used per cluster.
Additional NodePools metrics such as hypershift_nodepools_size and hypershift_nodepools_available_replicas are available but not ingested in Telemetry.
In addition to knowing how many nodepools per hosted cluster, we would like to expose the knowledge of the nodepool size.
This will help inform our decision making and provide some insights on how the product is being adopted/used.
Goals
The main goal of this epic is to show the following NodePools metrics on Telemeter, ideally as recording rules:
- Hypershift_nodepools_size
- hypershift_nodepools_available_replicas
Requirements
The implementation involves creating updates to the following GitHub repositories:
similar PRs:
https://github.com/openshift/hypershift/pull/1544
https://github.com/openshift/cluster-monitoring-operator/pull/1710