This repository has been archived by the owner on Jul 11, 2023. It is now read-only.
tests/e2e: client-server deployment traffic split test #1823
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
- Test runs HTTP from multiple source client deployments to one destination traffic split, backed by multiple server services - Number of clients and servers backing the traffic split is tunable By default: - 2 Clients with 5 replicaset - 5 Servers with 2 replicaset - Adds traffic targets - Creates traffic split service and adds all servers to as traffic split backends. It then tests traffic from all clients to the traffic split FQDN. - Server instances are instrumented to reply with their pod name. The test will also verify all server backing the traffic split are actually and eventually reached.
eduser25
force-pushed
the
trafficsplit-test
branch
from
958fb7c to
070df73
Compare
shashankram
reviewed
Oct 13, 2020
shashankram
approved these changes
Oct 13, 2020
snehachhabria
approved these changes
Oct 13, 2020
eduser25
added a commit
to eduser25/osm
that referenced
this pull request
Oct 14, 2020
…sh#1823) - Test runs HTTP from multiple source client deployments to one destination traffic split, backed by multiple server services - Number of clients and servers backing the traffic split is tunable By default: - 2 Clients with 5 replicaset - 5 Servers with 2 replicaset - Adds traffic targets - Creates traffic split service and adds all servers to as traffic split backends. It then tests traffic from all clients to the traffic split FQDN. - Server instances are instrumented to reply with their pod name. The test will also verify all server backing the traffic split are actually and eventually reached.
draychev
pushed a commit
to draychev/osm
that referenced
this pull request
Oct 28, 2020
…sh#1823) - Test runs HTTP from multiple source client deployments to one destination traffic split, backed by multiple server services - Number of clients and servers backing the traffic split is tunable By default: - 2 Clients with 5 replicaset - 5 Servers with 2 replicaset - Adds traffic targets - Creates traffic split service and adds all servers to as traffic split backends. It then tests traffic from all clients to the traffic split FQDN. - Server instances are instrumented to reply with their pod name. The test will also verify all server backing the traffic split are actually and eventually reached.
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.
destination traffic split, backed by multiple server services
By default:
It then tests traffic from all clients to the traffic split FQDN.
also verify all server backing the traffic split are actually and eventually
reached.
Affected area:
Tests [X]
Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution?
No