Up-Sizing Resources with Helm Chart / Kubernetes

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 ).

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.


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