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
configvar CSI_PROW_E2E_VERSION_1_13 v1.14.0 "E2E version for Kubernetes 1.13.x"# we can't use the one from 1.13.x because it didn't have --storage.testdriver
203
+
# TOOO: remove versioned variables and make e2e version match k8s version
204
204
configvar CSI_PROW_E2E_VERSION_1_14 v1.14.0 "E2E version for Kubernetes 1.14.x"
205
205
configvar CSI_PROW_E2E_VERSION_1_15 v1.15.0 "E2E version for Kubernetes 1.15.x"
206
+
configvar CSI_PROW_E2E_VERSION_1_16 v1.16.0 "E2E version for Kubernetes 1.16.x"
206
207
# TODO: add new CSI_PROW_E2E_VERSION entry for future Kubernetes releases
207
208
configvar CSI_PROW_E2E_VERSION_LATEST master "E2E version for Kubernetes master"# testing against Kubernetes master is already tracking a moving target, so we might as well use a moving E2E version
208
209
configvar CSI_PROW_E2E_REPO_LATEST https://github.com/kubernetes/kubernetes "E2E repo for Kubernetes >= 1.13.x"# currently the same for all versions
@@ -292,11 +293,6 @@ regex_join () {
292
293
# alpha in previous Kubernetes releases. This was considered too
293
294
# error prone. Therefore we use E2E tests that match the Kubernetes
294
295
# version that is getting tested.
295
-
#
296
-
# However, for 1.13.x testing we have to use the E2E tests from 1.14
297
-
# because 1.13 didn't have --storage.testdriver yet, so for that (and only
298
-
# that version) we have to define alpha tests differently.
299
-
configvar CSI_PROW_E2E_ALPHA_1_13 '\[Feature: \[Testpattern:.Dynamic.PV..block.volmode.\] should.create.and.delete.block.persistent.volumes'"alpha tests for Kubernetes 1.13"# Raw block was an alpha feature in 1.13.
300
296
configvar CSI_PROW_E2E_ALPHA_LATEST '\[Feature:'"alpha tests for Kubernetes >= 1.14"# there's no need to update this, adding a new case for CSI_PROW_E2E for a new Kubernetes is enough
# Some tests are known to be unusable in a KinD cluster. For example,
@@ -723,22 +719,6 @@ install_sanity () (
723
719
run_with_go "${CSI_PROW_GO_VERSION_SANITY}" go test -c -o "${CSI_PROW_WORK}/csi-sanity""${CSI_PROW_SANITY_IMPORT_PATH}/cmd/csi-sanity"|| die "building csi-sanity failed"
724
720
)
725
721
726
-
# Whether the hostpath driver supports raw block devices depends on which version
727
-
# we are testing. It would be much nicer if we could determine that by querying the
728
-
# installed driver's capabilities instead of having to do a version check.
729
-
hostpath_supports_block () {
730
-
local result
731
-
result="$(docker exec csi-prow-control-plane docker image ls --format='{{.Repository}} {{.Tag}} {{.ID}}'| grep hostpath |whileread -r repo tag id;do
732
-
if [ "$tag"=="v1.0.1" ];then
733
-
# Old version because the revision label is missing: didn't have support yet.
734
-
echo"false"
735
-
return
736
-
fi
737
-
done)"
738
-
# If not set, then it must be a newer driver with support.
739
-
echo "${result:-true}"
740
-
}
741
-
742
722
# The default implementation of this function generates a external
743
723
# driver test configuration for the hostpath driver.
0 commit comments