It used to be necessary to override from where the E2E suite came on a case-by-case basis (initially, testing was using a more recent suite against an older Kubernetes). This should never become necessary again and the lack of a specific entry for 1.18 already had the unintended effect that Kubernetes 1.18 was tested with the suite from master, so overall it is better to always use the E2E suite which matches Kubernetes.
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... |