When `add_kubernetes_metadata` is used with {beatname_uc}, it uses the
`container` indexer and the `logs_path`. So events whose path in `log.file.path`
contains a reference to a container ID are enriched with metadata of the pod of
this container.

This behaviour can be disabled by disabling default indexers and matchers in the
configuration:
[source,yaml]
-------------------------------------------------------------------------------
processors:
  - add_kubernetes_metadata:
      default_indexers.enabled: false
      default_matchers.enabled: false
-------------------------------------------------------------------------------
