vmware-tanzu
/
velero
mirror of https://github.com/vmware-tanzu/velero.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #2393 from duyanghao/add-velero-volume-controller 

Add velero-volume-controller as an implemented choice of velero restic 3rd party controller
pull/2406/head
Nolan Brubaker 2020-04-07 15:38:48 -04:00 committed by GitHub
parent fffed56319 a7ebca2453
commit 90c324a76d
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 16 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
site/docs/master/restic.md
View File

@ -410,7 +410,7 @@ within each restored volume, under `.velero`, whose name is the UID of the Veler
1. Once all such files are found, the init container's process terminates successfully and the pod moves
on to running other init containers/the main containers.
## 3rd party controller
## 3rd party controllers
### Monitor backup annotation
@ -418,6 +418,12 @@ Velero does not currently provide a mechanism to detect persistent volume claims
To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watcher][7]
### Add backup annotation
Velero does not currently provide a single command or automatic way to backup all volume resources in the cluster without annotating pods or pod templates.
The [velero-volume-controller][10] written by duyanghao helps to solve this problem by adding backup annotation to pods with volumes automatically.
[1]: https://github.com/restic/restic
[2]: customize-installation.md#enable-restic-integration
[3]: https://github.com/vmware-tanzu/velero/releases/
@ -427,3 +433,4 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch
[7]: https://github.com/bitsbeats/velero-pvc-watcher
[8]: https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv
[9]: https://github.com/restic/restic/issues/1800
[10]: https://github.com/duyanghao/velero-volume-controller

9
site/docs/v1.3.1/restic.md
View File

@ -410,7 +410,7 @@ within each restored volume, under `.velero`, whose name is the UID of the Veler
1. Once all such files are found, the init container's process terminates successfully and the pod moves
on to running other init containers/the main containers.
## 3rd party controller
## 3rd party controllers
### Monitor backup annotation
@ -418,6 +418,12 @@ Velero does not currently provide a mechanism to detect persistent volume claims
To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watcher][7]
### Add backup annotation
Velero does not currently provide a single command or automatic way to backup all volume resources in the cluster without annotating pods or pod templates.
The [velero-volume-controller][10] written by duyanghao helps to solve this problem by adding backup annotation to pods with volumes automatically.
[1]: https://github.com/restic/restic
[2]: customize-installation.md#enable-restic-integration
[3]: https://github.com/vmware-tanzu/velero/releases/
@ -427,3 +433,4 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch
[7]: https://github.com/bitsbeats/velero-pvc-watcher
[8]: https://docs.microsoft.com/en-us/azure/aks/azure-files-dynamic-pv
[9]: https://github.com/restic/restic/issues/1800
[10]: https://github.com/duyanghao/velero-volume-controller