History

Patrick Ohly 2f6c4f5eab e2e: use Ginkgo context All code must use the context from Ginkgo when doing API calls or polling for a change, otherwise the code would not return immediately when the test gets aborted.		2022-12-16 20:14:04 +01:00
..
test-driver	Merge pull request #113976 from swatisehgal/dra-fix-claim-parameter-name	2022-11-18 05:16:30 -08:00
deploy.go	e2e: use Ginkgo context	2022-12-16 20:14:04 +01:00
dra.go	e2e: use Ginkgo context	2022-12-16 20:14:04 +01:00
kind-build-image.sh
kind.yaml
OWNERS
README.md

README.md

Overview

The tests in this directory cover dynamic resource allocation support in Kubernetes. They do not test the correct behavior of arbitrary dynamic resource allocation drivers.

If such a driver is needed, then the in-tree test/e2e/dra/test-driver is used, with a slight twist: instead of deploying that driver directly in the cluster, the necessary sockets for interaction with kubelet (registration and dynamic resource allocation) get proxied into the e2e.test binary. This reuses the work done for CSI mock testing. The advantage is that no separate images are needed for the test driver and that the e2e test has full control over all gRPC calls, in case that it needs that for operations like error injection or checking calls.

Cluster setup

The container runtime must support CDI. The latest cri-o releases contain support, containerd 1.6.x does not. To bring up a kind cluster with containerd built from their main branch, use:

test/e2e/dra/kind-build-image.sh dra/node:latest && \
kind create cluster --config test/e2e/dra/kind.yaml --image dra/node:latest