-
Notifications
You must be signed in to change notification settings - Fork 387
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
Fix IPsec for IPv6 overlays #3155
Fix IPsec for IPv6 overlays #3155
Conversation
Codecov Report
@@ Coverage Diff @@
## main #3155 +/- ##
===========================================
- Coverage 65.32% 54.99% -10.34%
===========================================
Files 268 374 +106
Lines 26903 51533 +24630
===========================================
+ Hits 17574 28339 +10765
- Misses 7417 20747 +13330
- Partials 1912 2447 +535
Flags with carried forward coverage won't be shown. Click here to find out more.
|
build/images/ovs/apply-patches.sh
Outdated
# This patch is necessary to ensure that ovs-monitor-ipsec generates a correct IPsec configuration | ||
# for strongSwan when using IPv6. | ||
# TODO: Switch to official patch once it is merged upstream. | ||
curl https://github.com/antoninbas/ovs/commit/126ec7700080427bf109604d9a49bcca2c74f77d.patch | \ |
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.
should we also check the OVS version here for this patch?
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.
one question which is not related with this PR, I am wondering which one is the correct IPsec
or IPSec
? I saw both in our documents or codes.
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.
- I think this patch can be applied to all OVS versions currently supported by this script
- I believe the most "correct" one is
IPsec
, and we should try to standardize on this one
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.
thanks, I will check and update IPSec
to IPsec
in a separate PR. I am thinking maybe we can standardize some abbrs words and common review rules and document them in our contributing.md, any suggestion? below are two main things I noticed:
- Make sure all K8s related words start with upper case.
- some abbrs. like
IPsec
Antrea
etc.
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.
Sounds good to me
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.
Thanks for the fix!
Update on this: my OVS patch has been merged upstream and backported to the 2.15 release train (openvswitch/ovs@e59194b). I am tempted to drop this PR, wait until OVS 2.15.4 is released and then update the OVS version in Antrea to 2.15.4. I will make a decision before the Antrea v1.6 release freeze. |
When using IPv6, the IPsec configuration (ipsec.conf) generated by ovs-monitor-ipsec for strongSwan is currently not correct. A patch has been submitted upstream, but until it is accepted and merged, we apply a temporary version of the patch. This was tested for a VXLAN overlay in an IPv6-only cluster. Fixes antrea-io#3151 Signed-off-by: Antonin Bas <abas@vmware.com>
aa018fa
to
62598ee
Compare
No OVS 2.15.4 release yet, so I'm merging this for v1.6 |
/test-all |
/test-e2e |
/test-ipv6-only-e2e |
I forgot that |
When using IPv6, the IPsec configuration (ipsec.conf) generated by
ovs-monitor-ipsec for strongSwan is currently not correct. A patch has
been submitted upstream, but until it is accepted and merged, we apply a
temporary version of the patch.
This was tested for a VXLAN overlay in an IPv6-only cluster.
Fixes #3151
Signed-off-by: Antonin Bas abas@vmware.com