Bug 1907998 - Gather kube_pod_resource_request/limit metrics as exposed in upstream KEP 1916
Summary: Gather kube_pod_resource_request/limit metrics as exposed in upstream KEP 1916
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: kube-scheduler
Version: 4.7
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.7.0
Assignee: Clayton Coleman
QA Contact: RamaKasturi
Depends On:
TreeView+ depends on / blocked
Reported: 2020-12-15 16:25 UTC by Clayton Coleman
Modified: 2021-02-24 15:44 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-02-24 15:44:28 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-kube-scheduler-operator pull 283 0 None closed Bug 1907998: Collect /metrics/resources from scheduler 2021-01-19 10:02:15 UTC
Red Hat Product Errata RHSA-2020:5633 0 None None None 2021-02-24 15:44:50 UTC

Description Clayton Coleman 2020-12-15 16:25:36 UTC
We want to more accurately reflect to administrators the resource requests and limits in use on the cluster. As part of upstream KEP 1916 we added a O(pods) (constant factor ~1 series/pod) set of metrics that capture non-terminal (pod,resource,limits/request) values as a sum as interpreted by the kube model (init containers are max).  This will in the future allow a large number of capacity planning dashboards to be implemented.

We want to report total requested / limits metrics to telemetry to assess the rough fleet level use of requests and limits which will be a separate recording rule.  That will allow us to evaluate use of vertical autoscaling and HPA autoscaling in the fleet and whether that leads to higher utilization.

While this is an alpha stability metric, the implementation has low resource cost and scraping by default will allow us to improve overall admin experience on cluster in the UI starting in 4.8 with custom dashboards / better graphs in pod UI, as well as improving the requested limits on the main console dashboard.

Comment 7 Clayton Coleman 2021-01-12 15:09:08 UTC
test with 4.7.0-0.nightly-2020-12-20-031835,there are 3 endpoints under openshift-kube-scheduler, but only find "kube_pod_resource_request" and "kube_pod_resource_limit" under
please change to VERIFIED if it is not a bug

That is intentional and discussed here: https://github.com/kubernetes/enhancements/pull/1916/files#diff-d4bcd9dbd0f7f963d2fdfe8202d93742bae278c771607805080b45a6a14d1cf2R288 (we don't necessarily want to have multiple components reporting the same high cardinality metrics and the view is the same from all three).

Comment 10 errata-xmlrpc 2021-02-24 15:44:28 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.