Commit 7bcee13d added alpha feature gates for Kubernetes 1.19 in the CSI_PROW_E2E_ALPHA_GATES_LATEST variable based on the comment in https://github.com/kubernetes-csi/external-provisioner/pull/493#discussion_r502663402 that alpha testing only runs for the latest Kubernetes. But some components (like external-health-monitor) are configured with a single Prow job which runs the default set of tests on a stable Kubernetes release (currently 1.17). Those tests used to include alpha testing which then broke during Kind cluster startup because the Kubernetes 1.19 feature gates weren't recognized by 1.17. The solution is to disable alpha testing for Kubernetes != latest in the default set of tests.
Name |
Last commit
|
Last update |
---|---|---|
.prow.sh | Loading commit data... | |
CONTRIBUTING.md | Loading commit data... | |
LICENSE | Loading commit data... | |
OWNERS | Loading commit data... | |
README.md | Loading commit data... | |
RELEASE.md | Loading commit data... | |
SECURITY_CONTACTS | Loading commit data... | |
SIDECAR_RELEASE_PROCESS.md | Loading commit data... | |
build.make | Loading commit data... | |
cloudbuild.sh | Loading commit data... | |
cloudbuild.yaml | Loading commit data... | |
code-of-conduct.md | Loading commit data... | |
filter-junit.go | Loading commit data... | |
go-get-kubernetes.sh | Loading commit data... | |
prow.sh | Loading commit data... | |
travis.yml | Loading commit data... | |
update-vendor.sh | Loading commit data... | |
util.sh | Loading commit data... | |
verify-go-version.sh | Loading commit data... | |
verify-shellcheck.sh | Loading commit data... | |
verify-subtree.sh | Loading commit data... | |
verify-vendor.sh | Loading commit data... |