-
Notifications
You must be signed in to change notification settings - Fork 716
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
Allow e2e tests to use CI builds of control plane images #238
Comments
See also: kubernetes/test-infra#1400 #101 Maybe you @pipejakob could take ownership over kubernetes/test-infra#1400? |
@mikedanese @pipejakob @ixdy Did the pushing of master images to gcr.io ever happen or is it yet to be done? |
still tbd. |
Work being done now in: kubernetes/test-infra#1400 |
Sent a PR for this kubernetes/test-infra#4176 |
This is now fixed; relevant extract from latest CI e2e runs:
vs earlier
Now we can detect regressions at HEAD much faster, yay 🎉 |
Is this a BUG REPORT or FEATURE REQUEST?
FEATURE REQUEST (of e2es)
When our e2e tests are run, they pass a parameter to
kubeadm init
to specify the release of Kubernetes to use for the control plane images (i.e.--kubernetes-version latest
). This means that there can be lag between a bug being merged to kubernetes/master and exercising of that code in a kubeadm e2e, since our e2e infrastructure can only use images built as part of releases (even if those are alpha/beta/rc releases).It would be great if we could create CI builds of these control plane images and use them as part of our e2e tests to close the gap between regression and detection of non-kubeadm code.
The text was updated successfully, but these errors were encountered: