endpoint: Fix syncing of invalid policymap entries on upgrade #35834
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
Mark policymap entries not valid explicitly when policy map entry is not valid so that map sync will update the entry, instead just ignoring the key, as in that case the key would remain in the map if it would have needed to be removed instead. Fixes: cilium#35534 Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
|
/test |
nathanjsweet
approved these changes
Nov 11, 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.
Mark policymap entries not valid explicitly when policy map entry is not valid so that map sync will update the entry, instead just ignoring the key, as in that case the key would remain in the map if it would have needed to be removed instead.
Fixes: #35534