# Add\_kubernetes\_metadata does not append kubernetes metadata

**URL:** <https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [February 5, 2019, 5:44pm UTC](https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170 "2019-02-05T17:44:24Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![drinnird](https://avatars.discourse-cdn.com/v4/letter/d/e47774/32.png) [@drinnird](https://discuss.elastic.co/u/drinnird)\
**Post date:** [February 5, 2019, 5:44pm UTC](https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170/1 "2019-02-05T17:44:24Z")

</div>

Hi,  
We are setting up metricbeat + heartbeat + APM on our kubernetes cluster.

I am deploying heartbeat through helm chart here:

> **[helm/charts](https://github.com/helm/charts/tree/master/stable/heartbeat)**
>
> Curated applications for Kubernetes. Contribute to helm/charts development by creating an account on GitHub.

I am deploying with this command:  
`helm install --name heartbeat -f heartbeatVALUES.yaml stable/heartbeat`

for the heartbeatVALUES.yaml I'm providing this:

> <https://gist.github.com/digressionary/31a280a6696ef107339bb235489c8e51>

However, no kubernetes metadata is added.

I have used the same snippet in my metricsbeat values.yaml, and it is successfully appending the kubernetes metadata. The documentation for add\_kubernetes\_metadata is a little sparse, I can't tell what I'm missing?

Here is my entire setup information,versions,etc:

Kubernetes: docker-for-desktop, v 1.13.0 / docker engine v 18.09.1  
ES: v 5.6  
Heartbeat: 6.6.0

Completely fresh install of all parts.

Possibly the docker-for-desktop is the problem?

---

<div class="post-metadata">

**Author:** ![Andrew\_Cholakian1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrew_cholakian1/32/3612_2.png) [@Andrew\_Cholakian1](https://discuss.elastic.co/u/Andrew_Cholakian1)\
**Post date:** [February 7, 2019, 7:02pm UTC](https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170/2 "2019-02-07T19:02:56Z")

</div>

I realize this is confusing, but the `add_kubernetes_metadata` processor adds metadata about the pod that heartbeat is running on. Not very useful for your scenario.

Starting in heartbeat 6.7 , when using the heartbeat autodiscovery provider k8s metadata will be added automatically.

Till then, you may want to use a similar approach to [Autodiscover and metadata](https://discuss.elastic.co/t/autodiscover-and-metadata/162980/2?u=andrew_cholakian1)

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [March 7, 2019, 7:03pm UTC](https://discuss.elastic.co/t/add-kubernetes-metadata-does-not-append-kubernetes-metadata/167170/3 "2019-03-07T19:03:01Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.