mirrors/velero
1
0
Fork 0
mirror of https://github.com/vmware-tanzu/velero.git synced 2026-01-06 05:25:40 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

update 3rd party controllers for v1.3.2 restic docs

Browse Source 
Signed-off-by: duyanghao <1294057873@qq.com>
This commit is contained in:
duyanghao
2020-04-08 10:22:14 +08:00
parent 90c324a76d
commit d3deb2b1e2
1 changed files with 8 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
site/docs/v1.3.2/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