Installing Velero

Velero is a client-server utility for backing up and restoring Kubernetes cluster resources.

1. Make sure that:

   • Either the worker node groups have at least 2 vCPUs available;
   • Or automatic scaling is enabled.

2. Make sure that you can connect to the cluster with kubectl.

3. Install OpenStack CLI if it is not already installed. Make sure that you can authorize in the cloud using it.

4. Create a Hotbox bucket to store backups in the Object Storage service.

5. Create an account in the Object Storage service.

   Save the account's key ID and secret to the s3_creds file:

   Copy
   [default]aws_access_key_id=<Access Key ID>aws_secret_access_key=<Secret Key>

6. Determine which version of Velero is compatible with the Kubernetes cluster version you want to install Velero in.

7. Download the correct version of the Velero client.

8. Determine the version of the AWS plugin that is compatible with Velero version.

9. Add the path to the client to the environment variable:

   • Path for Windows.
   • PATH for Linux/macOS.

10. Install the server part of Velero in the Kubernetes cluster. In the command, specify the name of the bucket created for Velero and the path to the s3_creds file with the account data:

    Linux/macOS

    Windows

    Copy
    velero install \--plugins \  velero/velero-plugin-for-aws:v<selected AWS plugin version>,registry.infra.mail.ru:5010/velero/velero-plugin-mcs:v1.2.2 \--provider aws \--bucket <Velero bucket name> \--secret-file <path to s3_creds file> \--use-volume-snapshots=false \--backup-location-config \  region=ru-msk,s3ForcePathStyle="true",s3Url=https://hb.bizmrg.com:443

    After the installation is complete, a message will be displayed:

    Copy
    Velero is installed! ⛵ Use 'kubectl logs deployment/velero -n velero' to view the status.

11. Create a Kubernetes secret so that the server part of Velero can authorize in the VK Cloud:

    Linux/macOS

    Windows

    Copy
    kubectl -n velero create secret generic openstack-cloud-credentials \  --from-literal OS_PROJECT_ID=$OS_PROJECT_ID \  --from-literal OS_REGION_NAME=$OS_REGION_NAME \  --from-literal OS_IDENTITY_API_VERSION=$OS_IDENTITY_API_VERSION \  --from-literal OS_PASSWORD=$OS_PASSWORD \  --from-literal OS_AUTH_URL=$OS_AUTH_URL \  --from-literal OS_USERNAME=$OS_USERNAME \  --from-literal OS_INTERFACE=$OS_INTERFACE \  --from-literal OS_FILE_OPERATION_TIMEOUT=$OS_FILE_OPERATION_TIMEOUT \  --from-literal OS_DOMAIN_NAME=$OS_USER_DOMAIN_NAME \  -o yaml

    Output should contain a similar information:

    Copy
    apiVersion: v1data:  OS_AUTH_URL: ...  OS_DOMAIN_NAME: ...  ...kind: Secretmetadata:  creationTimestamp: ...  name: openstack-cloud-credentials  namespace: velero  resourceVersion: ...  selfLink: ...  uid: ...type: Opaque

12. Patch the Velero deployment in the cluster. This is needed for:

    • limiting resource consumption by Velero plugins for AWS and VK Cloud;

    • specifying the secret with variables for authorization in VK Cloud.

    1. Create a file with the patch:

       velero-patch.yaml

    2. Apply the patch to the Velero deployment:

       Copy
       kubectl patch deployment velero -n velero --patch-file velero-patch.yaml

       The Velero deployment will be patched and restarted.

13. Create a default snapshot location by running the command:

    Copy
    velero snapshot-location create default --provider openstack --config region=ru-msk

1. Run the command to check the configured plugins:

   Copy
   velero plugin get

   The output of the command should contain the following plugins:

   Copy
   NAME                                        KIND...                                         ...velero.io/aws                               VolumeSnapshottervelero.io/openstack                         VolumeSnapshotter

2. Run the command to check the configured backup locations:

   Copy
   velero backup-location get

   A similar information should be displayed:

   Copy
   NAME      PROVIDER   BUCKET/PREFIX   PHASE       LAST VALIDATED                  ACCESS MODE   DEFAULTdefault   aws        ...             Available   ...                             ReadWrite     true

3. Run the command to check the configured snapshot locations:

   Copy
   velero snapshot-location get

   A similar information should be displayed:

   Copy
   NAME      PROVIDERdefault   openstack

Run the command:

Copy
velero uninstall