tidb-backup: add restoreUsingExistingVolume option

pingcap · Feb 15, 2020 · b8498c6 · b8498c6
1 parent d43d3d6
commit b8498c6
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 1 deletion.
diff --git a/charts/tidb-backup/templates/backup-pvc.yaml b/charts/tidb-backup/templates/backup-pvc.yaml
@@ -1,4 +1,4 @@
-{{- if (or (eq .Values.mode "backup") (eq .Values.mode "scheduled-restore")) }}
+{{- if (or (eq .Values.mode "backup") (eq .Values.mode "scheduled-restore") (not .Values.restoreUsingExistingVolume)) }}
 kind: PersistentVolumeClaim
 apiVersion: v1
 metadata:

diff --git a/charts/tidb-backup/values.yaml b/charts/tidb-backup/values.yaml
@@ -80,6 +80,11 @@ restoreOptions: "-t 16"
 # When a GC happens, the current time minus this value is the safe point.
 tikvGCLifeTime: 720h
 
+# By default, restores are performed by binding to an existing volume containing backup data.
+# To restore from gcp, ceph, or s3, set this to false to create a new volume to load the backup into
+# This setting only affects the "restore" mode.
+restoreUsingExistingVolume: true
+
 # By default, the backup/restore uses PV to store/load backup data
 # You can choose to store/load backup data to/from gcp, ceph or s3 bucket by enabling the following corresponding section: