-
Notifications
You must be signed in to change notification settings - Fork 260
Remove bridgeName field from CNI windows conflist files #3135
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
Conversation
e91aaf7 to
72a8bd7
Compare
QxBytes
left a comment
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.
So just confirming that "bridge" (the field) isn't used in windows, and mode will default to bridge if it is not specified? Could you also run the full pipeline with this change?
|
@QxBytes pipeline passes |
a1c4831 to
69e6239
Compare
QxBytes
left a comment
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.
On windows, a reference search for the bridgeName field of endpoint info does not reveal any usages. it seems like you're only modifying windows conflists so there shouldn't be any effect.
69e6239 to
abe6d77
Compare
|
/azp run Azure Container Networking PR |
|
Azure Pipelines successfully started running 1 pipeline(s). |
remove bridgeName field from CNI windows conflist files
Reason for Change:
This PR is to cleanup windows cni config file to remove bridgeName fields
Issue Fixed:
Requirements:
Notes: