Andrew Gizas

Hello @eedugon , I started having a look at this. For my testing I have something as simple as: Redis manifest with a volume with type `EmptyDir` ```yaml apiVersion: v1...

We will keep this issue open because although we have merged an update for the Volumes dashboard still the pod metadata enrichment is not possible without an enhancement (see [comment](https://github.com/elastic/beats/issues/39524#issuecomment-2191405410))...

I have updated description and autodiscovery library to make use of use_kubeadm variable See comment https://github.com/elastic/elastic-agent-autodiscover/pull/98#discussion_r1684158494

@MichaelKatsoulis I added again the use_kubeadm option [here](https://github.com/elastic/beats/pull/40086/files#diff-c00c194167e320d0bb1f2291fe85b8eb12853ffa5074e633e06b2d607b625845R28) Reason is that kubelet metricsets, proxy and scheduler make use of AddClusterECSMeta (like [here](https://github.com/elastic/beats/blob/main/metricbeat/module/kubernetes/apiserver/metricset.go#L48)) which is using finally the [kubernetes config](https://github.com/elastic/beats/blob/main/metricbeat/module/kubernetes/util/kubernetes.go#L42) struct....

@elastic/beats-tech-leads can I have a review here? The pr looks good and tested

@cmacknz I was testing the above [enhancement](https://github.com/elastic/integrations/pull/11187) through the integration, but I could not observe any improvements in case of applying the use_kubeadm variable through the integration.  I think...

Oh I see that we refer https://github.com/elastic/elastic-agent-autodiscover/blob/main/kubernetes/metadata/config.go#L63-L64 and this uses use_kubeadm: true!!!! So question would be how to initialise the kubeadm in agent provider: I see only this option https://www.elastic.co/guide/en/fleet/current/advanced-kubernetes-managed-by-fleet.html#_step_2_create_a_new_configmap...

@swiatekm any progress on this? Do you want to document the steps in case of EA? Even in case of overrides is it not clear to me where/how I apply...

@jade-guiton-dd I will try to fix the linting errors and will open it as ready for review. thanks for the ping

@jade-guiton-dd did another round for the lint/test errors. Lets see > I was thinking it's probably a good idea to wait until pipeline instrumentation (https://github.com/open-telemetry/opentelemetry-collector/issues/12676) has implemented the "outcome =...