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.
BGP peering in a ipv6-only cluster
This PR takes ipv6 support as far as bgp peering for nodes inside the cluster;
NOTE; with this PR ipv6 code is actually used if the nodeIP is recognised as an ipv6 address. Before ipv4 operation was hard-coded.
The CIDR handling does not work yet so the veth devices does not get any (ipv6) addresses. The
kube-bridge
device is howerver assigned an ipv6 address;Design notes
The
iptablesCmdHandler
is now created with protocol;A function for creating the right iptablesCmdHandler is provided to avoid code duplication. The
PodEgressRules
funtions are now methods inNetworkRoutingController
to be able to access ipv6 stuff.The ipset 31-caracter name limitation
This is a problem. The
Refresh
function added "-temp" to the name which together with the "inet6:" prefix made the temp names too long. As a temporary solution just a "-" is added.IMO some hash string like "tmp_d2d362cdc6579390f1c0617d7" shall be used for temporary ipset's to make the temp name independent from the original set name.
Please comment on this.