-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding support of UDN usage #156
Conversation
https://redhat-internal.slack.com/archives/C077NGF5HE1/p1728676760441059 - I wonder if the annotation will eventually get better? |
@jtaleric @rsevilla87 should we do more tests or can we merge this change? |
Using the UDN ip from the Server pod annotations. Service and IPv6 are not supported Using --udn option create a UserDefinedNetwork object on the netperf ns
@jtaleric @rsevilla87 did you have the time to take a look at it? |
@rsevilla87 @jtaleric I have updated the PR. Sorry for the late response, I had no OCP cluster to test the change last week. |
@rsevilla87 @jtaleric is it okay to merge this? My next step would be to add the UDN support for VMs |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
Using --udn option create a UserDefinedNetwork object on the netperf ns
Type of change
Description
This new option deploys a UDN network in the netperf Namespace. All the pods are using the UDN interface to contact each other.
It does not support Service and IPv6 (even if the implementation of v6 looks straightforward).
It uses the CRD
userdefinednetworks
and not a NAD to create the UDN interfaces on the pods.Related Tickets & Documents
Checklist before requesting a review
Testing