---
title: "Velero With Wasabi"
slug: "velero-with-wasabi"
updated: 2026-06-08T19:49:36Z
published: 2026-06-08T19:49:36Z
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wasabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Velero With Wasabi

[Velero](https://velero.io/) is open-source software used to backup [Kubernetes](https://kubernetes.io/) pod data and Wasabi may be used to store Velero backups. This article outlines the procedure for setting up Velero for use with Wasabi.

> The data restoration process is handled by your specific backup software application. As there are many potential variables that will affect your unique environment, Wasabi strongly recommends that you seek the guidance of your backup software's technical support resources in the event that you encounter difficulty or have application-specific inquiries.

## Requirements

- Active [Wasabi Cloud Storage Account](https://wasabi.com/sign-up).
- Access to the [Wasabi Console](https://console.wasabisys.com/) as the account root user.
- Wasabi bucket created to store your backups. Do not enable Object Lock or Versioning. See [Creating a Bucket](https://docs.wasabi.com/docs/working-with-buckets-and-objects#creating-a-bucket) for details on this procedure.
- This solution was tested with Velero version 1.18.0 running on Ubuntu Linux version 24.04.4 with Kubernetes version v1.32.
- Access to your Kubernetes server.

## Configuring Wasabi Console

1. Log in to the [Wasabi Console](https://console.wasabisys.com/) as the account root user.
2. Configure a policy for a “velero” user (that will be created below) using the following policy. See [Creating and Deleting a Policy](https://docs.wasabi.com/docs/creating-a-policy) for instructions on how to create a policy. We named the policy “VeleroPolicy” in our example. Change YOUR_BUCKET_NAME to your own bucket name.

```json
{
  "Version": "2012-10-17",
  "Statement": [
    {
      "Effect": "Allow",
      "Action": [
        "s3:GetObject",
        "s3:DeleteObject",
        "s3:PutObject",
        "s3:PutObjectTagging",
        "s3:AbortMultipartUpload",
        "s3:ListMultipartUploadParts"
      ],
      "Resource": "arn:aws:s3:::YOUR_BUCKET_NAME/*"
    },
    {
      "Effect": "Allow",
      "Action": "s3:ListBucket",
      "Resource": "arn:aws:s3:::YOUR_BUCKET_NAME"
    }
  ]
}
```
3. Create a “velero” user and attach the previously created policy to it. See [Creating a User](https://docs.wasabi.com/docs/creating-a-user-account-and-access-key#creating-a-user) for details.
  - Allow programatic-only access, not console access.
  - Do not require Multi-Factor Authentication (MFA).
  - It is not necessary to assign the user to a group.
  - Save the access and secret keys in a secure location.

## Configring Velero

These instructions are based on Velero running on the same server as Kubernetes.

1. Log in to your Kubernetes server.
2. Create a file with your Wasabi “velero” user’s access and secret keys as shown below. We named our file credentials-velero.

```plaintext
[wasabi]
aws_access_key_id=<YOUR_VELERO_USER_ACCESS_KEY>
aws_secret_access_key=<YOUR_VELERO_USER_SECRET_KEY>
```
3. If Velero is not installed, you may install Velero with the following commands. Replace YOUR_BUCKET_NAME with the name of your bucket, and replace the region and s3Url with the region and region’s URL that your bucket is located in.

> These configuration examples discuss the use of Wasabi's us-east-1 storage region. Use the region your bucket is located in. For a list of regions, see [Available Storage Regions](https://docs.wasabi.com/docs/en/where-is-my-data-stored-and-how-are-wasabis-storage-regions-secured?highlight=regions#available-storage-regions).

```bash
BUCKET=YOUR_BUCKET_NAME
velero install \
  --provider aws \
  --plugins velero/velero-plugin-for-aws:v1.13.0 \
  --bucket $BUCKET \
  --secret-file ./credentials-velero \
  --backup-location-config region=us-east-1,s3Url=https://s3.us-east-1.wasabisys.com \
  --use-node-agent \
  --default-volumes-to-fs-backup
```
4. If Velero is already installed, you may instead just create a Wasabi backup storage location. Replace YOUR_BUCKET_NAME with the name of your bucket, and replace the region and s3Url with the region and region’s URL that your bucket is located in. It is only required to add the plugin (first command) if it is not already installed.

> Ensure your Velero installation is configured with the following options so Velero will do filesystem backups for all volumes by default.
> 
> --use-node-agent
> 
> --default-volumes-to-fs-backup

```bash
velero plugin add velero/velero-plugin-for-aws:v1.13.0

kubectl create secret generic -n velero wasabi-credentials \
--from-file=wasabi=<PATH_TO_FILE>/credentials-velero

BUCKET=YOUR_BUCKET_NAME

velero backup-location create wasabi \
  --provider aws \
  --bucket $BUCKET \
  --credential=wasabi-credentials=wasabi \
  --config region=us-east-1,s3Url=https://s3.us-east-1.wasabisys.com
```

## Performing a Test Backup and Restore

For our example, we will create a test nginx pod for backup and restoral so as not to disturb other Kubernetes pods.

1. Create a test namespace of “backup-test-ns”.

```bash
kubectl create namespace backup-test-ns
```
2. Create a test configuration file by issuing the following command.

```bash
cat <<EOF > backup-test.yaml
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: backup-test-claim
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi
---
apiVersion: v1
kind: Pod
metadata:
  name: backup-test-pod
spec:
  volumes:
    - name: backup-test-storage
      persistentVolumeClaim:
        claimName: backup-test-claim
  containers:
    - name: backup-test-container
      image: nginx
      volumeMounts:
        - mountPath: "/usr/share/nginx/html"
          name: backup-test-storage
EOF
```
3. Create the pod.

```bash
kubectl apply -n backup-test-ns -f backup-test.yaml
```
4. Make a small change to identify the nginx instance prior to being backed up.

```bash
kubectl exec pod/backup-test-pod -n backup-test-ns \
-- sh -c "echo 'Velero backup test successful' \
> /usr/share/nginx/html/index.html"
```
5. Create a backup. You may omit the `--storage-location wasabi` if you installed Velero as part of this process which has Wasabi set as the default location.

```bash
velero backup create test-restore-backup \
--include-namespaces backup-test-ns \
--storage-location wasabi
```
6. Check the status of the backup. It should show the Phase as Completed in green once the backup is finished.

```bash
velero backup describe test-restore-backup
```

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-03-18_at_11_53_43 AM.png)
7. Delete the test namespace.

```bash
kubectl delete namespace backup-test-ns
```
8. Restore the backup.

```bash
velero restore create test-restore-verify --from-backup test-restore-backup
```
9. Issue the following commands to see if the restore was successful. The first command should show a STATUS of Running and the second command output should read “Velero backup test successful”.

```bash
kubectl get pods -n backup-test-ns

kubectl exec pod/backup-test-pod -n backup-test-ns \
-- sh -c "cat /usr/share/nginx/html/index.html"
```

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot_2026-03-18_at_4_33_06 PM.png)
10. Delete the test namespace.

```bash
kubectl delete namespace backup-test-ns
```

## Setting Up a Backup Schedule

1. Issue the following command to set up a schedule. In this example, we have the backup set to run every day at midnight. Adjust the Time-to-Live (TTL, when Velero will delete the backup) value to meet your organization’s policies. We have it set to 90 days, or 2160 hours. If you installed Velero as part of this procedure where Wasabi is set as the default storage location, omit the `--storage-location wasabi` portion of the command.

```bash
velero schedule create wasabi-backup --schedule="0 0 * * *" \
--storage-location wasabi --ttl 2160h
```
2. Log in to the [Wasabi Console](https://console.wasabisys.com/) and verify the backups are being stored in your bucket after the schedule has run once.

![](https://cdn.document360.io/bef0a1ea-7768-4d5a-b520-c4fe2f7fafad/Images/Documentation/Screenshot 2026-03-18 at 12.19.55 PM.png)