# Multi-POD deployment in K8

**URL:** <https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993>\
**Category:** Support\
**Created:** [April 11, 2024, 8:42pm UTC](https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993 "2024-04-11T20:42:22Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![abhisheknamdeo](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@abhisheknamdeo](https://forum.weaviate.io/u/abhisheknamdeo)\
**Post date:** [April 11, 2024, 8:42pm UTC](https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993/1 "2024-04-11T20:42:22Z")

</div>

We are using Weaviate deployment using helm on EKS cluster.  
[weaviate-helm/weaviate/templates at master · weaviate/weaviate-helm · GitHub](https://github.com/weaviate/weaviate-helm/tree/master/weaviate/templates)

We see poor performance using single POD Weaviate and looking for the option to have multiple PODs deployed to have stability in the application.

I was unable to find details on how to upgrade the deployment to multi POD model? Do we have any document explaining the configuration required?

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [April 12, 2024, 12:54pm UTC](https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993/2 "2024-04-12T12:54:50Z")

</div>

hi @abhisheknamdeo!

Welcome to our community 🤗

The best path for your scenario will be deploying a second weaviate instance, with the desired replicas.

Then you create your collections, and migrate your data over.

We have this handy script to help you on that:

> **[Migrate data | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/manage-data/migrate)**
>
> Overview

Let me know if this helps!

---

<div class="post-metadata">

**Author:** ![abhisheknamdeo](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@abhisheknamdeo](https://forum.weaviate.io/u/abhisheknamdeo)\
**Post date:** [April 12, 2024, 2:45pm UTC](https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993/3 "2024-04-12T14:45:08Z")

</div>

Thanks for your response. As I understand, I should be creating a new Weaviate instance in EKS with multiple replicas and later migrate the data from current Weaviate instance to the new one.

Could you please point me to the location where we can define replicas? I was unable to find that in the HELM deployment configurations.

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [April 12, 2024, 2:47pm UTC](https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993/4 "2024-04-12T14:47:14Z")

</div>

there you go:

> <https://github.com/weaviate/weaviate-helm/blob/6af507027de9777a481cc48cfb43fcfe7e706118/weaviate/values.yaml#L61>

---

<div class="post-metadata">

**Author:** ![abhisheknamdeo](https://avatars.discourse-cdn.com/v4/letter/a/90db22/32.png) [@abhisheknamdeo](https://forum.weaviate.io/u/abhisheknamdeo)\
**Post date:** [April 12, 2024, 3:00pm UTC](https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993/5 "2024-04-12T15:00:48Z")

</div>

Thank you so much. This helps.

I increased the replica count to 3. No we see three PODs, but with that we see three PV and three PVC.

We assume the new volumes doesn’t contain the same data that we had in initial volume, is that correct? Do we have an inbuilt feature to sync data between these volumes or should be done manually?

Here are the resources -

#-\> kubectl get pods | grep weaviate  
weaviate-0 1/1 Running 0 47m  
weaviate-1 1/1 Running 1 (49m ago) 49m  
weaviate-2 1/1 Running 0 47m  
[root@AWSBZZNVAL0009:/root]#  
#-\> kubectl get pv  
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE  
pvc-79fcd7fe-86ef-431c-965e-641634978e53 1000Gi RWO Delete Bound weaviate/weaviate-data-weaviate-2 gp3 91m  
pvc-9b8d33fe-a498-47f9-9627-44762bec179a 1000Gi RWO Delete Bound weaviate/weaviate-data-weaviate-0 gp3 50d  
pvc-a9ee6ce3-cdd7-4205-b5c7-31e68c37c3d3 1000Gi RWO Delete Bound weaviate/weaviate-data-weaviate-1 gp3 128m  
[root@AWSBZZNVAL0009:/root]#  
#-\> kubectl get pvc  
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE  
weaviate-data-weaviate-0 Bound pvc-9b8d33fe-a498-47f9-9627-44762bec179a 1000Gi RWO gp3 50d  
weaviate-data-weaviate-1 Bound pvc-a9ee6ce3-cdd7-4205-b5c7-31e68c37c3d3 1000Gi RWO gp3 128m  
weaviate-data-weaviate-2 Bound pvc-79fcd7fe-86ef-431c-965e-641634978e53 1000Gi RWO gp3 91m

---

<div class="post-metadata">

**Author:** ![DudaNogueira](https://yyz1.discourse-cdn.com/flex027/user_avatar/forum.weaviate.io/dudanogueira/32/7846_2.png) [@DudaNogueira](https://forum.weaviate.io/u/DudaNogueira)\
**Post date:** [April 16, 2024, 12:19pm UTC](https://forum.weaviate.io/t/multi-pod-deployment-in-k8/1993/6 "2024-04-16T12:19:25Z")

</div>

that’s right.

you now have 3 weaviates running in multi node.

Now you can create your collections and specify to use a replication factor of 3, for example:

> **[Replication | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/configuration/replication)**
>
> Weaviate instances can be replicated to increase availability and read throughput, and to enable zero-downtime upgrades. On this page, you will learn how to set replication for your Weaviate instance.
