Cherry-pick #22438 to 7.x: Fix duplicated events in kubernetes autodiscover for pods with init or ephemeral containers #22492
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.
Cherry-pick of PR #22438 to 7.x branch. Original message:
What does this PR do?
Stop sending duplicated events for pods with init or ephemeral containers.
Why is it important?
Actually not so important because in principle duplicated events should generate the same configuration, and configurations are de-duplicated, but just in case these duplicated events have unexpected effects.
Also, an additional test is added to cover init containers.
Checklist
I have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues