Use Velero with Kind without Minio

use_velero_with_kind.md

This quick Gist will show you how to get Velero up and running with Kind without using Minio. You might find this useful if you need a quick instance of Velero for testing or are just getting started with the tool but do not have access to AWS, Azure, or GCP.

Prereqs

• Docker
• Helm
• Velero (brew install velero, choco install velero, or build from source)

1. Create a new Kind cluster

   $: kind create cluster --name=test-cluster

2. Pull s3rver, a fake S3 server written in Node. (More info here. Bind it to the Docker network created by kind:

   $: docker run -d --net=kind --name=velero-backups triplew/s3rver

3. Create the YAML file shown below at /tmp/velero-values.yaml; include the lines that say NOT_NEEDED:

configuration:
  provider: aws
  backupStorageLocation:
    bucket: test-bucket
    config:
      region: fake-region
      s3Url: http://velero-backups:4568
      s3ForcePathStyle: true
initContainers:
  - name: aws
    image: velero/velero-plugin-for-aws:v1.1.0
    imagePullPolicy: IfNotPresent
    volumeMounts:
      - mountPath: /target
        name: plugins
credentials:
  secretContents:
    cloud: |
      [default]
      region = NOT_NEEDED
      aws_access_key_id = NOT_NEEDED
      aws_secret_access_key = NOT_NEEDED

4. Install the Helm repo for Velero, then install Velero

$: helm repo add vmware-tanzu/velero && helm install --values /tmp/velero-values.yaml velero vmware-tanzu/velero

5. Use Velero as desired.

$: velero backup create test-backup

Limitations

• You won't be able to fetch logs or download the backups, as these are not supported by s3rver.