From 9f3f6cfe02054afd017648106dad4de3952c5479 Mon Sep 17 00:00:00 2001 From: mattwr18 Date: Thu, 30 Jan 2020 21:02:27 +0100 Subject: [PATCH] Set up PVC with helm!! - It turns out we can set it up with helm, it was just an issue with not starting with a clean slate. I guess it probably would have been better to just set it up from scratch and deleted the develop server, like we intend to do in production. --- .../templates/volumes/pvc-neo4j-data.yaml | 10 ++++++++++ .../templates/volumes/pvc-uploads.yaml | 12 ++++++++++++ 2 files changed, 22 insertions(+) create mode 100644 deployment/helm/human-connection/templates/volumes/pvc-neo4j-data.yaml create mode 100644 deployment/helm/human-connection/templates/volumes/pvc-uploads.yaml diff --git a/deployment/helm/human-connection/templates/volumes/pvc-neo4j-data.yaml b/deployment/helm/human-connection/templates/volumes/pvc-neo4j-data.yaml new file mode 100644 index 000000000..e89844181 --- /dev/null +++ b/deployment/helm/human-connection/templates/volumes/pvc-neo4j-data.yaml @@ -0,0 +1,10 @@ +apiVersion: v1 +kind: PersistentVolumeClaim +metadata: + name: neo4j-data-claim +spec: + accessModes: + - ReadWriteOnce + resources: + requests: + storage: 5Gi diff --git a/deployment/helm/human-connection/templates/volumes/pvc-uploads.yaml b/deployment/helm/human-connection/templates/volumes/pvc-uploads.yaml new file mode 100644 index 000000000..4d2ae7627 --- /dev/null +++ b/deployment/helm/human-connection/templates/volumes/pvc-uploads.yaml @@ -0,0 +1,12 @@ + +kind: PersistentVolumeClaim +apiVersion: v1 +metadata: + name: uploads-claim +spec: + accessModes: + - ReadWriteOnce + resources: + requests: + storage: 8Gi +