# How to scale up and down nodes automatically?

**URL:** <https://discuss.elastic.co/t/how-to-scale-up-and-down-nodes-automatically/224089>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [March 18, 2020, 11:21am UTC](https://discuss.elastic.co/t/how-to-scale-up-and-down-nodes-automatically/224089 "2020-03-18T11:21:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Anya\_Sabo](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/anya_sabo/32/49903_2.png) [@Anya\_Sabo](https://discuss.elastic.co/u/Anya_Sabo)\
**Post date:** [March 18, 2020, 1:29pm UTC](https://discuss.elastic.co/t/how-to-scale-up-and-down-nodes-automatically/224089/2 "2020-03-18T13:29:17Z")

</div>

That's correct, to scale you would change the number of nodes in the nodeSet (or potentially [replace a nodeSet](https://www.elastic.co/guide/en/cloud-on-k8s/1.0/k8s-orchestration.html#k8s-orchestration-limitations) to increase storage/node). We do not have support for the HPA or another autoscaling mechanism at this time. Unfortunately adopting the HPA model for Elasticsearch is challenging, as it expects there to be a single underlying deployment/sset/etc. In this case multiple ssets (can) make up an Elasticsearch resource. We hope to have a better autoscaling story in the future, but for now you would need to create something tailored for your use case.

---

_[View the full topic](https://discuss.elastic.co/t/how-to-scale-up-and-down-nodes-automatically/224089)._