ECK operator sizing

Elastic Orchestration Elastic Cloud on Kubernetes (ECK)
1

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?

2

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.