Add 3rd party controller to build an automatic way to backup all volume resources in the cluster

[duyanghao]

Describe the problem/challenge you have
Refers to #2355

Is there a do-one-command or automatic way for us to backup all persistent volume resources in the cluster? Right now, we have to add relevant annotations to all of pods with pv resources in cluster, which is complicated and unpractical in a production environment.

Velero doesn't have a built-in command to do this, you'd need to write your own script/automation. You could check out this community project: https://github.com/bitsbeats/velero-pvc-watcher

Describe the solution you'd like
Build an automatic way to backup all volume resources in the cluster

Anything else you would like to add:
@skriss To solve this, I have created a repo called velero-volume-controller, which is a Kubernetes controller for velero that detects and adds relevant backup annotation to pods with volumes. Could you take a look at this and add it to the 3rd party controller part in the velero Restic Integration docs?

[carlisia]

Related:

• Make it easy to mark/unmark a volume for restic backup #605
• Add option to back up all volumes by default with restic #1871

[carlisia]

I added this topic to our community meeting tomorrow (3/31): https://hackmd.io/Jq6F5zqZR7S80CeDWUklkA?both#March-31-2020.

[nrb]

@duyanghao Do you to continue supporting this controller? Is it commercially backed?

[duyanghao]

@nrb

Do you to continue supporting this controller?

Yes

Is it commercially backed?

Not yet, but currently, our team plans to use this controller combined with velero Restic Integration to backup and restore Kubernetes clusters in a production environment.

[skriss]

FYI we already have https://github.com/vmware-tanzu/velero/blob/master/site/docs/master/restic.md#3rd-party-controller in our docs. I don't see any issue with linking to third-party community projects, we should just be clear about ownership.

[skriss]

btw, this looks like a neat project @duyanghao!

[duyanghao]

FYI we already have https://github.com/vmware-tanzu/velero/blob/master/site/docs/master/restic.md#3rd-party-controller in our docs. I don't see any issue with linking to third-party community projects, we should just be clear about ownership.

@skriss I guess you mistake my meaning of add it to the 3rd party controller part. What I want to say is that maybe velero official can add velero-volume-controller to the list of velero restic 3rd party controller as an implemented
choice since the recommended controller(i.e. velero-pvc-watcher) can't satisfy the demand of building an automatic way to backup all volume resources in the cluster.

I have create a PR for this.