Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Run e2e tests for 1.19 #349

Merged
merged 2 commits into from
Oct 6, 2020
Merged

Run e2e tests for 1.19 #349

merged 2 commits into from
Oct 6, 2020

Conversation

timoreimann
Copy link
Contributor

This change adds 1.19 to the list of Kubernetes versions we run e2e tests for.

Other drive-improvements include:

  • Add script get-e2etest-sha256.sh to get the SHA256 sum of a e2e.test binary of a given Kubernetes release (needed to update the e2e test runner Dockerfile image).
  • Update the "How to add support for a new Kubernetes release" checklist.

Copy link
Contributor

@adamwg adamwg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

Timo Reimann added 2 commits October 6, 2020 00:23
This change adds 1.19 to the list of Kubernetes versions we run e2e
tests for.

Other drive-improvements include:

- Add script `get-e2etest-sha256.sh` to get the SHA256 sum of a e2e.test
  binary of a given Kubernetes release (needed to update the e2e test
  runner Dockerfile image).
- Update the "How to add support for a new Kubernetes release"
  checklist.
@timoreimann timoreimann force-pushed the upgrade-e2e-tests-for-1.19 branch from 6d4be3b to d4f8b95 Compare October 5, 2020 22:24
@timoreimann timoreimann marked this pull request as ready for review October 6, 2020 16:20
@timoreimann timoreimann merged commit a6f5d96 into master Oct 6, 2020
@timoreimann timoreimann deleted the upgrade-e2e-tests-for-1.19 branch October 6, 2020 16:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants