From 58f5b7816292853fcff3f2b6a32341da06dbcfa8 Mon Sep 17 00:00:00 2001 From: Mikael Frykholm Date: Fri, 11 Apr 2025 14:23:58 +0200 Subject: [PATCH] Add how to export the config. --- README.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/README.md b/README.md index 9edb81b..f2fd433 100644 --- a/README.md +++ b/README.md @@ -120,11 +120,15 @@ Save into a file called credentials-velero to be used during the install: aws_access_key_id=123123123123123123123123123123 aws_secret_access_key=12312312312312312312312213123 +Export the kubectl config file for velero to use: + + microk8s config > ~/.kube/config velero install --features=EnableCSI --use-node-agent --provider aws --plugins velero/velero-plugin-for-aws:v1.2.1 --bucket velero --secret-file ./credentials-velero --use-volume-snapshots=true --backup-location-config region=sto3,s3ForcePathStyle="true",s3Url=https://s3.sto3.safedc.net --snapshot-location-config region=sto3 --wait velero schedule create prod-schedule --schedule="0 3 * * *" --snapshot-move-data=true velero backup create rut-prod --snapshot-move-data --default-volumes-to-fs-backup=false --from-schedule prod-schedule ### Kubernetes logs and instrospection + vi logging.yaml #Change destination to prod monitoring server scp logging.yaml internal-sto4-test-k8sc-0.rut.sunet.se: ssh internal-sto4-test-k8sc-0.rut.sunet.se