At the moment, the application needs two persistent volumes:
/data/ folder where
neo4j stores its database and
/nitro-backend/public/uploads where the backend stores uploads.
As a matter of precaution, the persistent volume claims that setup these volumes live in a separate folder. You don't want to accidently loose all your data in your database by running
kubectl delete -f human-connection/
or do you?
Run the following:
# in folder deployments/$ kubectl apply -f volumespersistentvolumeclaim/neo4j-data-claim createdpersistentvolumeclaim/uploads-claim created
We tested a couple of options how to do disaster recovery in kubernetes. First, there is the offline backup strategy of the community edition of Neo4J, which you can also run on a local installation. Kubernetes also offers so-called volume snapshots. Changing the reclaim policy of your persistent volumes might be an additional safety measure. Finally, there is also a kubernetes specific disaster recovery tool called Velero.