-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add daemonset name in pods controlled by DaemonSets #26808
Add daemonset name in pods controlled by DaemonSets #26808
Conversation
Pinging @elastic/integrations (Team:Integrations) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm. It will need a changelog. Also since merging this will close the respective issue please make sure we follow up properly with a new issue about the workload fields (I left a comment there too).
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
Trends 🧪💚 Flaky test reportTests succeeded. Expand to view the summary
Test stats 🧪
|
* Add daemonset name in pods controller by DaemonSets (cherry picked from commit 4933aef)
* Add daemonset name in pods controller by DaemonSets (cherry picked from commit 4933aef) Co-authored-by: Michael Katsoulis <[email protected]>
What does this PR do?
This PR adds
kubernetes.daemonset.name
in Pods' metadata.Why is it important?
It enriches the documents of pods belonging to
DaemonSets
with the DaemonSet name.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
kubectl apply -f https://k8s.io/examples/controllers/daemonset.yaml
kubernetes.daemonset.name
. As an example see screenshots below.Related issues
Screenshots