-
Notifications
You must be signed in to change notification settings - Fork 245
[release-4.17] OCPBUGS-57285: Implement IPsec NAT-Traversal encapsulation option #2726
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
base: release-4.17
Are you sure you want to change the base?
[release-4.17] OCPBUGS-57285: Implement IPsec NAT-Traversal encapsulation option #2726
Conversation
@pperiyasamy: This pull request references Jira Issue OCPBUGS-57285, which is valid. 7 validation(s) were run on this bug
Requesting review from QA contact: The bug has been updated to refer to the pull request using the external bug tracker. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: pperiyasamy The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The following commands are run for API bump: go get github.com/openshift/[email protected] go mod vendor make update-codegen Signed-off-by: Periyasamy Palanisamy <[email protected]>
This commit consumes configuration parameters for the IPsec `Full` mode, it currently has encapsulation option to configure OVN so that inter pod traffic across node are encapsulated to handle NAT traversal. So it implements the following. 1. When the encapsulation option is set with "Always", then enforce NAT-T encapsulation on the OVN. 2. When the encapsulation option is set with "Auto" or the config option for full mode is never set, then it continues to render the "auto" option for NAT-T encapsulation. 3. On the IBMCloud platform, NAT-T encapsulation is always enforced. Signed-off-by: Periyasamy Palanisamy <[email protected]> (cherry picked from commit 50899e2) (cherry picked from commit d660f37)
e280654
to
5997958
Compare
passed: (5m56s) 2025-06-18T06:15:10 "[sig-networking] SDN IPSEC EW Author:huirwang-High-80099-Verify encapsulation=Always/Auto works. [Disruptive] [Serial]" /label cherry-pick-approved |
/assign @jcaamano |
/retest-required |
/retest |
/test ? |
@pperiyasamy: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
@pperiyasamy: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
Manual cherry-pick of 4.18 commit d660f37.
Bump openshift/api version to consume IPsec encapsulation API.