Awesome

Kubernetes Fury Disaster Recovery (DR) implements backups and disaster recovery for the Kubernetes Fury Distribution (KFD) using Velero.

If you are new to KFD please refer to the official documentation on how to get started with KFD.

Overview

Kubernetes Fury DR module is based on Velero and Velero Node Agent.

Velero allows you to:

• backup your cluster
• restore your cluster in case of problems
• migrate cluster resources to other clusters
• replicate your production environment to development and testing environment.

Together with Velero, Velero Node Agent allows you to:

• backup Kubernetes volumes
• restore Kubernetes volumes

And by using the snapshot-controller, the support for CSI Snapshot Data Movement can be enabled, which allows you to:

• backup the volume data to a pre-defined backup storage
• have consistent backups of your data

The module contains also velero plugins to natively integrate with Velero with different cloud providers and use cloud provider's volumes as the storage backend.

Packages

Kubernetes Fury DR provides the following packages:

The velero package contains the following additional components:

Integration with cloud providers

Use the following Velero Plugins to integrate Velero with cloud providers:

Deploy the necessary infrastructure to persist the backups natively in cloud providers volumes, using the following terraform modules:

Compatibility

Check the compatibility matrix for additional information about previous releases of the modules.

Usage

Kubernetes Fury DR deployment depends on the environment.

Prerequisites

Velero on AWS

Velero on AWS is based on the AWS Velero Plugin.

It requires the secret cloud-credentials in the kube-system namespace containing a service account with appropriate credentials. As an alternative, the module supports authentication via IAM Roles.

To deploy Velero on AWS:

1. List the packages you want to deploy and their version in a Furyfile.yml

bases:
  - name: dr/velero/velero-base
    version: "v3.0.0"
  - name: dr/velero/velero-aws
    version: "v3.0.0"
  - name: dr/velero/velero-node-agent
    version: "v3.0.0"
  - name: dr/velero/velero-schedules
    version: "v3.0.0"

modules:
  - name: dr/aws-velero
    version: "v3.0.0"

See furyctl documentation for additional details about Furyfile.yml format.

2. Execute furyctl legacy vendor -H to download the packages

3. Inspect the downloaded packages under ./vendor/katalog/velero.

4. Deploy the necessary infrastructure via terraform using the aws-velero terraform module:

module "velero" {
  source             = "path/to/vendor/modules/aws-velero"
  backup_bucket_name = "my-cluster-velero"
  project            = "sighup-staging"
}

More information on modules inputs can be found in the aws-velero module documentation

Here you can find an example designed to create all necessary cloud resources for Velero on AWS.

5. Define a kustomization.yaml that includes the downloaded resources.

resources:
  - ./vendor/katalog/dr/velero/velero-aws
  - ./vendor/katalog/dr/velero/velero-node-agent
  - ./vendor/katalog/dr/velero/velero-schedules

6. To deploy the packages to your cluster, execute:

kustomize build . | kubectl apply -f -

Velero on GCP

Velero on GCP is based on the Velero GCP Plugin.

It requires the secret cloud-credentials in the kube-system namespace containing a service account with appropriate credentials. As an alternative, the module supports workload identity.

Check the required Velero GCP plugin permissions here

To deploy Velero on GCP:

1. List the packages you want to deploy and their version in a Furyfile.yml

bases:
  - name: dr/velero/velero-base
    version: "v3.0.0"
  - name: dr/velero/velero-gcp
    version: "v3.0.0"
  - name: dr/velero/velero-node-agent
    version: "v3.0.0"
  - name: dr/velero/velero-schedules
    version: "v3.0.0"

modules:
  - name: dr/gcp-velero
    version: "v3.0.0"

See furyctl documentation for additional details about Furyfile.yml format.

2. Execute furyctl legacy vendor -H to download the packages

3. Inspect the downloaded packages under ./vendor/katalog/velero.

4. Deploy the necessary infrastructure via terraform using the gcp-velero terraform module:

module "velero" {
  source             = "path/to/vendor/modules/gcp-velero"
  backup_bucket_name = "my-cluster-velero"
  project            = "sighup-staging"
}

More information on modules inputs can be found in the gcp-velero module documentation

Here you can find an example designed to create all necessary cloud resources for Velero on GCP.

5. Define a kustomization.yaml that includes the downloaded resources.

resources:
  - ./vendor/katalog/dr/velero/velero-gcp
  - ./vendor/katalog/dr/velero/velero-node-agent
  - ./vendor/katalog/dr/velero/velero-schedules

6. To deploy the packages to your cluster, execute:

kustomize build . | kubectl apply -f -

Velero on Azure

Velero on Azure is based on the Azure Velero Plugin.

Requires the cloud-credentials secret config in the kube-system namespace.

To deploy Velero on Azure:

1. List the packages you want to deploy and their version in a Furyfile.yml

bases:
  - name: dr/velero/velero-base
    version: "v3.0.0"
  - name: dr/velero/velero-azure
    version: "v3.0.0"
  - name: dr/velero/velero-node-agent
    version: "v3.0.0"
  - name: dr/velero/velero-schedules
    version: "v3.0.0"

modules:
  - name: dr/azure-velero
    version: "v3.0.0"

See furyctl documentation for additional details about Furyfile.yml format.

2. Execute furyctl legacy vendor -H to download the packages

3. Inspect the downloaded packages under ./vendor/katalog/velero.

4. Deploy the necessary infrastructure via terraform using the azure-velero terraform module:

module "velero" {
  source             = "path/to/vendor/modules/azure-velero"
  backup_bucket_name = "my-cluster-velero"
  project            = "sighup-staging"
}

More information on modules inputs can be found in the azure-velero module documentation

Here you can find an example designed to create all necessary cloud resources for Velero on Azure.

5. Define a kustomization.yaml that includes the downloaded resources.

resources:
  - ./vendor/katalog/dr/velero/velero-azure
  - ./vendor/katalog/dr/velero/velero-node-agent
  - ./vendor/katalog/dr/velero/velero-schedules

6. To deploy the packages to your cluster, execute:

kustomize build . | kubectl apply -f -

Velero on-premises

velero-on-prem deploys a MinIO in-cluster instance as an object storage backend for Velero.

Please note that the MinIO server is running in the same cluster that is being backed up.

To deploy velero on-prem:

1. List the packages you want to deploy and their version in a Furyfile.yml

bases:
  - name: dr/velero/velero-base
    version: "v3.0.0"
  - name: dr/velero/velero-on-prem
    version: "v3.0.0"
  - name: dr/velero/velero-node-agent
    version: "v3.0.0"
  - name: dr/velero/velero-schedules
    version: "v3.0.0"

See furyctl documentation for additional details about Furyfile.yml format.

2. Execute furyctl legacy vendor -H to download the packages

3. Inspect the downloaded packages under ./vendor/katalog/velero.

4. Define a kustomization.yaml that includes the downloaded resources.

resources:
  - ./vendor/katalog/dr/velero/velero-on-prem
  - ./vendor/katalog/dr/velero/velero-node-agent
  - ./vendor/katalog/dr/velero/velero-schedules

5. To deploy the packages to your cluster, execute:

kustomize build . | kubectl apply -f -

Contributing

Before contributing, please read first the Contributing Guidelines.

Reporting Issues

In case you experience any problem with the module, please open a new issue.

License

This module is open-source and it's released under the following LICENSE