-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Pull kubectl-skew tests out from other upgrade tests, since it's a different matrix #109
Conversation
This also removes the usage of |
cc @maisem |
01551b1
to
05609aa
Compare
provider: 'gke' | ||
provider-env: '{gke-provider-env}' | ||
jobs: | ||
- 'kubernetes-e2e-{provider}-{version-cluster}-{version-client}-kubctl-skew': |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
kubectl :)
05609aa
to
b9d4902
Compare
@spxtr PTAL. |
Looks fine to me. cc @fejta who is looking into cleaning up this file. I think the plan is to move the upgrade jobs into their own file. We'll have to duplicate the job template stuff, but I think that's fine. |
I'll happily make sure to merge your changes |
Automatic merge from submit-queue Always skew the client when running version-skew tests As mentioned in the comments: - for upgrade jobs, we want kubectl to be at the same version as master. - for client skew tests, we want to use the skewed kubectl (that's what we're testing). So, remove gate on `JENKINS_USE_SKEW_KUBECTL`, and always use the skewed `kubectl`. This should go in before kubernetes/test-infra#109.
kubernetes/kubernetes#26789 is in; merging this. |
Rollback minikube to 0.23.0
Updating go version.
This is a result of kubernetes/kubernetes#25087; the matrix that we care about is different for node-master and client-master skews.