Having a convenient way to invoke make setup-e2e test-e2e teardown-e2e while referring to the Helm chart in the registry at oci://registry.k8s.io/dra-example-driver/charts/dra-example-driver instead of the local filesystem will make it easier to do a final smoke test of the promoted artifacts before announcing a release.
|
deployments/helm/dra-example-driver |
The scripts also assume a local build of the container image where we should also make it possible to skip a local build and pull the image instead.
|
# Build the example driver image |
|
${SCRIPTS_DIR}/build-driver-image.sh |
|
|
|
# If a cluster is already running, load the image onto its nodes |
|
EXISTING_CLUSTER="$(${KIND} get clusters | grep -w "${KIND_CLUSTER_NAME}" || true)" |
|
if [ "${EXISTING_CLUSTER}" != "" ]; then |
|
${SCRIPTS_DIR}/load-driver-image-into-kind.sh |
|
fi |
Having a convenient way to invoke
make setup-e2e test-e2e teardown-e2ewhile referring to the Helm chart in the registry atoci://registry.k8s.io/dra-example-driver/charts/dra-example-driverinstead of the local filesystem will make it easier to do a final smoke test of the promoted artifacts before announcing a release.dra-example-driver/test/e2e/setup-e2e.sh
Line 39 in 5f544fa
The scripts also assume a local build of the container image where we should also make it possible to skip a local build and pull the image instead.
dra-example-driver/demo/build-driver.sh
Lines 30 to 37 in 5f544fa