# Deletion of eck-operator pod

**URL:** <https://discuss.elastic.co/t/deletion-of-eck-operator-pod/296360>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [February 5, 2022, 12:45pm UTC](https://discuss.elastic.co/t/deletion-of-eck-operator-pod/296360 "2022-02-05T12:45:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![pkaramol](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pkaramol/32/22610_2.png) [@pkaramol](https://discuss.elastic.co/u/pkaramol)\
**Post date:** [February 5, 2022, 12:45pm UTC](https://discuss.elastic.co/t/deletion-of-eck-operator-pod/296360/1 "2022-02-05T12:45:14Z")

</div>

We are upgrading out istio version.

ECK (and the `elastic` / `kibana` pods) have `istio` sidecar injected.

For all pods to take the new sidecars, a restart is needed, so that new pods are generated.

This is more or less manageable with `kibana` / `elastic`.

**My question is whether it is ok to run `kubectl delete pod elastic-operator-0`.**

Apart from us being unable to perform any operation during the pod's unavailability, is there any other impact? Assuming the pod is recreated and back to `Running` state, everything will be normal again?

---

<div class="post-metadata">

**Author:** ![BenB196](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/benb196/32/83401_2.png) [@BenB196](https://discuss.elastic.co/u/BenB196)\
**Post date:** [February 5, 2022, 1:37pm UTC](https://discuss.elastic.co/t/deletion-of-eck-operator-pod/296360/2 "2022-02-05T13:37:38Z")

</div>

I believe that this should be fine. (I've done a `drain` on a node with the operator before and it rebuilt just fine).

They also mention deleting the pod (and even the deployment) for migrating from ECK yaml install to helm install ([Install ECK using the Helm chart | Elastic Cloud on Kubernetes [1.9] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/1.9/k8s-install-helm.html#k8s-migrate-to-helm)).

> Uninstall the current ECK operator. You can do this by taking the operator.yaml file you used to install the operator and running kubectl delete -f operator.yaml. Alternatively, you could delete each resource individually.

So, given these 2 things, I don't believe you will run into any issues deleting the ECK operator pod and letting it immediately recreate it.

---

<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:** [March 5, 2022, 1:38pm UTC](https://discuss.elastic.co/t/deletion-of-eck-operator-pod/296360/3 "2022-03-05T13:38:30Z")

</div>

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