Our previous metrics were inadequate for calculating pod request and limits - completed pods were supposed to be excluded, init containers were not included, and overhead wasn't calculated. Starting with 4.7 we now have a Kube metric that calculates this correctly from the scheduler - kube_pod_resource_request and kube_pod_resource_limit - and the console can use them quite easily. Update the console with the new metrics.
https://github.com/openshift/console/pull/7894 fix PR
Created attachment 1750838 [details] 01 - no request line # oc get pods console-664f87d4f-f99fq -n openshift-console -o json | jq '.spec.containers[0].resources.requests' { "cpu": "10m", "memory": "100Mi" } On a cluster with PR fix, CPU/Memory Usage charts doesn't show the request line(orange dotted line), see attachment 01 [details] - no request line. Assigning back for double confirmation
I see this as well for the console pod. Assigning back to Clayton. Clayton, let us know if you'd like someone on the console team to investigate.
Created attachment 1772080 [details] pod CPU/Memory requests/limits
Created attachment 1772081 [details] project CPU/Memory requests
Pod CPU/Memory requests/limits is shown correctly, see attachment 'pod CPU/Memory requests/limits' Project CPU/Memory requests is shown correctly, see attachment 'project CPU/Memory requests' Verified on 4.8.0-0.nightly-2021-04-13-171608
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.8.2 bug fix and security 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. https://access.redhat.com/errata/RHSA-2021:2438