# ECK Sizing **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [February 25, 2020, 4:03pm UTC](https://discuss.elastic.co/t/eck-sizing/220887 "2020-02-25T16:03:53Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![Nevetha\_K](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/nevetha_k/32/48163_2.png) [@Nevetha\_K](https://discuss.elastic.co/u/Nevetha_K)\ **Post date:** [February 25, 2020, 4:03pm UTC](https://discuss.elastic.co/t/eck-sizing/220887/1 "2020-02-25T16:03:53Z")
Hi - We are considering moving to ECK to be run on Openshift Platform. Currently the elasticsearch is running on a VM with (5 Node cluster with 8x32 VM size). Once I move to OCP, how will the node sizing work? Is it going to be a 1:1 sizing for VM:Kubernetes Worker Node? For eg, will I need 5 Worker Nodes with 8x32 and each worker node running one container? ---
**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:** [February 25, 2020, 4:54pm UTC](https://discuss.elastic.co/t/eck-sizing/220887/2 "2020-02-25T16:54:38Z")
You can size your Kubernetes nodes however you'd like, but sizing your Elasticsearch resource to the same as the existing Elasticsearch VMs is a reasonable place to start in my opinion. You may want to adjust up or down from there. ---
**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, 7:46am UTC](https://discuss.elastic.co/t/eck-sizing/220887/3 "2022-11-04T07:46:39Z")