Fix pod annotations propagating to namespace #13165
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
Currently, there's a bug with the jaeger injector where annotation overrides from a pod can propagate to any pod in the same namespace, provided they happen after the admission for the original pod occurs. This fixes that by performing a deep copy of the namespace annotations, instead of editing the one in the local cache (which appears to have been unintentional). Validated with a local deployment and checking that annotations are no longer propagated to unrelated pods. Signed-off-by: Scott Fleener <[email protected]>
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.
Currently, there's a bug with the jaeger injector where annotation overrides from a pod can propagate to any pod in the same namespace, provided they happen after the admission for the original pod occurs.
This fixes that by performing a deep copy of the namespace annotations, instead of editing the one in the local cache (which appears to have been unintentional).
Validated with a local deployment and checking that annotations are no longer propagated to unrelated pods.