-
Notifications
You must be signed in to change notification settings - Fork 260
Setup SNAT Configuration Based on Azure Host Support #401
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
f90ee37 to
4ace0a3
Compare
tamilmani1989
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.
unit tests are missing.
d03e72c to
dbf83ed
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
49a7ee1 to
70ffe52
Compare
cd8e5be to
779622e
Compare
266efc2 to
18ce2de
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
a634e1d to
df3ed5b
Compare
df3ed5b to
9a6b604
Compare
tamilmani1989
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.
minor comments
4de34f9 to
bf243f3
Compare
tamilmani1989
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.
lgtm
bf243f3 to
62168c2
Compare
62168c2 to
304d082
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
What this PR does / why we need it:
CNI will now query for SNAT and DNS support from Azure Host.
In Linux, the features can be separately applied; but on Windows SNAT will only be disabled if both new features on the Host are supported.