DRA: Device Binding Conditions

[pohly]

Enhancement Description

• One-line enhancement description: Some network- or fabric-attached devices need to be attached to a node before a pod using them can be scheduled.
• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-scheduling/5007-device-attach-before-pod-scheduled/README.md
• Discussion Link: DRA: structured parameters: network-attached resource kubernetes#124042 (comment)
• Primary contact (assignee): @pohly, @KobayashiD27, @ttsuuubasa
• Responsible SIGs:
  /sig scheduling
  /wg device-management
• Enhancement target (which target equals to which milestone):
  • Alpha release target: 1.33
  • Beta release target: TBD
  • Stable release target: TBD
• Alpha (v1.34)
  • KEP (k/enhancements) update PR(s):
    • KEP-5007: DRA Device Binding Conditions #5012
    • Update KEP-5007 DRA Device Binding Conditions #5342
  • Code (k/k) update PR(s): Implement DRA Device Binding Conditions (KEP-5007) kubernetes#130160
  • Docs (k/website) update PR(s): DRA Device Binding Conditions #5007 document website#49814
• Alpha (v1.35)
  • KEP (k/enhancements) update PR(s):
    • KEP-5007: DRA Device Binding Conditions alpha in 1.35 #5487
    • TODO: update kep.yaml back to alpha
  • Code (k/k) update PR(s):
    • scheduler: KEP-5007 allocator test - devices w/wo BindingConditions kubernetes#134967
    • scheduler: KEP-5007 add integration tests on DeviceBindingConditions kubernetes#134942
    • scheduler: KEP-5007 Add BindingTimeout args to DynamicResources plugin kubernetes#134905
  • Docs (k/website) update PR(s): KEP-5007: DRA Device Binding Conditions beta in 1.36 #5846
• Beta (v1.36)
  • KEP (k/enhancements) update PR(s): KEP-5007: DRA Device Binding Conditions beta in 1.36 #5846
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):

<--

• Stable
  • KEP (k/enhancements) update PR(s):
  • Code (k/k) update PR(s):
  • Docs (k/website) update(s):
    -->

Please keep this description up to date. This will help the Enhancement Team to track the evolution of the enhancement efficiently.

[pohly]

/assign @KobayashiD27

As discussed in kubernetes/kubernetes#124042 (comment).

/sig scheduling
/wg device-management

[k8s-ci-robot]

@pohly: GitHub didn't allow me to assign the following users: KobayashiD27.

Note that only kubernetes members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @KobayashiD27

As discussed in kubernetes/kubernetes#124042 (comment).

/sig scheduling
/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.

[KobayashiD27]

Thank you for creating the issue. I will post a draft KEP as soon as possible.

[KobayashiD27]

@pohly

To facilitate the discussion on the KEP, we would like to share the design of the composable controller we are considering as a component utilizing the fabric-oriented scheduler function. By sharing this, we believe we can deepen the discussion on the optimal implementation of the scheduler function. Additionally, we would like to verify whether the controller design matches the DRA design.

Background

Our controller's philosophy is to efficiently utilize fabric devices. Therefore, we prefer to allocate devices directly connected to the node over attached fabric devices. (e.g., Node-local devices > Attached fabric devices > Pre-attached fabric devices)

Design Overview

This design aims to efficiently utilize fabric devices, prioritizing node-local devices to improve performance. The composable controller manages fabric devices that can be attached and detached. Therefore, it publishes a list of fabric devices as ResourceSlices.

The structure we are considering is as follows:

# composable controller publish this pool
kind: ResourceSlice
pool: composable-device
driver: gpu.nvidia.com
nodeSelector: fabric1
devices:
  - name: device1
  ...
  - name: device2
  ...

The vendor's DRA kubelet plugin will also publish the devices managed by the vendor as ResourceSlices.

# vendor DRA kubelet plugin publish this pool
kind: ResourceSlice
pool: Node1
driver: gpu.nvidia.com
nodeName: Node1
devices:
  - name: device3
  ...

Here, when the scheduler selects the fabric device device1, it waits for the attachment of the fabric device during PreBind. The composable controller performs the attachment operation by checking the flag of the ResourceClaim. After successful attachment, the composable controller changes the flag of the ResourceClaim.

We are considering the following two methods for handling ResourceSlices upon completion of the attachment. We would like to hear your opinions and feasibility on these two composable controller proposals.

Proposal 1: The composable controller publishes ResourceSlices with NodeName set within the pool

Multiple ResourceSlices are published with the same pool name. One indicates the devices included in the fabric, and the other indicates the devices attached to the node.

# composable controller publish this pool
kind: ResourceSlice
pool: composable-device
driver: gpu.nvidia.com
nodeSelector: fabric1
devices:
  - name: device2
  ...
---
kind: ResourceSlice
pool: composable-device
driver: gpu.nvidia.com
nodeName: Node1
devices:
  - name: device1
  ...

If the vendor's plugin responds to hotplug, device1 will appear in the ResourceSlice published by the vendor.

# vendor DRA kubelet plugin publish this pool
kind: ResourceSlice
pool: Node1
driver: gpu.nvidia.com
nodeName: Node1
devices:
  - name: device3
  ...
  - name: device1
  ...

This may cause device duplication issues between ResourceSlices. To prevent multiple ResourceSlices from publishing duplicate devices, we plan to define a deny list and standardize it with DRA.

Advantages

• No need to change the allocationResult by the scheduler or composable controller.
• Can distinguish attached fabric devices and maintain prioritization.

Disadvantages

• ResourceSlices created by the composable controller may not be understood by the vendor kubelet plugin. (NVIDIA drivers use internal information, so cooperation is needed)
• Attached and unattached fabric devices are mixed in one pool. (DRA: structured parameters: network-attached resource kubernetes#124042 (comment))
• A mechanism to prevent device duplication is needed (e.g., deny list).

Proposal 2: Attached devices are published by the vendor's plugin

In this case, devices are removed from the composable-device pool.

# composable controller publish this pool
kind: ResourceSlice
pool: composable-device
driver: gpu.nvidia.com
nodeSelector: fabric1
devices:
  - name: device2
  ...

If the vendor's plugin responds to hotplug, device1 will appear in the ResourceSlice published by the vendor.

# vendor DRA kubelet plugin publish this pool
kind: ResourceSlice
pool: Node1
driver: gpu.nvidia.com
nodeName: Node1
devices:
  - name: device3
  ...
  - name: device1
  ...

This breaks the linkage between ResourceClaim and ResourceSlice. Therefore, it is necessary to modify the AllocationResult of the ResourceClaim.

Advantages

• Simplifies device management.
• Centralizes management as the vendor's plugin directly publishes devices.
• No need for mechanisms to prevent device duplication (e.g., deny list).

Disadvantages

• Cannot distinguish attached fabric devices, making prioritization difficult.
• Requires modification of the linkage between ResourceClaim and ResourceSlice (expected to be done by the scheduler or DRA controller. Which is more appropriate?).
• Until the linkage is fixed, the device being used may be published as a ResourceSlice and reserved by other Pods.

We would appreciate your feedback and insights on these proposals to ensure the optimal implementation of the scheduler function and alignment with the DRA design.

[pohly]

Let's keep the discussion in this issue shorter. You now can put all of this, including the alternatives, into the KEP document.