RFC: DRA: optional allocation
-
One-line PR description: optional allocation
-
Issue link: https://github.com/kubernetes/enhancements/issues/4381
-
Other comments:
Running a pod without some resource may be useful if there is a fallback in the application code. Allocating more than one may also be useful, in particular when the upper bound is unlimited. Then it becomes possible to ask for all instances available on a node in a daemon set.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: pohly Once this PR has been reviewed and has the lgtm label, please assign derekwaynecarr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
/close
Will become part of a future KEP updated after prototyping it in https://github.com/kubernetes-sigs/wg-device-management.
@pohly: Closed this PR.
In response to this:
/close
Will become part of a future KEP updated after prototyping it in https://github.com/kubernetes-sigs/wg-device-management.
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.