# ECK operator sizing

**URL:** <https://discuss.elastic.co/t/eck-operator-sizing/261868>\
**Category:** Elastic Cloud on Kubernetes (ECK)\
**Created:** [January 22, 2021, 4:46am UTC](https://discuss.elastic.co/t/eck-operator-sizing/261868 "2021-01-22T04:46:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![deepak\_deore](https://avatars.discourse-cdn.com/v4/letter/d/9fc29f/32.png) [@deepak\_deore](https://discuss.elastic.co/u/deepak_deore)\
**Post date:** [January 22, 2021, 4:46am UTC](https://discuss.elastic.co/t/eck-operator-sizing/261868/1 "2021-01-22T04:46:10Z")

</div>

elastic-operator pod was in CrashLoopBackOff on an EKS cluster of 125 worker node and 84 namespaces  
it was OOMKilled after deleting manually to come out of crashloop, default memory request is 128M, making it 256M also got it OOMKilled

Keeping memory request 512M made it stable

Question: are there guidelines somewhere for elastic operator sizing?

---

<div class="post-metadata">

**Author:** ![pebrc](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pebrc/32/101790_2.png) [@pebrc](https://discuss.elastic.co/u/pebrc)\
**Post date:** [January 23, 2021, 11:03am UTC](https://discuss.elastic.co/t/eck-operator-sizing/261868/2 "2021-01-23T11:03:45Z")

</div>

We don't have specific guidelines yet as the memory requirements depend very much on size of your Kubernetes cluster and the number of Elastic stack applications you want to run. But it should be possible to use the Vertical Pod Autoscaler if it is available in your Kubernetes environment.

---

<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:** [November 4, 2022, 8:22am UTC](https://discuss.elastic.co/t/eck-operator-sizing/261868/3 "2022-11-04T08:22:15Z")

</div>