Kubernetes Autodiscovery

[xyz7]

Hi @jsoriano,

Below topic suggests add_kubernetes_metadata is enabled by default if using hints-based autodiscover as mentioned in below reference configuration.

Is add_kubernetes_metadata in filebeat enabled by default?

Just a general question I guess since the documentation wasn't very clear to me. When running Filebeat on Kubernetes as instructed here, https://www.elastic.co/guide/en/beats/filebeat/master/running-on-kubernetes.html Is the add_kubernetes_metadata processor supposed to be enabled by default? Or do I need to configure to enable? I'm using v7.6.

My filebeat config autodiscover part is like this:

    filebeat.autodiscover:
      providers:
        - type: kubernetes
          hints.enabled: true
          include_annotations: ["artifact.spinnaker.io/name","ad.datadoghq.com/tags"]
          templates:
            - condition:
                equals:
                  kubernetes.namespace: myapp

where I have hints.enabled: true, skipped hints.default_config and have templates.

I'm using v7.9.0

Will add_kubernetes_metadata by default enabled in the above configuration as I have skipped hints.default_config and used templates ?

[jsoriano (Jaime Soriano)]

Hey @xyz7, welcome to discuss

@xyz7

Below topic suggests add_kubernetes_metadata is enabled by default if using hints-based autodiscover as mentioned in below reference configuration.

It is not exactly that add_kubernetes_metadata is enabled when using hints-based autodiscover. When using hints-based autodiscover, Beats will include in events the same metadata that would be included by this processor, but only for events of configurations generated from hints.

Functionally this is indeed similar to using add_kubernetes_metadata, but enrichment done by hints-based autodiscover is generally more optimal in resources.

@xyz7

Will add_kubernetes_metadata by default enabled in the above configuration as I have skipped hints.default_config and used templates ?

It won't be enabled. Enrichment will only be done for configurations generated from hints, but won't happen for the configurations generated from templates.