that you can install velero you have a kind-cluster and minio running
In this repo there are the default user and password.
docker run -d --rm -p 9000:9000 --name minio \
-e "MINIO_ROOT_USER=AKIAIOSFODNN7EXAMPLE" \
-e "MINIO_ROOT_PASSWORD=wJalrXUtnFEMI/K7MDENG/bPxRfiCYEXAMPLEKEY" \
-v ${HOME}/dev/velero/data:/data \
minio/minio server /datato get access on a mac ⇒ systempreference - network - IP <ip-address>:9000 or localhost:9000
add a new bucket ⇒ acme-develpoment
$ kind create cluster --name velero --image kindest/node:v1.19.1
````
=== Install Velero
1. with brew
```bash
brew install velero-
in a container
docker run -it --rm -v ${HOME}:/root/ -v ${PWD}:/work -w /work --net host alpine sh
# install curl & kubectl
in the container
```bash
export KUBE_VERSION=v1.19.1
apk add --no-cache curl vim
#curl -LO https://storage.googleapis.com/kubernetes-release/release/`curl -s https://storage.googleapis.com/kubernetes-release/release/stable.txt`/bin/linux/amd64/kubectl
curl -LO https://storage.googleapis.com/kubernetes-release/release/${KUBE_VERSION}/bin/linux/amd64/kubectl
chmod +x ./kubectl
mv ./kubectl /usr/local/bin/kubectlin the container
export VELERO_VERSION=v1.5.3
# version see https://github.com/vmware-tanzu/velero/releases/
curl -L -o /tmp/velero.tar.gz https://github.com/vmware-tanzu/velero/releases/download/${VELERO_VERSION}/velero-${VELERO_VERSION}-linux-amd64.tar.gz
tar -C /tmp -xvf /tmp/velero.tar.gz
mv /tmp/velero-${VELERO_VERSION}-linux-amd64/velero /usr/local/bin/velero
chmod +x /usr/local/bin/veleroPlugin: AWS <br> https://github.com/vmware-tanzu/velero-plugin-for-aws
generate a security file
echo '[default]' > ~/dev/velero/creds/credentials-velero-minio
echo 'aws_access_key_id = minioadmin' >> ~/dev/velero/creds/credentials-velero-minio
echo 'aws_secret_access_key = minioadmin' >> ~/dev/velero/creds/credentials-velero-miniovelero install \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.1.0 \
--use-volume-snapshots=false \
--secret-file ~/dev/velero/creds/credentials-velero-minio \
--bucket acme-development \
--backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://*<ip-address>:9000*change the IP to your IP-address from the minio container.
# velero backup create default-namespace-backup --include-namespaces default
# velero backup describe default-namespace-backup
# velero backup logs default-namespace-backupUninstall Verlero
in the container
velero install -o yaml --dry-run \
--provider aws \
--plugins velero/velero-plugin-for-aws:v1.1.0 \
--use-volume-snapshots=false \
--secret-file ~/dev/velero/creds/credentials-velero-minio \
--bucket acme-development \
--backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://*<ip-address>:9000 | kubectl delete -f -
````
delete container +
exit out of the container with the --rm the container is deleted.
Delete the kind cluster
```bash
kind delete cluster velerotime="2021-01-06T11:51:17Z" level=info msg="No backup locations were ready to be verified" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:120" time="2021-01-06T11:51:17Z" level=error msg="Current backup storage locations available/unavailable/unknown: 0/0/1)" controller=backupstoragelocation logSource="pkg/controller/backupstoragelocation_controller.go:154" I0106 11:51:18.685344 1 request.go:621] Throttling request took 1.048411596s, request: GET:https://10.0.0.1:443/apis/apiregistration.k8s.io/v1beta1?timeout=32s
❯ kubectl get secrets -n velero cloud-credentials -o jsonpath="{.data.cloud}" | base64 -d
[default]
aws_access_key_id = minioadmin
aws_secret_access_key = minioadmin
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent