Kubernetes Backup via Velero

Introduction

This guide walks through the process of backing up a Kubernetes cluster using Restic with Velero. Velero is a command-line tool that backs up Kubernetes clusters and restores them in case of loss. Velero includes a command-line interface and server-side component that runs inside of your Kubernetes cluster.

Velero lets you:

  • Take backups of your cluster and restore them in case of loss.

  • Migrate cluster resources to other clusters.

  • Replicate your production cluster to development and testing clusters.

The Storj Velero plugin does not support volume snapshots for now.

Prerequisites

Instructions

Install Velero with Storj plugin

$ velero install --provider tardigrade \
    --plugins storjlabs/velero-plugin:latest \
    --bucket $BUCKET \
    --backup-location-config accessGrant=$ACCESS \
    --no-secret
$ velero install --provider tardigrade \
    --plugins storjlabs/velero-plugin:latest \
    --bucket $BUCKET \
    --backup-location-config accessGrant=$ACCESS \
    --no-secret

To generate an access grant ($ACCESS) for the configuration, follow the guide here: Sharing Your First Object.

Backup/Restore

Perform a backup:

$ velero backup create $BACKUP_NAME
$ velero backup create $BACKUP_NAME

Perform a restore:

$ velero restore create $RESTORE_NAME --from-backup $BACKUP_NAME
$ velero restore create $RESTORE_NAME --from-backup $BACKUP_NAME

Note: it's possible to overwrite the backup location or access grant by editing the backupstoragelocations.velero.io CR and restarting the Velero Pod on the cluster in case of any mistake with the configuration.

The complete Velero documentation is located here.

Multicloud Architecture for Disaster Prevention and Migration

Because Storj is a globally distributed hot object store, you can store and recover your Kubernetes volumes from anywhere in the world, instantly, without having to replicate data across regions. For DevOps managers, this can mean better resilience for your cluster, reduced global RTO (recovery time objective), cost-savings, and improved native security over centralized alternatives.

In the example below, we can see a Disaster Recovery scenario where we might need to migrate into a new cluster:

In this scenario, Cluster B is restored from the backup of A and reconstituting the Kubernetes volume in the cluster.

Github Source: Velero Plugin

Previous
Kerberos Vault
Next
Livepeer