# Operator Upgrade causes nodes to be restarted

**URL:** <https://discuss.elastic.co/t/operator-upgrade-causes-nodes-to-be-restarted/219640>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [February 17, 2020, 2:30pm UTC](https://discuss.elastic.co/t/operator-upgrade-causes-nodes-to-be-restarted/219640 "2020-02-17T14:30:03Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![acondrat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/acondrat/32/62829_2.png) [@acondrat](https://discuss.elastic.co/u/acondrat)\
**Post date:** [February 17, 2020, 2:30pm UTC](https://discuss.elastic.co/t/operator-upgrade-causes-nodes-to-be-restarted/219640/1 "2020-02-17T14:30:03Z")

</div>

Hello,

I noticed that upgrading the operator causes all the nodes in the cluster to be restarted. Perhaps it is because it changes the `common.k8s.elastic.co/controller-version` annotation on the Elasticsearch object.

This might be a source of trouble (downtime, performance degradation, etc). Is this some expected behavior and can it be avoided?

Thanks!

---

<div class="post-metadata">

**Author:** ![sebgl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebgl/32/48702_2.png) [@sebgl](https://discuss.elastic.co/u/sebgl)\
**Post date:** [February 17, 2020, 2:47pm UTC](https://discuss.elastic.co/t/operator-upgrade-causes-nodes-to-be-restarted/219640/2 "2020-02-17T14:47:36Z")

</div>

Hey @acondrat, this is explicitly documented there: [https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-upgrading-eck.html#k8s-ga-upgrade](https://www.elastic.co/guide/en/cloud-on-k8s/current/k8s-upgrading-eck.html#k8s-ga-upgrade)

We aim to avoid it in the future as much as we can, but any change in ECK impacting the Pod specs will trigger a rolling upgrade, by design.

Note you can set the following annotation on any existing Elasticsearch resource if you don't want ECK to reconcile them:

```auto
common.k8s.elastic.co/pause: true

```

---

<div class="post-metadata">

**Author:** ![acondrat](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/acondrat/32/62829_2.png) [@acondrat](https://discuss.elastic.co/u/acondrat)\
**Post date:** [February 17, 2020, 6:16pm UTC](https://discuss.elastic.co/t/operator-upgrade-causes-nodes-to-be-restarted/219640/3 "2020-02-17T18:16:30Z")

</div>

thanks @sebgl , I missed that line in the docs!

Still, I think the Operator should not do anything if the spec of Elasticsearch did not change.

---

<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, 7:45am UTC](https://discuss.elastic.co/t/operator-upgrade-causes-nodes-to-be-restarted/219640/4 "2022-11-04T07:45:20Z")

</div>