aws / aws/containers-roadmap

[EKS] [Control plane]: Add request of /metrics/resources to expose kube_pod_resource_request and kube_pod_resource_limit

Open
#2,600 3 comments 10 reactions 0 assignees View on GitHub
EKS Proposed
Dominant language
Shell
Stars
5.4k
Forks
334
PR merge metrics
No merged PRs in 30d

Description

### Community Note

* Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request
* Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
* If you are interested in working on this issue or have submitted a pull request, please leave a comment

**Tell us about your request**

According to the below doc the two metrics are called kube_pod_resource_request and kube_pod_resource_limit are exposed at the HTTP endpoint /metrics/resources.

https://kubernetes.io/docs/concepts/cluster-administration/system-metrics/#:~:text=Once%20a%20pod,show%2Dhidden%2Dmetrics

However EKS doesnt expose the metrics " kube_pod_resource_request and kube_pod_resource_limit" in scheduler.

What do you want us to build?

Hence we need EKS to expose these metrics in scheduler, since these metrics gives the accurate information of pods resource request and pod resource limit respectively

**Which service(s) is this request for?**
EKS

**Tell us about the problem you're trying to solve. What are you trying to do, and why is it hard?**
We need to get the pod level resource request and resource limit exposed from scheduler metrics.

Contributor guide

Open the contributing guide

Research direction

Start with the linked Kubernetes system-metrics documentation and the scheduler's /metrics/resources endpoint. Confirm the expected kube_pod_resource_request and kube_pod_resource_limit metrics and identify how EKS currently exposes scheduler metrics; done means both pod-level metrics are available from EKS as described.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes
Domain
cloud, observability
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.