# Up-Sizing Resources with Helm Chart / Kubernetes

**URL:** <https://discuss.elastic.co/t/up-sizing-resources-with-helm-chart-kubernetes/290481>\
**Category:** Elasticsearch\
**Created:** [November 29, 2021, 7:04pm UTC](https://discuss.elastic.co/t/up-sizing-resources-with-helm-chart-kubernetes/290481 "2021-11-29T19:04:15Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jamiejackson](https://avatars.discourse-cdn.com/v4/letter/j/d07c76/32.png) [@jamiejackson](https://discuss.elastic.co/u/jamiejackson)\
**Post date:** [November 29, 2021, 7:04pm UTC](https://discuss.elastic.co/t/up-sizing-resources-with-helm-chart-kubernetes/290481/1 "2021-11-29T19:04:15Z")

</div>

I have a 3-node ES cluster which was spun up with the Elasticsearch Helm chart ( [helm-charts/README.md at main · elastic/helm-charts · GitHub](https://github.com/elastic/helm-charts/blob/main/elasticsearch/README.md) ).

I want to bump up the heap/CPU/memory allocations, so I've created a new, dedicated node group with three "large" EC2 instances (2CPU/8GBRAM).

What's the proper sequence for migrating/up-sizing into that node group?

I had thought to add a second Helm configuration for the new node group and go from there, but I don't want to make any assumptions, so I'll wait to see what the proper procedure is.

Thanks,  
Jamie

---

<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:** [December 27, 2021, 7:04pm UTC](https://discuss.elastic.co/t/up-sizing-resources-with-helm-chart-kubernetes/290481/2 "2021-12-27T19:04:24Z")

</div>

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