egressgw: drop traffic if no gateway is found#24835
Conversation
|
Hi @jibi 👋, it's me again for the second part of the work to actually drop traffic that doesn't match any gateway :D (for reference/other people tuning in you will be able to find more context here #24449 (comment)). |
786a3ff to
1c8fb00
Compare
|
/test Job 'Cilium-PR-K8s-1.16-kernel-4.19' failed: Click to show.Test NameFailure OutputJenkins URL: https://jenkins.cilium.io/job/Cilium-PR-K8s-1.16-kernel-4.19/898/ If it is a flake and a GitHub issue doesn't already exist to track it, comment |
jibi
left a comment
There was a problem hiding this comment.
Looks good! Just a couple of small comments
1c8fb00 to
acb187d
Compare
c4b6f89 to
2e9ad4a
Compare
|
🤔 can you try rebasing on top of master please? |
2e9ad4a to
bd991e1
Compare
jibi
left a comment
There was a problem hiding this comment.
We should also update docs (both the egressgw one as well as the upgrade guide) to point out that from now on we'll start dropping packets in case no gateway is found, but this can be done in a follow up PR since CI is already green
Oops, you caught me not reading other reviews 😅. I'll keep my review as "requesting changes" because otherwise the merge button is green. Thanks! |
fair enough 👍 @MrFreezeex could you please add a note about the new behaviour:
|
bd991e1 to
2b80b7e
Compare
zacharysarah
left a comment
There was a problem hiding this comment.
@MrFreezeex Thanks for the update. Minor edits, otherwise LGTM
Switch to dropping traffic when no gateway are found for an egressgw instead of the previous behavior consisting of allowing traffic without the snat. It also adds a new drop reason (DROP_NO_EGRESS_GATEWAY) for this specific case. Signed-off-by: Arthur Outhenin-Chalandre <arthur@cri.epita.fr>
2b80b7e to
064cf32
Compare
|
/test |
|
Conformance job failure (https://github.com/cilium/cilium/actions/runs/4740958766/jobs/8417418731?pr=24835) seems related to #24622 |
|
All good here with reviews and CI, merging this 🚢 thanks again for the great work! |
Switch to dropping traffic when no gateway are found for an egressgw instead of the previous behavior consisting of allowing traffic without the snat.
Please ensure your pull request adheres to the following guidelines:
description and a
Fixes: #XXXline if the commit addresses a particularGitHub issue.
Fixes: <commit-id>tag, thenplease add the commit author[s] as reviewer[s] to this issue.
Fixes: #issue-number