# Additional storage volumes

**URL:** <https://discourse.jupyter.org/t/additional-storage-volumes/5012>\
**Category:** Zero to JupyterHub on Kubernetes\
**Tags:** jupyterhub, how-to, help-wanted\
**Created:** [June 30, 2020, 6:32am UTC](https://discourse.jupyter.org/t/additional-storage-volumes/5012 "2020-06-30T06:32:45Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![cbell](https://yyz1.discourse-cdn.com/flex031/user_avatar/discourse.jupyter.org/cbell/32/1079_2.png) [@cbell](https://discourse.jupyter.org/u/cbell)\
**Post date:** [July 17, 2020, 5:24pm UTC](https://discourse.jupyter.org/t/additional-storage-volumes/5012/7 "2020-07-17T17:24:49Z")

</div>

I have had success hosting the hub sqlite db on NFS. We are using AWS EFS to host this.

Here’s a portion of the helm chart:

```
hub:
  extraVolumes:
    - name: hub-db-dir
      persistentVolumeClaim:
        claimName: nfs-host-pvc

```

Here’s a pvc config:

```
apiVersion: v1 
kind: PersistentVolume 
metadata: 
  name: nfs-host-pv 
spec: 
  capacity: 
    storage: 1Gi 
  accessModes: 
    - ReadWriteMany 
  nfs: 
    server: amazon-efs-hub-storage-server
    path: "/host-hub" 
 
--- 
kind: PersistentVolumeClaim 
apiVersion: v1 
metadata: 
  name: nfs-host-pvc
spec: 
  accessModes: 
    - ReadWriteMany 
  storageClassName: "" 
  resources: 
    requests: 
      storage: 1Gi

```

The only thing I’ll note, is that using Helm - there was a bit of an annoyance that a basic deployment needs to be deployed, and then this change can be pushed. Little more on that was discussed here: [JupyterHub hub-db-dir PV Question](https://discourse.jupyter.org/t/jupyterhub-hub-db-dir-pv-question/2157)

---

_[View the full topic](https://discourse.jupyter.org/t/additional-storage-volumes/5012)._