From 04fb8190fe611a7e2ebafc5384c5c734b61d13ee Mon Sep 17 00:00:00 2001 From: Vasilis Remmas Date: Wed, 24 Jul 2024 09:15:34 +0200 Subject: [PATCH] Update DRA integration info and e2e test Signed-off-by: Vasilis Remmas --- docs/how-to-use.md | 3 +++ e2e/test-dra-integration.sh | 7 ++++--- 2 files changed, 7 insertions(+), 3 deletions(-) diff --git a/docs/how-to-use.md b/docs/how-to-use.md index 09197162b..c9af017f5 100644 --- a/docs/how-to-use.md +++ b/docs/how-to-use.md @@ -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/), > 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. +> +> 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 resources. diff --git a/e2e/test-dra-integration.sh b/e2e/test-dra-integration.sh index 997996cb4..2d8e46e5d 100755 --- a/e2e/test-dra-integration.sh +++ b/e2e/test-dra-integration.sh @@ -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 # 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: -# - We explitictly don't pin the revision of the dra-example-driver to a specific commit to ensure that the integration -# continues to work even when the dra-example-driver is updated (which may also indicate API changes on the DRA). +# - We explitictly pin the revision of the dra-example-driver to the branch `classic-dra` to indicate that the +# 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 # e2e suite runs. echo "installing dra-example-driver" repo_path="repos/dra-example-driver" 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 KIND_CLUSTER_NAME=kind ${repo_path}/demo/scripts/load-driver-image-into-kind.sh chart_path=${repo_path}/deployments/helm/dra-example-driver/