From adaa58ae2c868439abd3c1fb1a1d64da4db184a4 Mon Sep 17 00:00:00 2001 From: Nir Soffer Date: Wed, 31 May 2023 01:33:20 +0300 Subject: [PATCH] Add velero configuration to `ramenctl config` Velero uses the same s3 bucket using the same s3 profile, but it needs a different secret stored at `veleroNamespaceSecretKeyRef`. The secret is created by `velero install`. Seems to be complete, but not tested with ramen yet. Signed-off-by: Nir Soffer --- ramenctl/ramenctl/resources/configmap.yaml | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/ramenctl/ramenctl/resources/configmap.yaml b/ramenctl/ramenctl/resources/configmap.yaml index a8274bbca2..ec4ded6ef6 100644 --- a/ramenctl/ramenctl/resources/configmap.yaml +++ b/ramenctl/ramenctl/resources/configmap.yaml @@ -30,6 +30,8 @@ data: catalogSourceName: ramen-catalog catalogSourceNamespaceName: ramen-system clusterServiceVersionName: ramen-dr-cluster-operator.v0.0.1 + kubeObjectProtection: + veleroNamespaceName: velero s3StoreProfiles: - s3ProfileName: minio-on-dr1 s3Bucket: bucket @@ -38,6 +40,9 @@ data: s3SecretRef: name: ramen-s3 namespace: ramen-system + veleroNamespaceSecretKeyRef: + key: cloud + name: cloud-credentials - s3ProfileName: minio-on-dr2 s3Bucket: bucket s3CompatibleEndpoint: $minio_url_dr2 @@ -45,3 +50,6 @@ data: s3SecretRef: name: ramen-s3 namespace: ramen-system + veleroNamespaceSecretKeyRef: + key: cloud + name: cloud-credentials