-
Notifications
You must be signed in to change notification settings - Fork 46
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
Fix TCP Route test #183
Fix TCP Route test #183
Conversation
/cc @kl52752 /assign @bowei |
@AwesomePatrol: GitHub didn't allow me to request PR reviews from the following users: akwi-github. Note that only GoogleCloudPlatform members and repo collaborators can review this PR, and authors cannot review their own PRs. 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. |
92b7e81
to
99ace2f
Compare
/lgtm |
99ace2f
to
293ef8e
Compare
293ef8e
to
cb00cac
Compare
Previously, the tests relied on hardcoded names of NEGs created by neg-controller in GKE cluster. Now all e2e tests can be run without GKE.
cb00cac
to
72a3f0f
Compare
/approve |
/lgtm |
/cc @mag-kol |
{Type: exec.ActionTypeMeta, Name: eventName(negID)}, | ||
{Type: exec.ActionTypeCreate, Name: actionName(exec.ActionTypeCreate, negID)}, |
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.
thisis changing the behavior of the test, isn't it?
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.
yes, previously there were hardcoded references to existing NEGs. Now they are created as needed for the duration of the test
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.
that's a good point, you don't have to change the behaviour of the test. Just create the NEG with raw API call and leave the node as it was (External).
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.
I considered that, but I opted for a simpler solution for now. We can always add another test later
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: AwesomePatrol, bowei, Ramkumar-K 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 |
abfa33a
into
GoogleCloudPlatform:master
Aleksander: Could you PTAL GoogleCloudPlatform#183? Rohit: I’m no longer on this team
Previously, the tests relied on hardcoded names of NEGs created by
neg-controller in GKE cluster. Now all e2e tests can be run without GKE.