Unexpected pod restart after operator upgrade to 2.3


According to documentation, 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!

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