Skip processing unrelated namespace peers for Network Policy #4776
+32
−5
Conversation
This file contains 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
tssurya
added
kind/bug
When network policy object contains peers from namespace which is not on subject's user defined network, then it doesn't make sense to add that peer namespace into OVN's network policy ACL, because those namespaces are isolated already. Hence this commit avoids processing such peers in network policy namespace peer handler. Signed-off-by: Periyasamy Palanisamy <pepalani@redhat.com>
pperiyasamy
force-pushed
the
udn-netpol-skip-unrelated-ns
branch
from
b918dc5
to
c68b191
Compare
github-actions
bot
added
the
area/unit-testing
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.
When network policy object contains peers from namespace which is not on subject's user defined network, then it doesn't make sense to add that peer namespace into OVN's network policy ACL, because those namespaces are isolated already. Hence this PR avoids processing such peers in network policy namespace peer handler.