CNI Ipv6 Dualstack Support #538
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
tamilmani1989
changed the title
tamilmani1989
changed the title
…working into cniv6_chain # Conflicts: # Makefile
matmerr
reviewed
Apr 8, 2020
matmerr
reviewed
Apr 8, 2020
matmerr
reviewed
Apr 8, 2020
matmerr
reviewed
Apr 15, 2020
matmerr
reviewed
Apr 15, 2020
matmerr
reviewed
Apr 15, 2020
matmerr
reviewed
Apr 15, 2020
tamilmani1989
commented
Apr 16, 2020
matmerr
approved these changes
Apr 16, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
What this PR does / why we need it:
This PR adds ipv6 datapath support for containers. The ipv6 ips are non-vnet ips and connection across VM works only with Azure udr solution. The containers will get ipv6 address inaddtion to vnet ipv4 address. containers within VM can communicate directly via ipv6. For Container communication across VMs, the src ip has to snat with vnet ipv6 CA.
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Release note: