Open githubeto opened 2 weeks ago
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.
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.
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 withsum 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"})
18.2Gi ...? (Worker node is 16Gi memory spec.)