github/multus-cni
1
0
Fork 1
mirror of https://github.com/k8snetworkplumbingwg/multus-cni.git synced 2025-06-23 14:27:09 +00:00
Code Issues Projects Releases Wiki Activity

Update DRA integration info and e2e test

Browse Source 
Signed-off-by: Vasilis Remmas <vremmas@nvidia.com>
This commit is contained in:
Vasilis Remmas 2024-07-24 09:15:34 +02:00
parent 8587734174
commit 04fb8190fe
No known key found for this signature in database
GPG Key ID: 75BE2DCF63A193FF
2 changed files with 7 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
docs/how-to-use.md
View File

@ -640,6 +640,9 @@ If you wish to have auto configuration use the `readinessindicatorfile` in the c
> :warning: Dynamic Resource Allocation (DRA) is [currently an alpha](https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/), > :warning: Dynamic Resource Allocation (DRA) is [currently an alpha](https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation/),
> and is subject to change. Please consider this functionality as a preview. The architecture and usage of DRA in > and is subject to change. Please consider this functionality as a preview. The architecture and usage of DRA in
> Multus CNI may change in the future as this technology matures. > Multus CNI may change in the future as this technology matures.
>
> The current DRA integration is based on the DRA API for Kubernetes 1.26 to 1.30. With Kubernetes 1.31, the DRA API
> will change and multus doesn't integrate with the new API yet.
Dynamic Resource Allocation is alternative mechanism to device plugin which allows to requests pod and container Dynamic Resource Allocation is alternative mechanism to device plugin which allows to requests pod and container
resources. resources.

7
e2e/test-dra-integration.sh
View File

@ -6,15 +6,16 @@ export PATH=${PATH}:./bin
# This test is using an example implementation of a DRA driver. This driver is mocking GPU resources. At our test we # This test is using an example implementation of a DRA driver. This driver is mocking GPU resources. At our test we
# don't care about what these resources are. We want to ensure that such resource is correctly passed in the Pod using # don't care about what these resources are. We want to ensure that such resource is correctly passed in the Pod using
# Multus configurations. A couple of notes: # Multus configurations. A couple of notes:
# - We explitictly don't pin the revision of the dra-example-driver to a specific commit to ensure that the integration # - We explitictly pin the revision of the dra-example-driver to the branch `classic-dra` to indicate that the
# continues to work even when the dra-example-driver is updated (which may also indicate API changes on the DRA). # integration continues to work even when the dra-example-driver is updated. We know that classic-dra is supported
# in Kubernetes versions 1.26 to 1.30. Multus supports DRA in the aforementioned Kubernetes versions.
# - The chart and latest is image is not published somewhere, therefore we have to build locally. This leads to slower # - The chart and latest is image is not published somewhere, therefore we have to build locally. This leads to slower
# e2e suite runs. # e2e suite runs.
echo "installing dra-example-driver" echo "installing dra-example-driver"
repo_path="repos/dra-example-driver" repo_path="repos/dra-example-driver"
rm -rf $repo_path || true rm -rf $repo_path || true
git clone https://github.com/kubernetes-sigs/dra-example-driver.git ${repo_path} git clone --branch classic-dra https://github.com/kubernetes-sigs/dra-example-driver.git ${repo_path}
${repo_path}/demo/build-driver.sh ${repo_path}/demo/build-driver.sh
KIND_CLUSTER_NAME=kind ${repo_path}/demo/scripts/load-driver-image-into-kind.sh KIND_CLUSTER_NAME=kind ${repo_path}/demo/scripts/load-driver-image-into-kind.sh
chart_path=${repo_path}/deployments/helm/dra-example-driver/ chart_path=${repo_path}/deployments/helm/dra-example-driver/