fix(core) : owner information in logs #1753
Merged
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
Prateeknandle
requested review from
daemon1024,
DelusionalOptimist and
PrimalPimmy
Signed-off-by: Prateek Nandle <[email protected]>
DelusionalOptimist
approved these changes
May 15, 2024
daemon1024
approved these changes
May 15, 2024
DelusionalOptimist
pushed a commit
to DelusionalOptimist/KubeArmor
that referenced
this pull request
May 23, 2024
fix(core) : owner information in logs
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.
Purpose of PR?:
When the pod is not available, we should not update the
dm.OwnerInfomap.The variables which stores owner info were storing info from previous pod, when current pod was not available. Then the
dm.OwnerInfomap was updated with wrong owner info from previous execution.Fixes #
Does this PR introduce a breaking change?
no
If the changes in this PR are manually verified, list down the scenarios covered::
on gcp cluster
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>