-
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
Make kubernetes autodiscover and metadata work for other resources #14044
Labels
autodiscovery
containers
Related to containers use case
enhancement
libbeat
Team:Integrations
Label for the Integrations team
Comments
exekias
added
enhancement
libbeat
containers
Related to containers use case
Team:Integrations
Label for the Integrations team
autodiscovery
labels
Oct 14, 2019
One of the things that we could base on this: #13873 |
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
autodiscovery
containers
Related to containers use case
enhancement
libbeat
Team:Integrations
Label for the Integrations team
As of today, both
kubernetes
autodiscover provider andadd_kubernetes_metadata
processor only work with Pods. We want to extend their support so we can do both autodiscover and enrichment based on other kinds of resources (for instance, nodes, services, namespaces...).A configuration like this could be a good fit (up to discussion):
This would make autodiscover launch configurations based on cluster nodes.
About
add_kubernetes_metadata
, we need to figure out what's the best approach for the configcc @vjsamuel @sorantis @odacremolbap @ChrsMark
The text was updated successfully, but these errors were encountered: