# Deploying ELK stack using ECK on GCK Auto Pilot **URL:** \ **Category:** Elastic Cloud on Kubernetes (ECK)\ **Created:** [June 10, 2022, 12:59pm UTC](https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891 "2022-06-10T12:59:48Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\ **Post date:** [June 10, 2022, 12:59pm UTC](https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891/1 "2022-06-10T12:59:48Z")
Hello, When I was first trying deploying elasticaserach stack using ECK on Google Cloud Kubernetes in Auto Pilot mode. I could not perform only one thing from the documentation which was setting `command: ['sh', '-c', 'sysctl -w vm.max_map_count=262144']` on the elasticserach nodes Do I really need this command to run on elasticserach pods and without that, I can expect some unwanted unexpected behavior of the cluster, or will there be just a max cap of RAM that the node can properly use? If so what is that value? I am kindly hoping for your answer. ---
**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:** [June 14, 2022, 12:37pm UTC](https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891/2 "2022-06-14T12:37:59Z")
We have a page in our documentation that explains this kernel setting here: [Virtual memory | Elastic Cloud on Kubernetes [master] | Elastic](https://www.elastic.co/guide/en/cloud-on-k8s/master/k8s-virtual-memory.html) ---
**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\ **Post date:** [June 14, 2022, 8:45pm UTC](https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891/3 "2022-06-14T20:45:49Z")
Hello Peter, thank you for your answer. My question was raised from my last experience trying to deploy elasticserach cluster using ECK and Google Cloud Kubernetes in Autopilot mode. When I tried to deploy [this](https://discuss.elastic.co/t/error-a-container-name-must-be-specified-for-pod-elk-monitoring-es-hot-0/291038) configuration you can notice that I kept privileged: **false** , because It's not allowed to run privileged pods as [this](https://cloud.google.com/kubernetes-engine/docs/concepts/autopilot-overview#no_privileged_pods) says(This generated some error about command but was running just without it). I still want to use autopilot mode for bigger abstraction, less overhead, and cheaper solution. Summering, my question is what are the limits that I should expect(like index size or maybe max\_heap setting) leaving **vm.max\_map\_count** as the default value 65536? ---
**Author:** ![Adriann](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adriann/32/77780_2.png) [@Adriann](https://discuss.elastic.co/u/Adriann)\ **Post date:** [June 17, 2022, 3:24pm UTC](https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891/4 "2022-06-17T15:24:41Z")
I have read the documentation one more time and I came to a conclusion that these privilege pods do not matter if you choose for example niofs storage type. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 15, 2022, 3:24pm UTC](https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891/5 "2022-07-15T15:24:57Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.