Update k8s autodiscover metadata in nodes earlier#29289
Update k8s autodiscover metadata in nodes earlier#29289ChrsMark merged 10 commits intoelastic:masterfrom
Conversation
Nodes metadata is used by autodiscover to include it in events or to generate autodiscover hints for the pods in the node. This change watches explicitly for changes in nodes to update this metadata instead of waiting for resyncs. Signed-off-by: chrismark <chrismarkou92@gmail.com>
|
Pinging @elastic/integrations (Team:Integrations) |
|
This pull request does not have a backport label. Could you fix it @ChrsMark? 🙏
NOTE: |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
|
/package |
|
This pull request is now in conflicts. Could you fix it? 🙏 |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
|
/package |
Signed-off-by: chrismark <chrismarkou92@gmail.com>
Signed-off-by: chrismark <chrismarkou92@gmail.com>
2bc6a3d to
2798e05
Compare
|
/package |
|
/package |
|
/package |
What does this PR do?
Node metadata is used by autodiscover to include it in events or
to generate autodiscover hints for the pods in the node.
This change watches explicitly for changes in nodes to update these
metadata immediately instead of waiting for full resyncs.
Checklist
CHANGELOG.next.asciidocorCHANGELOG-developer.next.asciidoc.Related issues