# PV sizing problem in k8s environment where PV resizing is not possible

**URL:** <https://forum.weaviate.io/t/pv-sizing-problem-in-k8s-environment-where-pv-resizing-is-not-possible/2617>\
**Category:** Support\
**Created:** [June 5, 2024, 7:58am UTC](https://forum.weaviate.io/t/pv-sizing-problem-in-k8s-environment-where-pv-resizing-is-not-possible/2617 "2024-06-05T07:58:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Rio](https://avatars.discourse-cdn.com/v4/letter/r/ea666f/32.png) [@Rio](https://forum.weaviate.io/u/Rio)\
**Post date:** [June 5, 2024, 7:58am UTC](https://forum.weaviate.io/t/pv-sizing-problem-in-k8s-environment-where-pv-resizing-is-not-possible/2617/1 "2024-06-05T07:58:22Z")

</div>

Hello. Team.

I constructed weaviate with helm chart in isolated k8s cluster.  
Unfortunately, the k8s cluster I use does not support PV resizing.  
In this case, how should I decide the PV capacity?  
The default value of Helm chart is 32G,  
should I create it from the beginning with the maximum storage size?

Thank you.

---

<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:** [June 7, 2024, 5:59pm UTC](https://forum.weaviate.io/t/pv-sizing-problem-in-k8s-environment-where-pv-resizing-is-not-possible/2617/2 "2024-06-07T17:59:01Z")

</div>

Hi @Rio !

That can bite you back you on the long run.

if you allocate some disk space, and grow beyond it, requiring more disk than initially allocated, you will need to backup and restore on a bigger disk sized cluster.

Note that this is on yours k8s issue lack of PV resizing. So a pv resizing can really help you here.  
For Weaviate, as long as it has disk space, it will keep writing.

in 1.25+ we are introducing some ground base features that will allow, for example dynamic sharding. With that, you will be able to spin a new node with 100G, and drain the initial 32G node.

Check here our roadmap for more info on that:

> **[Weaviate Core Roadmap | Weaviate - Vector Database](https://weaviate.io/developers/weaviate/roadmap)**
>
> Weaviate is an open source project that is hosted on GitHub. GitHub uses issues to request features and to track projects. This page highlights some of the issues that Weaviate is working on for upcoming releases.

There are a lot of factors that can influentiate on the size of disk size used by Weaviate, so you’ll need to add some similar dataset and estimate based on that.

Let me know if this helps 🙂

Thanks!