Add dual-stack support for Antrea Egress#7761
Draft
XinShuYang wants to merge 3 commits intoantrea-io:mainfrom
Draft
Add dual-stack support for Antrea Egress#7761XinShuYang wants to merge 3 commits intoantrea-io:mainfrom
XinShuYang wants to merge 3 commits intoantrea-io:mainfrom
Conversation
82fc42e to
766a9fb
Compare
c4151f9 to
71371c1
Compare
93e34cc to
c35a752
Compare
Contributor
Author
|
/test-ipv6-e2e |
41ea06f to
cbe1265
Compare
Contributor
Author
|
/test-ipv6-e2e |
6fea007 to
51a62d3
Compare
Contributor
Author
|
/test-ipv6-e2e |
Introduce dual-stack Egress by enabling new fields spec.egressIPs and spec.externalIPPools. Both IPv4 and IPv6 egress IPs are always scheduled to the same Node via an extended consistent hash scheduler. The antrea-controller allocates IPs atomically from their respective ExternalIPPools in egress HA mode. The antrea-agent handles dual-stack Egress through a dedicated sync path that installs per-IP SNAT mark flows and iptables rules, and installs per-Pod OFPort flows for both IP families. Admission webhook validation ensures the dual-stack and single-stack fields are mutually exclusive. Signed-off-by: Shuyang Xin <shuyang.xin@broadcom.com>
Signed-off-by: Shuyang Xin <shuyang.xin@broadcom.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 17 out of 17 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 17 out of 17 changed files in this pull request and generated 1 comment.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
You can also share your feedback on Copilot code review. Take the survey.
| // We don't care about the value of egress.Spec.EgressIPs, just use it to reach a consensus among all agents | ||
| // about which one should do the update. | ||
| if len(egress.Spec.EgressIPs) != expectedDualStackCount { | ||
| return fmt.Errorf("spec.EgressIPs is unavailable, the dual-stack egress status failed to update") |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Introduce dual-stack Egress by enabling new fields spec.egressIPs and
spec.externalIPPools. Both IPv4 and IPv6 egress IPs are always scheduled
to the same Node via an extended consistent hash scheduler.
The antrea-controller allocates IPs atomically from their respective
ExternalIPPools in egress HA mode.
The antrea-agent handles dual-stack Egress through a dedicated sync path
that installs per-IP SNAT mark flows and iptables rules, and installs
per-Pod OFPort flows for both IP families.
Admission webhook validation ensures the dual-stack and single-stack
fields are mutually exclusive.