# Helm Elastic APM

**URL:** <https://discuss.elastic.co/t/helm-elastic-apm/152118>\
**Category:** APM\
**Created:** [October 11, 2018, 7:29pm UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118 "2018-10-11T19:29:57Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![Clay\_Gorman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clay_gorman/32/19512_2.png) [@Clay\_Gorman](https://discuss.elastic.co/u/Clay_Gorman)\
**Post date:** [October 11, 2018, 7:29pm UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118/1 "2018-10-11T19:29:57Z")

</div>

Hey there,

I am attempting to use [https://github.com/helm/charts/tree/master/stable/apm-server](https://github.com/helm/charts/tree/master/stable/apm-server) and notice its a daemonset that doesnt appear to expose the 8200 port to the host.

I was wondering if anyone has advice on how I connect my pod to the local apm running on the same host with this chart?

Thanks in advance

---

<div class="post-metadata">

**Author:** ![esseti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/esseti/32/8383_2.png) [@esseti](https://discuss.elastic.co/u/esseti)\
**Post date:** [October 15, 2018, 11:57am UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118/2 "2018-10-15T11:57:24Z")

</div>

same problem here, I can't figure it out.. any news from your side?

---

<div class="post-metadata">

**Author:** ![Michelle\_Sausa](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michelle_sausa/32/48873_2.png) [@Michelle\_Sausa](https://discuss.elastic.co/u/Michelle_Sausa)\
**Post date:** [October 15, 2018, 7:54pm UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118/3 "2018-10-15T19:54:03Z")

</div>

We are aware of that chart, but it was not built by us nor is it currently maintained by us. We are, however, actively looking into releasing and maintaining our own Helm charts.

---

<div class="post-metadata">

**Author:** ![esseti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/esseti/32/8383_2.png) [@esseti](https://discuss.elastic.co/u/esseti)\
**Post date:** [October 16, 2018, 7:53am UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118/4 "2018-10-16T07:53:47Z")

</div>

Since that is stable, and deploys a DaeomnSet, why don't you just update that one? same for the filebeat: there's an helm that does (afaik) the same as the script you have in the official tutorial, why not using the helm?

---

<div class="post-metadata">

**Author:** ![Clay\_Gorman](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/clay_gorman/32/19512_2.png) [@Clay\_Gorman](https://discuss.elastic.co/u/Clay_Gorman)\
**Post date:** [October 26, 2018, 4:25pm UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118/5 "2018-10-26T16:25:33Z")

</div>

I ended up adding host\_port in combination with [https://bravopooper.wordpress.com/2017/07/17/communicating-with-local-daemon-set-pods-in-kubernetes/](https://bravopooper.wordpress.com/2017/07/17/communicating-with-local-daemon-set-pods-in-kubernetes/)

I ended up getting it working but I am not that happy with it.

---

<div class="post-metadata">

**Author:** ![esseti](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/esseti/32/8383_2.png) [@esseti](https://discuss.elastic.co/u/esseti)\
**Post date:** [October 29, 2018, 9:43am UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118/6 "2018-10-29T09:43:17Z")

</div>

Thanks.. anyway, for my usecase this seems to be an overkill for the helm. I just need 1 apm or maybe 2 to handle the only one service that use apm. having 1 per node is probably too much.

---

<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:** [November 19, 2018, 5:43am UTC](https://discuss.elastic.co/t/helm-elastic-apm/152118/7 "2018-11-19T05:43:20Z")

</div>

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