k8s/watchers: fix missing missing CNP/CCNP updates#12143
Merged
Conversation
Since we were only comparing the spec of a CNP / CCNP, whenever the cilium-agent received a CNP or CCNP containing a 'specs', any following updates to that policy wouldn't be enforced in Cilium since the network policy would be considered equal as the one already being enforced. As Cilium is already comparing the network policies, before processing any policy update, we can remove this Spec.Equals. Fixes: 2d34336 ("use deepequal generated code") Signed-off-by: André Martins <andre@cilium.io>
|
Please set the appropriate release note label. |
3 similar comments
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
|
Please set the appropriate release note label. |
Member
Author
|
test-me-please |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
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.
Since we were only comparing the spec of a CNP / CCNP, whenever the
cilium-agent received a CNP or CCNP containing a 'specs', any following
updates to that policy wouldn't be enforced in Cilium since the network
policy would be considered equal as the one already being enforced.
As Cilium is already comparing the network policies, before processing
any policy update, we can remove this Spec.Equals.
Fixes: 2d34336 ("use deepequal generated code")
Signed-off-by: André Martins andre@cilium.io