Include extended resources like GPU for node order
mateuszlitwin opened this issue · comments
Is this a BUG REPORT or FEATURE REQUEST?:
/kind feature
What happened:
Extended resources like nvidia.com/gpu are not being used for node ordering, only CPU and memory are.
Support for prioritization based on extended resources has already been added in Kubernetes 1.16.0 (kubernetes/kubernetes@9ae5059) it would be very useful to have this supported in kube-batch as well.
Extra question: is there a plan to use more recent Kubernetes libraries for kube-batch? I would be happy to upgrade kube-batch to newer version unless it is not advised.
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
@fejta-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue with/reopen.
Mark the issue as fresh with/remove-lifecycle rotten.Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close
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/test-infra repository.