Docs 354 kubernetes cron job for backups

Created by: Tirokk

Authored by roschaefer May 8, 2019 Merged May 15, 2019

---

Pullrequest

Dear reviewer, the documentation and the tool velero work as expected on Digital Ocean's kubernetes clusters. However, sometimes I see strange errors like:

pod has unbound immediate PersistentVolumeClaims (repeated 3 times)

or

Volume is already exclusively attached to one node and can't be attached to another

When I delete/re-apply the deployments with:

$ kubectl delete -f deployment/human-connection/deployment-neo4j.yaml -f deployment/human-connection/deployment-backend.yaml
# wait until all objects are torn down
$ kubectl apply -f deployment/human-connection/deployment-neo4j.yaml -f deployment/human-connection/deployment-backend.yaml

And wait for a loooooong time ... (~15min)

The cluster is back again. I find it strange but I think this fulfills the requirements for issue #354 (closed).

Issues

• fixes #354 (closed)

Checklist

• None

How2Test

• Follow the documentation: https://docs.human-connection.org/human-connection/v/docs-354-kubernetes_cron_job_for_backups/deployment/disaster-recovery/velero

Todo

• None