Overview

Caution

At the moment, a Storage resource can only be used by a single Backup resource. This means you will need to create a separate Storage resource for each Backup resource. We are working on adding support for sharing a Storage resource between multiple Backup resources. Please check the roadmap for more information.

A Storage resource is used to define where the data of a Backup should be stored, or where a Restore should read the data from.

Usage

Storage resources can be managed using the kubectl command line tool, and are available by the name storage or storages.

$ kubectl get storages
NAME            STATUS   AGE   LOCATION
s3-storage      Ready    1s    s3://kannika-aws-s3/backups
gcs-storage     Ready    1s    gs://kannika-gcs/backups
azure-storage   Ready    1s    https://kannika-azure.blob.core.windows.net/backups
volume-storage  Ready    1s

Supported Storage

Currently, the following storage systems are supported:

• Kubernetes Volume (since 0.5.0)
• AWS S3 (since 0.6.0)
• Azure Blob Storage (since 0.6.0)
• Google Cloud Storage

Caution

When using cloud storage (GCS, S3, Azure Blob Storage), make sure no retention policy is defined on the target bucket or container as files disappearing might interfere with Armory’s own book keeping.

If old data must be periodically deleted, a retention policy can be configured directly on a Backup. Check out the relevant documentation.

Storage Class

It is also possible to configure a custom StorageClass that can be used in combination with Volume Storage. This allows you to offload your data to any storage provider that is supported by Kubernetes.

Please check the Storage Class section for more information.