Egress Gateway performance testing #37753
Merged
Conversation
This file contains hidden or 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
1ddd00a to
447532b
Compare
It is never used, so let's save a bit of time by not enabling it. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
0a1f9cf to
8016f29
Compare
|
/scale-egw |
Let's leverage the dedicated egw_scale_test_failed_tests_total metric. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
Add a step at the end of the egress gateway scale test to measure the network performance for pod to external endpoint traffic, potentially flowing through the egress gateway. More specifically, we leverage the cilium connectivity perf tool and configure it to deploy the client on one of the cluster nodes (in pod network), and the server on the external node (in host network). The egress gateway policy is updated to additionally match the client pod. Signed-off-by: Marco Iorio <marco.iorio@isovalent.com>
8016f29 to
62abf45
Compare
|
/scale-egw |
|
/test |
aanm
approved these changes
Feb 27, 2025
christarazi
approved these changes
Feb 28, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Add a step at the end of the egress gateway scale test to measure the network performance for pod to external endpoint traffic, potentially flowing through the egress gateway. More specifically, we leverage the cilium connectivity perf tool and configure it to deploy the client on one of the cluster nodes (in pod network), and the server on the external node (in host network). The egress gateway policy is updated to additionally match the client pod.