kubernetes
RFC: KEP-4381: DRA: network-attached resources
-
One-line PR description: nework-attached resources
-
Issue link: https://github.com/kubernetes/enhancements/issues/4381
-
Other comments:
Adding support for network-attached resources by extending the ResourceSlice with a node selector is fairly easy. The (one!) scheduler in the cluster can use that field during Filter instead of the node name.
Supporting multiple schedulers is harder and needs further work.
[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 dchen1107 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
When 'Network-attached resources' is said what exactly is the scope of this? Could it be a simple veth case or is this leaning more towards virtual functions?
This PR is not about network hardware in a node. That kind of resource is local to a node and already covered.
What this PR adds is support for things like an IP camera (accessible through the IP network) or special devices that can be accessed through some kind of fabric (GPU via PCI switch). Those resources are not local to a node and therefore need to be handled differently.
/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.