From 819657d863f78f86bbb65425e8b97c40d6ce6948 Mon Sep 17 00:00:00 2001 From: duyanghao <1294057873@qq.com> Date: Fri, 3 Apr 2020 10:51:22 +0800 Subject: [PATCH 1/2] add velero-volume-controller as an implemented choice of velero restic 3rd party controller Signed-off-by: duyanghao <1294057873@qq.com> --- site/docs/master/restic.md | 7 +++++++ site/docs/v1.3.1/restic.md | 7 +++++++ 2 files changed, 14 insertions(+) diff --git a/site/docs/master/restic.md b/site/docs/master/restic.md index b3c071b4d..c1623232b 100644 --- a/site/docs/master/restic.md +++ b/site/docs/master/restic.md @@ -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 hasn't provided a do-one-command or automatic way to backup all volume resources in the cluster without annotation. + +To solve this, [velero-volume-controller][10] helps to achieve this goal 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 \ No newline at end of file diff --git a/site/docs/v1.3.1/restic.md b/site/docs/v1.3.1/restic.md index b3c071b4d..c1623232b 100644 --- a/site/docs/v1.3.1/restic.md +++ b/site/docs/v1.3.1/restic.md @@ -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 hasn't provided a do-one-command or automatic way to backup all volume resources in the cluster without annotation. + +To solve this, [velero-volume-controller][10] helps to achieve this goal 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 \ No newline at end of file From a7ebca245313fcf96e58f8863ca1b657052ae27e Mon Sep 17 00:00:00 2001 From: duyanghao <1294057873@qq.com> Date: Tue, 7 Apr 2020 10:33:35 +0800 Subject: [PATCH 2/2] update docs Signed-off-by: duyanghao <1294057873@qq.com> --- site/docs/master/restic.md | 6 +++--- site/docs/v1.3.1/restic.md | 6 +++--- 2 files changed, 6 insertions(+), 6 deletions(-) diff --git a/site/docs/master/restic.md b/site/docs/master/restic.md index c1623232b..762933f57 100644 --- a/site/docs/master/restic.md +++ b/site/docs/master/restic.md @@ -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 @@ -420,9 +420,9 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch ### Add backup annotation -Velero hasn't provided a do-one-command or automatic way to backup all volume resources in the cluster without 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. -To solve this, [velero-volume-controller][10] helps to achieve this goal by adding backup annotation to pods with volumes automatically. +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 diff --git a/site/docs/v1.3.1/restic.md b/site/docs/v1.3.1/restic.md index c1623232b..762933f57 100644 --- a/site/docs/v1.3.1/restic.md +++ b/site/docs/v1.3.1/restic.md @@ -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 @@ -420,9 +420,9 @@ To solve this, a controller was written by Thomann Bits&Beats: [velero-pvc-watch ### Add backup annotation -Velero hasn't provided a do-one-command or automatic way to backup all volume resources in the cluster without 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. -To solve this, [velero-volume-controller][10] helps to achieve this goal by adding backup annotation to pods with volumes automatically. +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