-
Notifications
You must be signed in to change notification settings - Fork 160
Add a mode to run e2e tests using kubetest2. #712
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
Conversation
Hi @TeweiLuo. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/assign mattcary |
test/k8s-integration/main.go
Outdated
testParams.cloudProviderArgs, err = getGKEKubeTestArgs(*gceZone, *gceRegion, testParams.imageType) | ||
if err != nil { | ||
// Build params for both kubetest and kubetest2 for debugging. | ||
testParams.cloudProviderArgs, err = getGKEKubeTestArgs(*gceZone, *gceRegion, testParams.imageType, false /* useKubeTest2 */) |
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.
If we don't even log an error when, eg kubetest2=false and kubetest2 arg building returns an error, why are we building both sets of args?
It may simplify the logic considerably to just plumb through one set of args.
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.
Agreed - changed to only generate one set of args.
test/k8s-integration/main.go
Outdated
} | ||
case "gce": | ||
testParams.cloudProviderArgsK2 = []string{ | ||
"--legacy-mode", |
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.
could you add a comment for what legacy-mode does? I always forget, and since now kubetest1 can be considered a legacy mode it would be good to not be ambiguous.
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.
Good call. The naming isn't very helpful.
/retest |
@TeweiLuo: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
/ok-to-test |
/retest |
1 similar comment
/retest |
627d76f
to
cfd432d
Compare
Engprod plans to end kubetest support. This diff adds a --use-kubetest2 flag to the integration test driver. Next step is to add a canary test config to validate kubetest2.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mattcary, TeweiLuo 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 |
Engprod plans to end kubetest support. This diff adds a --use-kubetest2 flag to the
integration test driver.
Next step:
What type of PR is this?
/kind feature
What this PR does / why we need it:
Migrate to the latest test-infra supported test runner. Immediate benefits include reducing ssh-related flakiness in kubetest.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: