# Monitor kubernetes ingress resources with heartbeat

**URL:** <https://discuss.elastic.co/t/monitor-kubernetes-ingress-resources-with-heartbeat/216537>\
**Category:** Beats\
**Tags:** heartbeat\
**Created:** [January 25, 2020, 6:15pm UTC](https://discuss.elastic.co/t/monitor-kubernetes-ingress-resources-with-heartbeat/216537 "2020-01-25T18:15:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![laurentiusoica](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/laurentiusoica/32/27342_2.png) [@laurentiusoica](https://discuss.elastic.co/u/laurentiusoica)\
**Post date:** [January 25, 2020, 6:15pm UTC](https://discuss.elastic.co/t/monitor-kubernetes-ingress-resources-with-heartbeat/216537/1 "2020-01-25T18:15:22Z")

</div>

Is there any way to configure heartbeat to automatically detect the ingress resources in a cluster and run a simple health-check against each of them ?

Also, the heartbeat chart deploys a daemonset; is this really needed ? I get a lot of redundant data. And it scales with the cluster. Wouldn't a deployment with 2 replicas be more appropriate ?

---

<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:** [January 27, 2020, 3:02pm UTC](https://discuss.elastic.co/t/monitor-kubernetes-ingress-resources-with-heartbeat/216537/2 "2020-01-27T15:02:45Z")

</div>

What do you mean about ingress resources? Do you mean the endpoints heartbeat checks? I assume you've read our [autodiscover docs](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-autodiscover.html) already?

You're 100% right about the daemonset. We are targeting the new `scope` option for autodiscover in 7.6 (see the docs [here](https://www.elastic.co/guide/en/beats/heartbeat/7.6/configuration-autodiscover.html)), which let you look at the whole k8s cluster instead of just a single pod.

Also, which chart are you using? Is it [https://github.com/helm/charts/tree/master/stable/heartbeat](https://github.com/helm/charts/tree/master/stable/heartbeat) or [https://helm.elastic.co](https://helm.elastic.co)

---

<div class="post-metadata">

**Author:** ![laurentiusoica](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/laurentiusoica/32/27342_2.png) [@laurentiusoica](https://discuss.elastic.co/u/laurentiusoica)\
**Post date:** [January 27, 2020, 3:39pm UTC](https://discuss.elastic.co/t/monitor-kubernetes-ingress-resources-with-heartbeat/216537/3 "2020-01-27T15:39:55Z")

</div>

> What do you mean about ingress resources? Do you mean the endpoints heartbeat checks? I assume you've read our [autodiscover docs](https://www.elastic.co/guide/en/beats/heartbeat/current/configuration-autodiscover.html) already?

I mean k8s resources of ingress type, as per [Ingress | Kubernetes](https://kubernetes.io/docs/concepts/services-networking/ingress/#the-ingress-resource)  
I checked the autodiscoder docs, I hope I did not miss anything. And then I checked the codebase and my understanding is it's only watching pods, services and nodes [https://github.com/elastic/beats/blob/master/libbeat/autodiscover/providers/kubernetes/kubernetes.go#L104](https://github.com/elastic/beats/blob/master/libbeat/autodiscover/providers/kubernetes/kubernetes.go#L104)

> Also, which chart are you using? Is it [https://github.com/helm/charts/tree/master/stable/heartbeat](https://github.com/helm/charts/tree/master/stable/heartbeat) or [https://helm.elastic.co](https://helm.elastic.co/)

This one. [https://github.com/helm/charts/tree/master/stable/heartbeat](https://github.com/helm/charts/tree/master/stable/heartbeat) But I ended up doing my own manifests in order to move from DaemonSet to Deployment.

---

<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:** [February 24, 2020, 3:39pm UTC](https://discuss.elastic.co/t/monitor-kubernetes-ingress-resources-with-heartbeat/216537/4 "2020-02-24T15:39:56Z")

</div>

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