Fix issues when running uperf and uperf-scale modules with multus networks #839
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
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.
…works
Type of change
Description
There is a typo in the code when selecting the IP address of the pods while working with Multus networks. The filter used is
k8s.v1.cni.cncf.io/networks-status, which is invalid. The correct filter should bek8s.v1.cni.cncf.io/network-status.Additionally, the correct naming for the uperf clients has been implemented, ensuring the IP address of the uperf server in the Multus network is properly selected.
Related Tickets & Documents
Checklist before requesting a review
Testing