<p>I want to setup Elasticsearch on Kubernetes Cluster using Helm. I can setup Elasticsearch on Kubernetes Cluster without persistence. I am using below helm chart. </p>

<pre><code>helm install --name elasticsearch incubator/elasticsearch \
    --set master.persistence.enabled=false \
    --set data.persistence.enabled=false \
    --set image.tag=6.4.2 \
    --namespace logging
</code></pre>

<p>However, i am not able to use it with Persistence. Moreover i am confused as i am using neither cloud based storage(aws,gce) nor nfs. I am using Local VM storage. 
I added disk in my VM environment formated it under ext4. And now i am trying to use it as a persistent disk for my elasticsearch Deployment. </p>

<p>I tried lots of ways, not working much.
For any data if you need i would be helpful to provide. 
But kindly get a solution which will work.</p>

<p>I just need help..</p>

Bisshwajit Samanta
<p>I don't believe this chart will support local storage. </p>

<p>Looking at the volumeClaimTemplate <a href="https://github.com/helm/charts/blob/4bde54c86c3d3c1be56e428d810b93431b122e2d/incubator/elasticsearch/templates/master-statefulset.yaml#L182" rel="nofollow noreferrer">such as on the master-statefulset.yaml</a> shows that it's missing key parameters for a local volume setup (such as path, nodeAffinity, volumeBindingMode) described <a href="https://kubernetes.io/docs/concepts/storage/volumes/#local" rel="nofollow noreferrer">here</a>. If you are using a cloud deployment, just use a cloud volume claim. If you have deployed a cluster on a on-prem or just onto your computer, then you should fork the chart and adjust the volume claims to meet the requirements for local storage.</p>

<p>Either way on your future posts you should include relevant logs. With kubernetes errors it's helpful to see from all parts of the stack such as: kubernetes control plane logs, object events (like the output from describing the volume claim), helm logs, elasticsearch pod logs failing to discover a volume, etc etc.  </p>
