Velero
Last updated
Was this helpful?
Last updated
Was this helpful?
I tried Velero and it did not work reliably all the time. Sometimes the kubernetes cluster crashes during recovery or data is not fully recovered.
Feel free to test it out and update this documentation once you feel that it's working reliably. It is very likely that Digital Ocean had some bugs when I tried out the steps below.
We use for on premise backups, we tested on version v0.11.0, you can find their documentation .
Our kubernets configurations adds some annotations to pods. The annotations define the important persistent volumes that need to be backed up. Velero will pick them up and store the volumes in the same cluster but in another namespace velero.
You have to install the binary velero on your computer and get a tarball of the latest release. We use v0.11.0 so visit the page and download and extract e.g. .
Follow their instructions to setup the Velero namespace. We use and , so check out Velero's instructions how to setup :
Once completed, you should see the namespace in your kubernetes dashboard.
When you create your deployments for Human Connection the required annotations should already be in place. So when you create a backup of namespace human-connection:
That should backup your persistent volumes, too. When you enter:
You should see the persistent volumes at the end of the log:
Feel free to try out if you loose any data when you simulate a disaster and try to restore the namespace from the backup:
Wait until the wrongdoing has completed, then:
Now, I keep my fingers crossed that everything comes back again. If not, I feel very sorry for you.
Inspect the created backups:
Check out the . You can create a regular schedule e.g. with: