-
Notifications
You must be signed in to change notification settings - Fork 3.4k
ipsec: guard vxlan-in-esp policies by routing mode correctly. #35549
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
Merged
pchaigno
merged 1 commit into
cilium:main
from
ldelossa:ldelossa/vxlan-in-esp-policies-fix
Oct 25, 2024
Merged
ipsec: guard vxlan-in-esp policies by routing mode correctly. #35549
pchaigno
merged 1 commit into
cilium:main
from
ldelossa:ldelossa/vxlan-in-esp-policies-fix
Oct 25, 2024
Conversation
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
pchaigno
reviewed
Oct 25, 2024
Doesn't this need backporting to v1.16? |
Use the appropriate configuration option when deciding to install VXLAN-in-ESP related policies and states. Previous to this commit this was decided by checking whether a tunnel device was configured. This is too general. EgressGateway configures a tunnel device depsite the cluster being in native routing mode. It would be an error to install the VXLAN-in-ESP related policies and states in this scenario. Fix this by wiring the RoutingMode configuration into `LocalNodeConfiguration` and referring to this in ipsec.go Currently, this cannot actually case a bug in Cilium. This is because of the subsequent check on `EnableIPSecEncryptedOverlay` configuration flag. This cannot be enabled without tunnel mode being enabled. However, in future commits this restriction will be going away. Signed-off-by: Louis DeLosSantos <louis.delos@isovalent.com>
1677c31
to
4bacb14
Compare
No backport necessary.
No release has occurred since that. |
pchaigno
approved these changes
Oct 25, 2024
/test |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/datapath
Impacts bpf/ or low-level forwarding details, including map management and monitor messages.
area/encryption
Impacts encryption support such as IPSec, WireGuard, or kTLS.
ready-to-merge
This PR has passed all tests and received consensus from code owners to merge.
release-note/misc
This PR makes changes that have no direct user impact.
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.
See commit message for details.