Skip to content
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

[DNM] Remove ipsec state disable default crypto 4.17 #2601

Conversation

pperiyasamy
Copy link
Member

for QE testing.

The ovs-monitor-ipsec doesn't set authby, so when it calls ipsec auto --start
the default ones defined at Libreswan's compile time will be used. On restart,
Libreswan will use authby from libreswan.config. If libreswan.config is
incompatible with the Libreswan's compiled-in defaults, then we'll have an
authentication problem. But OTOH, ovs-monitor-ipsec does set ike and esp algorithms,
so those may be incompatible with libreswan.config as well. Hence commenting out the
"include" from libreswan.conf to avoid such conflicts.

Signed-off-by: Periyasamy Palanisamy <[email protected]>
(cherry picked from commit 553516e)
(cherry picked from commit 36e691e)
(cherry picked from commit 2e5c7d3)
The ovn-ipsec-host daemonset is not fast enough to trigger ovs-monitor-ipsec script
to delete ipsec tunnel entries when east-west IPsec is disabled from API. This still
keeps east west traffic with ipsec encrypted when IPsec mode is changed from full to
external mode. Hence this commit cleans up ipsec entries in the ovn-ipsec-host DS
prestop hook before killing ovs-monitor-ipsec script.

Signed-off-by: Periyasamy Palanisamy <[email protected]>
(cherry picked from commit ea18156)
(cherry picked from commit 3892c72)
The previous commit deletes ipsec entries in the preStop of the ovn-ipsec
container just before killing ovs-monitor-ipsec script. We never know
it may cause any other potential issues when cleanup and ovs-monitor-ipsec
running at the same time. hence moving ipsec cleanup logic into the sidecar
container so that it happens only after ovs-monitor-ipsec is killed.

Signed-off-by: Periyasamy Palanisamy <[email protected]>
(cherry picked from commit e58b561)
(cherry picked from commit 72c9115)
@openshift-ci openshift-ci bot requested review from kyrtapz and trozet December 12, 2024 14:40
Copy link
Contributor

openshift-ci bot commented Dec 12, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: pperiyasamy
Once this PR has been reviewed and has the lgtm label, please assign trozet for approval. For more information see the Code Review Process.

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Copy link
Contributor

openshift-ci bot commented Dec 12, 2024

@pperiyasamy: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-gcp-ovn-techpreview a6724b9 link true /test e2e-gcp-ovn-techpreview
ci/prow/4.17-upgrade-from-stable-4.16-e2e-aws-ovn-upgrade a6724b9 link false /test 4.17-upgrade-from-stable-4.16-e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-single-node a6724b9 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-hypershift-ovn-kubevirt a6724b9 link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/security a6724b9 link false /test security
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 a6724b9 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-aws-ovn-serial a6724b9 link false /test e2e-aws-ovn-serial
ci/prow/e2e-gcp-ovn-upgrade a6724b9 link true /test e2e-gcp-ovn-upgrade
ci/prow/4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade a6724b9 link false /test 4.17-upgrade-from-stable-4.16-e2e-azure-ovn-upgrade

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.

@openshift-merge-robot openshift-merge-robot added needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. and removed needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Dec 13, 2024
@pperiyasamy pperiyasamy closed this Jan 7, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants