# How to replacing ECK data node with minimal downtime/data moving?

**URL:** <https://discuss.elastic.co/t/how-to-replacing-eck-data-node-with-minimal-downtime-data-moving/353739>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [February 21, 2024, 2:03am UTC](https://discuss.elastic.co/t/how-to-replacing-eck-data-node-with-minimal-downtime-data-moving/353739 "2024-02-21T02:03:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![elastic13](https://avatars.discourse-cdn.com/v4/letter/e/2bfe46/32.png) [@elastic13](https://discuss.elastic.co/u/elastic13)\
**Post date:** [February 21, 2024, 2:03am UTC](https://discuss.elastic.co/t/how-to-replacing-eck-data-node-with-minimal-downtime-data-moving/353739/1 "2024-02-21T02:03:03Z")

</div>

Hello,  
we running an ES cluster using ECK installed on AWS EKS, with each ES instance per node.  
We often need to update the underlying AWS worker nodes for many scenarios:

- fixing runC CVE-2024-21626
- upgrade K8S version - which happens every 5-6 months

How to replacing k8s node with minimal data migrate to other nodes (we have many TB) ?

Is there a way to create new node, then replacing the old pod on old node with new pod on new node, and detach VPC from old node, attach the existing VPC? If that is possible then we can afford having down time like \< 1 min per node.

Thanks  
PS: we using karpenter to manage node, if that matters.

---

<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 20, 2024, 2:03am UTC](https://discuss.elastic.co/t/how-to-replacing-eck-data-node-with-minimal-downtime-data-moving/353739/2 "2024-03-20T02:03:18Z")

</div>

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