You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Create a kind cluster with two worker nodes so that the topology feature can be tested. Test cases that test accessing volumes from multiple nodes need to be skipped
# kubeadm has API dependencies between apiVersion and Kubernetes version
@@ -840,10 +845,6 @@ run_e2e () (
840
845
install_e2e || die "building e2e.test failed"
841
846
install_ginkgo || die "installing ginkgo failed"
842
847
843
-
# TODO (?): multi-node cluster (depends on https://github.com/kubernetes-csi/csi-driver-host-path/pull/14).
844
-
# When running on a multi-node cluster, we need to figure out where the
845
-
# hostpath driver was deployed and set ClientNodeName accordingly.
846
-
847
848
generate_test_driver >"${CSI_PROW_WORK}/test-driver.yaml"|| die "generating test-driver.yaml failed"
848
849
849
850
# Rename, merge and filter JUnit files. Necessary in case that we run the E2E suite again
0 commit comments