Open Jean-Baptiste-Lasselle opened 5 months ago
First tooling stack i'm gonna try out is k8up + restic (note: wrestic was merged into k8up some time ago) :
--globals3endpoint value set the S3 endpoint to be used globally [$BACKUP_GLOBALS3ENDPOINT]
--globals3bucket value set the S3 bucket to be used globally [$BACKUP_GLOBALS3BUCKET]
--globalsecretaccesskey value set the S3 secret access key to be used globally [$BACKUP_GLOBALSECRETACCESSKEY]
--globalaccesskeyid value set the S3 access key id to be used globally [$BACKUP_GLOBALACCESSKEYID]
--datapath value, --mountpath value to which path the PVCs should get mounted in the backup container (default: "/data") [$BACKUP_DATAPATH]
k8up.io/backupcommand-container | Specify in which container inside pod backup should be done
even there is an example : https://docs.k8up.io/k8up/2.8/how-tos/application-aware-backups.html#_pick_a_specific_container
IT is possible to find out exactly which minio bucket is matching which user:
This means that to restore a given user's data after a teraform destroy, i need to be able to force a given pvc to create a persistent volue from a given snapshot, and to use csi volume snapshotter. I think i'm right there.
If this works, then i would need to keep track a a database matching users and their volume snapshot
So well this issue is about bringing a full backup restore automation to the jupyterhub part of the platform.