-
Notifications
You must be signed in to change notification settings - Fork 25
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
Dualstack test case #108
Dualstack test case #108
Conversation
4f726ce
to
f5e643c
Compare
Needed so we can assign workloads from separate deployments to the same service, therefore the same NEG.
This reverts commit f569189.
… some servers binding only 1 ip version.
… the service is created as IPv4 Only) and addressed a code review cleanup comment.
f5e643c
to
e927382
Compare
…ified. This is only needed after aborting a run that had created a client before it could cleanup.
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.
Mostly LGTM, but let's make sure to fix server namespace cleanup order
Previous test runs passed, deflaking CSM: |
Re deflaking CSM: I just realized the grpcroute test is now expected to fail, so Arvin added a temporary skip in another PR. So no need to wait for the other adhoc run to finish. |
Co-authored-by: Sergii Tkachenko <[email protected]>
Co-authored-by: Sergii Tkachenko <[email protected]>
Have a test case that initializes 3 servers. They will each have different --address_type arguments from: "ipv4_ipv6", "ipv4", "ipv6". It will then create a client and run the round robin test ensuring that all 3 receive traffic. Due to warmup, we aren't concerned about equal traffic.
Once Java 1.66 is cut, update canonical server to point to it so that it has support for the address_type argument