As of today, both kubernetes autodiscover provider and add_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):
metricbeat.autodiscover:
- providers: kubernetes
resource: node
...
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 config
cc @vjsamuel @sorantis @odacremolbap @ChrsMark
As of today, both
kubernetesautodiscover provider andadd_kubernetes_metadataprocessor 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