-
Notifications
You must be signed in to change notification settings - Fork 4.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
Give kubetest2 its own makefile #10577
Conversation
/test pull-kops-e2e-kubernetes-aws-kubetest2 |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rifelpet The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
115dd5c
to
18ca211
Compare
/test pull-kops-e2e-kubernetes-aws-kubetest2 |
Use GOOS and GOARCH for running the kops binary Also try deploying and testing against k8s 1.20.2
18ca211
to
59c312f
Compare
/test pull-kops-e2e-kubernetes-aws-kubetest2 |
/lgtm |
/retest Review the full test history for this PR. Silence the bot with an |
This will help avoid cluttering up the main Makefile even further. I'm imagining we could put all our variants, perhaps even grid combinations (k8s version + distro + networking + cloud). That should greatly simplify the periodic job definitions.
Using GOOS and GOARCH for running the kops binary
Also try deploying and testing against k8s 1.20.2.
I'm not optimistic based on previous runs but we'll see how it goes this time. I may end up reverting back to 1.19 until we can figure out whats causing the failures.