Back compat for schedules.

A touch less graceful than I'd like but it does work.

Signed-off-by: W. Kavanaugh Latiolais <[email protected]>

Author: kav

charts/velero/ci/test-values-back-compat.yaml

@@ -19,6 +19,13 @@ serviceAccount:
   server:
     name: velero
 
+schedules:
+  mybackup:
+    schedule: "0 0 * * *"
+    template:
+      ttl: "240h"
+      includedNamespaces:
+        - foo
 # Whether or not to clean up CustomResourceDefintions when deleting a release.
 # Cleaning up CRDs will delete the BackupStorageLocation and VolumeSnapshotLocation instances, which would have to be reconfigured.
 # Backup data in object storage will _not_ be deleted, however Backup instances in the Kubernetes API will.

charts/velero/ci/test-values.yaml

@@ -18,6 +18,13 @@ serviceAccount:
   server:
     name: velero
 
+schedules:
+  - name: mybackup
+    schedule: "0 0 * * *"
+    template:
+      ttl: "240h"
+      includedNamespaces:
+        - foo
 # Whether or not to clean up CustomResourceDefintions when deleting a release.
 # Cleaning up CRDs will delete the BackupStorageLocation and VolumeSnapshotLocation instances, which would have to be reconfigured.
 # Backup data in object storage will _not_ be deleted, however Backup instances in the Kubernetes API will.

charts/velero/tests/__snapshot__/back-compat-snapshot_test.yaml.snap

@@ -164,3 +164,22 @@ manifest should match snapshot:
         bucket: velero
         region: us-west-1
       provider: aws
+  5: |
+    apiVersion: velero.io/v1
+    kind: Schedule
+    metadata:
+      annotations:
+        helm.sh/hook: post-install,post-upgrade
+        helm.sh/hook-delete-policy: before-hook-creation
+      labels:
+        app.kubernetes.io/instance: RELEASE-NAME
+        app.kubernetes.io/managed-by: Tiller
+        app.kubernetes.io/name: velero
+        helm.sh/chart: velero-2.14.0
+      name: RELEASE-NAME-velero-mybackup
+    spec:
+      schedule: 0 0 * * *
+      template:
+        includedNamespaces:
+        - foo
+        ttl: 240h

charts/velero/tests/__snapshot__/snapshot__test.yaml.snap

@@ -164,3 +164,22 @@ manifest should match snapshot:
         bucket: velero
         region: us-west-1
       provider: aws
+  5: |
+    apiVersion: velero.io/v1
+    kind: Schedule
+    metadata:
+      annotations:
+        helm.sh/hook: post-install,post-upgrade
+        helm.sh/hook-delete-policy: before-hook-creation
+      labels:
+        app.kubernetes.io/instance: RELEASE-NAME
+        app.kubernetes.io/managed-by: Tiller
+        app.kubernetes.io/name: velero
+        helm.sh/chart: velero-2.14.0
+      name: RELEASE-NAME-velero-mybackup
+    spec:
+      schedule: 0 0 * * *
+      template:
+        includedNamespaces:
+        - foo
+        ttl: 240h

charts/velero/tests/back-compat-snapshot_test.yaml

@@ -3,6 +3,7 @@ templates:
   - backupstoragelocation.yaml
   - restic-daemonset.yaml
   - volumesnapshotlocation.yaml
+  - schedule.yaml
 tests:
   - it: manifest should match snapshot
     values:

charts/velero/tests/snapshot__test.yaml

@@ -3,6 +3,7 @@ templates:
   - backupstoragelocation.yaml
   - restic-daemonset.yaml
   - volumesnapshotlocation.yaml
+  - schedule.yaml
 tests:
   - it: manifest should match snapshot
     values:

charts/velero/values.yaml

@@ -262,13 +262,13 @@ restic:
 # Backup schedules to create.
 # Eg:
 # schedules:
-#     name: mybackup
+#   - name: mybackup
 #     schedule: "0 0 * * *"
 #     template:
 #       ttl: "240h"
 #       includedNamespaces:
 #        - foo
-schedules: []
+# schedules: []
 
 scheduleLabels: {}
 
@@ -287,7 +287,7 @@ configMaps: {}
 ## End of additional Velero resource settings.
 ##
 
-# Depricated configuration key
+# Depricated
 configuration:
   backupStorageLocation: {}
   volumeSnapshotLocation: {}