# Helm-chart and ExtraVolumes

**URL:** <https://discuss.elastic.co/t/helm-chart-and-extravolumes/227907>\
**Category:** Elasticsearch\
**Created:** [April 14, 2020, 12:08pm UTC](https://discuss.elastic.co/t/helm-chart-and-extravolumes/227907 "2020-04-14T12:08:46Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jgato](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jgato/32/66279_2.png) [@jgato](https://discuss.elastic.co/u/jgato)\
**Post date:** [April 14, 2020, 12:08pm UTC](https://discuss.elastic.co/t/helm-chart-and-extravolumes/227907/1 "2020-04-14T12:08:47Z")

</div>

Hi there,  
I am deploying a cluster using your helm-chart package and everything goes ok. Now I would like to make something more advanced, like creating a backup repo, and export this directory as a volume.

Trying something like that:

```auto
esConfig:
  elasticsearch.yml: |
    path.repo: "/backup/data/"
...
...
extraVolumes: |
  - name: backup-volume
    emptydir: {}

extraVolumeMounts: |
   - name: backup-volume
     mountPath: /backup/data/

```

How I have to indicate to use a PVC with my default StorageClass to create the backup-volume?

Many thanks

---

<div class="post-metadata">

**Author:** ![fatmcgav](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fatmcgav/32/18305_2.png) [@fatmcgav](https://discuss.elastic.co/u/fatmcgav)\
**Post date:** [April 16, 2020, 9:21am UTC](https://discuss.elastic.co/t/helm-chart-and-extravolumes/227907/2 "2020-04-16T09:21:40Z")

</div>

So currently the Helm chart only creates a single Persistent Volume (PV) and Persistent Volume Claim (PVC) per Pod, which is intended to contain all the data pertinent to that specific Elasticsearch node.

When it comes to managing a snapshot volume for Elasticsearch, we would recommend that the PV is created by a cluster administrator.  
This is due to the fact that the snapshot filesystem needs to be shared by every Elasticsearch node [1], and therefore pod, within an Elasticsearch cluster. This requires either some kind of shared filesystem that Kubernetes can leverage, and a PV created with a `ReadWriteMany` accessMode configuration [2], or using a different Elasticsearch repository plugin such as GCS or S3. [3]

If this PVC was managed within the Helm chart, then the end result would be multiple PV's being created, which wouldn't work for an Elasticsearch snapshot repository.

I hope that clarifies things, but please feel free to ask if you need any further assistance.

Regards  
Gavin

[1] [https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html#snapshots-filesystem-repository](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html#snapshots-filesystem-repository)  
[2] [https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes)  
[3] [https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html#snapshots-repository-plugins](https://www.elastic.co/guide/en/elasticsearch/reference/current/snapshots-register-repository.html#snapshots-repository-plugins)

---

<div class="post-metadata">

**Author:** ![jgato](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jgato/32/66279_2.png) [@jgato](https://discuss.elastic.co/u/jgato)\
**Post date:** [April 16, 2020, 9:56am UTC](https://discuss.elastic.co/t/helm-chart-and-extravolumes/227907/3 "2020-04-16T09:56:49Z")

</div>

Absolutly, thanks!!!

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 14, 2020, 9:56am UTC](https://discuss.elastic.co/t/helm-chart-and-extravolumes/227907/4 "2020-05-14T09:56:53Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.