-
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
Kubetest2 - terraform support #10697
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 |
/test pull-kops-e2e-kubernetes-aws-kubetest2 |
/test pull-kops-e2e-kubernetes-aws-kubetest2 |
1 similar comment
/test pull-kops-e2e-kubernetes-aws-kubetest2 |
0d1ccbb
to
6311373
Compare
/test pull-kops-e2e-kubernetes-aws-kubetest2 |
/retest |
6311373
to
6e8a329
Compare
I backed out the makefile update so this should be ready for review now. I noticed an interesting behavior that I'm hoping is the source of some of our test job problems... When I was porting over the kops commands from kubetest1 to kubetest2 I copied the We built that logic into The k8s e2e test framework has a --num-nodes flag that is used in some tests and defaults to the number of Ready and Schedulable nodes fetched at startup. Kops not waiting for nodes to stop flapping their readiness caused the e2e framework to incorrectly detect the number of nodes, and some tests were being skipped as a result. See Line 7335 here. I'm hoping the |
/lgtm |
1 similar comment
/lgtm |
This adds support for
--target terraform
and applying/destroying the cluster using terraform.The specified terraform version is downloaded and unzipped each run, ideally we could cache this or use tfenv or something.