policy/correlation: Fix PolicyMatchL3Proto case
#35680
Merged
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
This commit fixes a bug in the policy correlation code where policies that only match a L3 identity and a L4 protocol (without a port) were previously not correlated. This commit was manually tested in addition to the added unit test. Signed-off-by: Sebastian Wicki <sebastian@isovalent.com>
This was referenced Oct 31, 2024
|
/test |
doniacld
approved these changes
Nov 4, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This commit fixes a bug in the policy correlation code where policies that only match a L3 identity and a L4 protocol (without a port) were previously not correlated.
This commit was manually tested in addition to the added unit test.
Ref: #35416 (fixes this on main, but v1.16 needs a different fix)