A library function to calculate Pod resource utilization about kubernetes HOT 13 OPEN

I think the hard part of this would be the same as why we can't move validation into staging. Some of those fields may not belong in staging like pod validation opts.

+1
This function relies /pkg/api/v1/pod and PodResourcesOptions and both of them are not in staging.

I'm +1 for having this but I think maybe we need to move both /pkg/api/v1/pod and /pkg/api/v1/resource to component-helpers

from kubernetes.

I've created #124609 to simply move both /pkg/api/v1/pod and /pkg/api/v1/resource to component-helpers.

To fully solve this problem, we need to replace the function pointed out in #124537 (comment) with the function in component-helpers.

I tend to replace them after #124609 if we all agree the movement, to reduce the complexity of #124609.

from kubernetes.

/sig scheduling

from kubernetes.

cc @liggitt for any concerns

from kubernetes.

+1, I think this would be helpful to have as a generic library function to generate resource requirements for pods.

from kubernetes.

/sig node

cc @SergeyKanzhelev @gjkim42

from kubernetes.

I think the hard part of this would be the same as why we can't move validation into staging. Some of those fields may not belong in staging like pod validation opts.

from kubernetes.

This one is easier. It's based on versioned types.

from kubernetes.

We also wanted to implement this: #115643

Those are not mutually exclusive, just pointing that for many use cases reading pod status may be a better idea.

from kubernetes.

btw, this function by itself was a result of the big effort: #115367

from kubernetes.

I think kubectl also faces this problem:

We now maintain this same function in three different places, I'll try if we can merge these three function into one in pkg component-helpers.

from kubernetes.

/triage accepted

Reusing the same code in scheduler and kubelet would be highly beneficial in quite a few flows

from kubernetes.

/assign

from kubernetes.