# Unexpected pod restart after operator upgrade to 2.3

**URL:** <https://discuss.elastic.co/t/unexpected-pod-restart-after-operator-upgrade-to-2-3/314202>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [September 12, 2022, 2:51pm UTC](https://discuss.elastic.co/t/unexpected-pod-restart-after-operator-upgrade-to-2-3/314202 "2022-09-12T14:51:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![pup\_seba](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pup_seba/32/42988_2.png) [@pup\_seba](https://discuss.elastic.co/u/pup_seba)\
**Post date:** [September 12, 2022, 2:51pm UTC](https://discuss.elastic.co/t/unexpected-pod-restart-after-operator-upgrade-to-2-3/314202/1 "2022-09-12T14:51:17Z")

</div>

Hi,

According to [documentation](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-upgrading-eck.html#k8s-beta-to-ga-rolling-restart), updating our current ECK operator from version 2.2 to 2.3 should have gone without operated pods being restarted. From our operated elasticsearch clusters running in this k8s cluster, 1 whole ES cluster of them was (rollout) restarted.

This was unexpected and undesired since we did not announce this would happen. Is there any way to understand/know what happened? I am not seeing too much relevant info in logs, but maybe I am not looking for the right things.

Our k8s version is v1.21.11 and the elasticsearch operated cluster that was unexpectedly restarted is in version 7.9.0.

Thank you!

---

<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:** [October 10, 2022, 2:52pm UTC](https://discuss.elastic.co/t/unexpected-pod-restart-after-operator-upgrade-to-2-3/314202/2 "2022-10-10T14:52:06Z")

</div>

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