# Deploying elasticsearch cluster in kubernetes - how to deal with storage? **URL:** \ **Category:** Elasticsearch\ **Created:** [December 12, 2018, 1:16am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-cluster-in-kubernetes-how-to-deal-with-storage/160456 "2018-12-12T01:16:55Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ethrbunny](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ethrbunny/32/34603_2.png) [@ethrbunny](https://discuss.elastic.co/u/ethrbunny)\ **Post date:** [December 12, 2018, 1:16am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-cluster-in-kubernetes-how-to-deal-with-storage/160456/1 "2018-12-12T01:16:56Z")
Im wanting to grow my elasticsearch installation into a cluster. To this end I'd like to run it under kubernetes but I can't figure out how to keep the various data stores (per container) properly assigned. IE if I were using dedicated hosts Id have local storage and each cluster member would use that storage. If I move to k8 I need to have a system that cluster members can come / go and know which data to associate with. Does that make any sense? Im sure this has been figured out / understood but I can't think of the proper question(s) to ask. Reading about clustering ([here](https://thoughts.t37.net/designing-the-perfect-elasticsearch-cluster-the-almost-definitive-guide-e614eabc1a87)) I get the sense that SANs aren't the way to go. Latency is low but local disks seem to be preferred. Accurate? Any pointers would be appreciated. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 9, 2019, 1:17am UTC](https://discuss.elastic.co/t/deploying-elasticsearch-cluster-in-kubernetes-how-to-deal-with-storage/160456/2 "2019-01-09T01:17:04Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.