If a container doesn't have cpu limits, kube_pod_resource_limit reports the init-container limit about kube-state-metrics

[dashpole]

/assign @rexagod
/triage accepted

[rexagod]

FYI While this seems like a bug, it is recommended to use kube-scheduler's exposed metrics for kube_pod_resource_{limit/request}s.

[andresm53]

Thanks @rexagod . The problem with that (kube-scheduler's exposed metrics) is: in my particular case, I am using Openshift (4.12) and by default it uses kube_pod_resource_limit to display the cpu metrics chart. This is how it looks like, for the example pod I provided before. As you can see the chart is confusing, because the pod doesn't effectively has any cpu limits, but the chart implies that it has.

[rexagod]

@andresm53 Oh wow! Thank you for bringing this up, I'll ping the console folks internally to take a look. That being said, I believe https://github.com/openshift/console would be a better place to raise this.

Closing, feel free to reopen in openshift/console.