Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

To obtain the "Allocated resources:" from the output of kubectl describe node <node-name>, what query should be used? #2522

Open
githubeto opened this issue Oct 10, 2024 · 1 comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@githubeto
Copy link

I believe that the most accurate value for determining whether a Pod can be scheduled is the Requests section under
"Allocated resources:" obtained from kubectl describe node .

image

This is because if these values are close to 100% (for example, 99%), attempting to schedule a Pod will result in a resource shortage, making it impossible to schedule.

So, how can we obtain this value using a Prometheus query in Grafana?

The reason I am asking this question is that while the query
kube_node_status_allocatable{resource="memory"}
can be used to obtain the total capacity of the node, the sum of the memory requests of currently scheduled Pods obtained with
sum by (node) (kube_pod_container_resource_requests{resource="memory"})
clearly exceeds the node's capacity. Each of my nodes has 16Gi of memory, but this query returns a total that exceeds 16Gi.

  • sum by (node) (kube_pod_container_resource_requests{resource="memory"})
    image

18.2Gi ...? (Worker node is 16Gi memory spec.)

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 10, 2024
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants