buildscripts: Add missing secondary_kube_context to xds LB tests #9380
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
sergiitk
force-pushed
the
xds-k8s-fix-failover
branch
from
d0c4feb
to
88352b4
Compare
sergiitk
force-pushed
the
xds-k8s-fix-failover
branch
from
88352b4
to
2382238
Compare
sergiitk
force-pushed
the
xds-k8s-fix-failover
branch
from
2382238
to
8e8cd8a
Compare
YifeiZhuang
approved these changes
Jul 15, 2022
sergiitk
changed the title
sergiitk
changed the title
larry-safran
pushed a commit
to larry-safran/grpc-java
that referenced
this pull request
Jul 18, 2022
temawi
pushed a commit
to temawi/grpc-java
that referenced
this pull request
Jul 22, 2022
…c#9380) Secondary cluster was not activated for LB tests. This resulted in the failover test failing, as it relies on workloads running in different zones. ref b/238226704
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Secondary cluster was not activated for LB tests. This resulted in the failover test failing, as it relies on workloads running in different zones.
ref b/238226704