[libbeat/processors/add_docker_metadata] Adding support for custom cgroup prefixes#16926
[libbeat/processors/add_docker_metadata] Adding support for custom cgroup prefixes#16926danmx wants to merge 1 commit intoelastic:masterfrom danmx:master
Conversation
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
1 similar comment
|
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
|
💚 CLA has been signed |
|
Pinging @elastic/integrations-platforms (Team:Platforms) |
|
jenkins, test this please |
exekias
left a comment
There was a problem hiding this comment.
Thank you so much for contributing 🎉 ! I'm wondering, why do you want to add docker metadata when running on Kubernetes? I would expect users to care more about kubernetes metadata in this case.
This will need a new changelog entry under CHANGELOG.next.asciidoc
|
@exekias |
|
@exekias I could use this PR to refactor |
Signed-off-by: danmx <daniel@iziourov.info>
💔 Tests FailedExpand to view the summary
Build stats
Test stats 🧪
Test errorsExpand to view the tests failures
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
| // of them are associated with Docker. Docker uses /docker/<CID> and | ||
| // Kubernetes, with Docker as a container runtime, uses | ||
| // /kubepods/<class>/<podID>/<cID> when naming cgroups. | ||
| // We use this to determine the container ID. |
There was a problem hiding this comment.
I think this will not work in cases of having more than one containers for a Pod. For instance, pause containers will be found under /kubepods/<class>/<podID> along with the main containers, and the structure would look like this:
/kubepods/besteffort/pod-abcdef/<cID1>/kubepods/besteffort/pod-abcdef/<cID2>
In this case how we identify which cID we are interested in?
❕ Build Aborted
Expand to view the summary
Build stats
Steps errorsExpand to view the steps failures
Log outputExpand to view the last 100 lines of log output
|
|
Hi! We're labeling this issue as |
|
Hi! |
What does this PR do?
Why is it important?
This change will allow detection of containers orchestrated by Kubernetes
Checklist
Author's Checklist
How to test this PR locally
Related issues
Use cases
Detecting containers running in Kubernetes Cluster
Screenshots
Logs