# Deploying ELK stack using ECK on GCK Auto Pilot

**URL:** <https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891>\
**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:** 1\
**Showing post:** 3

<div class="post-metadata">

**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")

</div>

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?

---

_[View the full topic](https://discuss.elastic.co/t/deploying-elk-stack-using-eck-on-gck-auto-pilot/306891)._