Remove blutgang/nginx from e2e tests and just randomize clients #2371
+182
−499
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.
This PR updates our e2e tests to randomize calls to execution clients instead of calling them through a load balancer like
nging
/blutgang
.In our staging env we have had issues with
blutgang
where it was running unstably and restarting frequently. Also when scanning theblutgang
logs it frequently removes nodes from the active set due to them falling behind (and then later adding them back) even if there is almost no load on the network. This resulted in usually always the same node receiving traffic during testing.