# ECK cluster dies after 3-4 months and tries to automatically create new cluster

**URL:** <https://discuss.elastic.co/t/eck-cluster-dies-after-3-4-months-and-tries-to-automatically-create-new-cluster/242950>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [July 28, 2020, 5:23pm UTC](https://discuss.elastic.co/t/eck-cluster-dies-after-3-4-months-and-tries-to-automatically-create-new-cluster/242950 "2020-07-28T17:23:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jack\_Watroba](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_watroba/32/45613_2.png) [@Jack\_Watroba](https://discuss.elastic.co/u/Jack_Watroba)\
**Post date:** [July 28, 2020, 5:23pm UTC](https://discuss.elastic.co/t/eck-cluster-dies-after-3-4-months-and-tries-to-automatically-create-new-cluster/242950/1 "2020-07-28T17:23:06Z")

</div>

We've been using ECK late last year, started with the beta operator, moved to 1.0, and now we're on 1.1.2, each time doing a complete uninstall/reinstall of the operator, and have updated the cluster to various versions in between, currently on 7.8. About 3-4 times over the past year, usually about 3-4 months into the cluster working fine, it will randomly die in the middle of night, and it acts as though it's spinning up a new cluster, it releases it's PVC's and recreates all of it's secrets and tries to init a new cluster, which always fails, and stays in a failed state until I can delete it and re-recreate it. Has anyone else experienced this behavior? I would really like to understand why this is happening as it makes for some unpleasant late night calls.

Here are the logs from the operator when this begins to happen:

> **[ECK death log - Pastebin.com](https://pastebin.com/pWYaCrmg)**
>
> Pastebin.com is the number one paste tool since 2002. Pastebin is a website where you can store text online for a set period of time.

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [July 28, 2020, 5:39pm UTC](https://discuss.elastic.co/t/eck-cluster-dies-after-3-4-months-and-tries-to-automatically-create-new-cluster/242950/2 "2020-07-28T17:39:21Z")

</div>

Have you by any chance copied any of the ECK created secrets to another namespace including the owner references? [https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-common-problems.html#k8s-common-problems-owner-refs](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-common-problems.html#k8s-common-problems-owner-refs)

---

<div class="post-metadata">

**Author:** ![Jack\_Watroba](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jack_watroba/32/45613_2.png) [@Jack\_Watroba](https://discuss.elastic.co/u/Jack_Watroba)\
**Post date:** [July 28, 2020, 6:17pm UTC](https://discuss.elastic.co/t/eck-cluster-dies-after-3-4-months-and-tries-to-automatically-create-new-cluster/242950/3 "2020-07-28T18:17:51Z")

</div>

Wow, that's a fun bug. Yep, that's probably exactly what's been happening to us. So glad to finally have an answer to this crazy behavior. Thanks!

---

<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 4, 2022, 8:08am UTC](https://discuss.elastic.co/t/eck-cluster-dies-after-3-4-months-and-tries-to-automatically-create-new-cluster/242950/4 "2022-11-04T08:08:02Z")

</div>


