Create velero backup and schedule yamls for all the necessary things

[billimek]

Create velero backup and schedule yamls for all the necessary things

[billimek]

Learned a couple of things about this:

1. It doesn't seem necessary to create both a velero schedule and velero backup. By creating a schedule, a backup is automatically created.
2. Attempting to leverage multiple velero backups each also doing a restic backup of a volume results in problems:
   • It doesn't appear to be possible to run multiple different backups targeting the same restic repository. Velero will throw errors stating that something else is already using the restic repo
   • It isn't possible to designate multiple different velero restic repos per namespace. This is a hard-coded thing
3. Using a single velero backup to handle multiple deployment restic backups results in a strange state where the single restic repo has the multiple workloads all backed-up but with different 'snapshot' timestamps

[echel0n]

I believe #2 is resolved in their beta version right now, seems it cleans up the restic repo locks.

I my self am leaning towards moving away from app-centric backups and going for an all-in-one cluster backup with restic snaps annotated, fairly easy to just specify --include-namespaces when performing a restore.

[billimek]

Not needed as I'll use a single generic velero backup (defined as https://github.com/billimek/k8s-gitops/blob/master/storage/velero/velero.yaml#L26-L30)