# ElasticSearch Storage and Kubernetes

**URL:** <https://discuss.elastic.co/t/elasticsearch-storage-and-kubernetes/170222>\
**Category:** Elasticsearch\
**Created:** [February 27, 2019, 6:17pm UTC](https://discuss.elastic.co/t/elasticsearch-storage-and-kubernetes/170222 "2019-02-27T18:17:14Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 27, 2019, 6:26pm UTC](https://discuss.elastic.co/t/elasticsearch-storage-and-kubernetes/170222/2 "2019-02-27T18:26:52Z")

</div>

GlusterFS is as far as I know not recommended, and there have been reports of issues. Have a look at the following threads:

> [@Elasticsearch run in kubernetes](https://discuss.elastic.co/t/elasticsearch-run-in-kubernetes/160679):
>
> Hi, all I run Elasticsearch 6.2.2 in Kubernetes and use glusterfs as storage backend. When i start is works well, everything looks OK. But run after a while, health of that some indices turned Red. I don't know what happen. I am the beginner for the Elasticsearch. I use local file system as storage backend before, it didn't find this problem. what is the best solution to share the elastic data among all the kubernetes nodes? Thanks. Below is my environments. apiVersion: extensions/v1beta1…

> [@Underlying file changed by an external force](https://discuss.elastic.co/t/underlying-file-changed-by-an-external-force/137555):
>
> Using elasticsearch cluster( 3 servers) with kubernetes, but elasticsearch cluster can not wrok fine and log show as below: [2018-06-27T05:48:31,798][WARN][o.e.c.r.a.AllocationService] [sBJEWnS] failing shard [failed shard, shard [logstash-2018.06.27][4], node[sBJEWnS1R1qL7blJL9Wl0Q], [P], recovery\_source[existing recovery], s[INITIALIZING], a[id=CSql7\_M8QnmfnylNrN-LFQ], unassigned\_info[[reason=ALLOCATION\_FAILED], at[2018-06-27T05:48:30.059Z], failed\_attempts[1], delayed=false, details[failed…

I suspect there might be additional ones if you search the forum.

---

_[View the full topic](https://discuss.elastic.co/t/elasticsearch-storage-and-kubernetes/170222)._
