Cherry-pick #25117 to 7.x: Watch kubernetes namespaces for autodiscover metadata for pods#25157
Merged
jsoriano merged 1 commit intoelastic:7.xfrom Apr 20, 2021
Merged
Conversation
Contributor
|
Pinging @elastic/integrations (Team:Integrations) |
Contributor
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
Member
Author
|
/test |
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
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 #25117 to 7.x branch. Original message:
What does this PR do?
Namespaces metadata is used by autodiscover to include it in events or
to generate autodiscover hints for the pods in the namespace.
This change watches explicitly for changes in namespaces to update this
metadata immediately instead of waiting for full resyncs.
Why is it important?
Changes are discovered immediately instead of needing to wait for full resyncs.
This removes one reason to need full resyncs, what can help in the future to reduce their frequency or completely remove them.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.