# Adding ECK Operator Liveness Probe

**URL:** <https://discuss.elastic.co/t/adding-eck-operator-liveness-probe/288235>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [November 2, 2021, 3:09pm UTC](https://discuss.elastic.co/t/adding-eck-operator-liveness-probe/288235 "2021-11-02T15:09:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MattThomson](https://avatars.discourse-cdn.com/v4/letter/m/9f8e36/32.png) [@MattThomson](https://discuss.elastic.co/u/MattThomson)\
**Post date:** [November 2, 2021, 3:09pm UTC](https://discuss.elastic.co/t/adding-eck-operator-liveness-probe/288235/1 "2021-11-02T15:09:01Z")

</div>

I've attempted to add liveness and readiness probes to the ECK operator itself (not the Elasticsearch,kibana,etc pods), but I can't find any documentation on exposed endpoints for health checks. So far I'm doing this with a kustomization patch:

```auto
- op: add
  path: /spec/template/spec/containers/0/livenessProbe
  value:
    initialDelaySeconds: 10
    failureThreshold: 6
    tcpSocket:
      port: 9443

```

However, while this seems to work, it results in the pod logs reporting

```auto
2021/11/02 14:39:01 http: TLS handshake error from 10.240.0.14:50396: EOF

```

Every time each probe runs (default 10 second intervals). Is there another way to set up liveness/readiness probes for ECK, or are they not recommended for ECK?  
e.g. an endpoint which can be used with httpGet instead of tcpSocket? I've tried the same port with "/", but this returns 404.

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [November 9, 2021, 9:35am UTC](https://discuss.elastic.co/t/adding-eck-operator-liveness-probe/288235/2 "2021-11-09T09:35:44Z")

</div>

Hi,

It's a good question. I'll open an issue in the ECK repo to discuss it (I'll update this thread with a link to the issue)  
I think there are a few points to discuss, using the webhook server might not be good idea as I'm not sure it reflects the status of the operator.

Thanks

---

<div class="post-metadata">

**Author:** ![michael.morello](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/michael.morello/32/47448_2.png) [@michael.morello](https://discuss.elastic.co/u/michael.morello)\
**Post date:** [November 9, 2021, 12:44pm UTC](https://discuss.elastic.co/t/adding-eck-operator-liveness-probe/288235/3 "2021-11-09T12:44:52Z")

</div>

I created [this issue](https://github.com/elastic/cloud-on-k8s/issues/5032) to discuss it further.

---

<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:** [December 7, 2021, 12:45pm UTC](https://discuss.elastic.co/t/adding-eck-operator-liveness-probe/288235/4 "2021-12-07T12:45:40Z")

</div>

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