# Heartbeat on Kubernetes cluster

**URL:** <https://discuss.elastic.co/t/heartbeat-on-kubernetes-cluster/337140>\
**Category:** Elasticsearch\
**Created:** [June 29, 2023, 4:17am UTC](https://discuss.elastic.co/t/heartbeat-on-kubernetes-cluster/337140 "2023-06-29T04:17:24Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jam\_mahmoudi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jam_mahmoudi/32/56194_2.png) [@jam\_mahmoudi](https://discuss.elastic.co/u/jam_mahmoudi)\
**Post date:** [June 29, 2023, 4:17am UTC](https://discuss.elastic.co/t/heartbeat-on-kubernetes-cluster/337140/1 "2023-06-29T04:17:24Z")

</div>

Hi guys  
I have a question  
How should I define a heartbeat to monitor all pods in a Kubernetes cluster?  
Do I only need to install and configure Heartbeat on the worker nodes, or do I need to install and configure it on each pod in the cluster?

I appreciate any advice

---

<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:** [July 27, 2023, 4:17am UTC](https://discuss.elastic.co/t/heartbeat-on-kubernetes-cluster/337140/2 "2023-07-27T04:17:43Z")

</div>

Closed on July 27, 2023, 4:17am UTC

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