Heptio Velero

Set Up our Environment

Let's pull down the Heptio Velero GitHub repo to help us get started: git clone https://github.com/heptio/velero

Let's download and install the Velero client: curl -LO https://github.com/heptio/velero/releases/download/v1.1.0/velero-v1.1.0-linux-amd64.tar.gz

tar -C /usr/local/bin -xzvf velero-v1.1.0-linux-amd64.tar.gz

Add velero directory to PATH export PATH=$PATH:/usr/local/bin/velero-v1.1.0-linux-amd64/

Create a Velero-specific credentials file (credentials-velero) in your local directory:

echo "[default]
aws_access_key_id = minio
aws_secret_access_key = minio123" > credentials-velero

Start the server and the local storage service:

kubectl apply -f velero/examples/minio/00-minio-deployment.yaml

velero install \ --provider aws \ --bucket velero \ --secret-file ./credentials-velero \ --use-volume-snapshots=false \ --backup-location-config region=minio,s3ForcePathStyle="true",s3Url=http://minio.velero.svc:9000

This example assumes that it is running within a local cluster without a volume provider capable of snapshots, so no VolumeSnapshotLocation is created (--use-volume-snapshots=false).

Deploy an example nginx application: kubectl apply -f velero/examples/nginx-app/base.yaml

Check to see that both Velero and nginx deployments have been successfully created:

kubectl get deployments -l component=velero --namespace=velero

kubectl get deployments --namespace=nginx-example

Back Up Our Resources

Let's backup any resource with labels "app=nginx": velero backup create nginx-backup --selector app=nginx

Verify if the backup has completed velero backup describe nginx-backup

Now, let's simulate a disaster: kubectl delete namespace nginx-example

Check that the nginx service and deployment are gone:

kubectl get deployments --namespace=nginx-example

kubectl get services --namespace=nginx-example

kubectl get namespace/nginx-example

You should get no results.

NOTE: You might need to wait for a few minutes for the namespace to be fully cleaned up.

Restore Our Resources

Run: velero restore create --from-backup nginx-backup

Run: velero restore get

NOTE: The restore can take a few moments to finish. During this time, the STATUS column reads InProgress.

After a successful restore, the STATUS column is Completed, and WARNINGS and ERRORS are 0. All objects in the nginx-example namespace should be just as they were before you deleted them.

If there are errors or warnings, you can look at them in detail:

velero restore describe <RESTORE_NAME>

You can verify that the nginx resources are available again:

kubectl get services --namespace=nginx-example

kubectl get namespace/nginx-example

cd <directory>	Change directory
ls	List directory
echo 'contents' > <file>	Write contents to a file
cat <file>	Output contents of file

i	In Command Mode	Change into Insert Mode, you can now insert and edit text in the file
esc	In Insert Mode	Change into Command Mode, you can now execute commands
:wq	In Command Mode	Save and Exit

Welcome!

Congratulations!

You've completed the scenario!

Scenario Rating

Steps

Heptio Velero

Set Up our Environment

Back Up Our Resources

Restore Our Resources

Welcome!

Heptio Velero

Congratulations!

You've completed the scenario!

Scenario Rating

Steps

Heptio Velero

Set Up our Environment

Back Up Our Resources

Restore Our Resources

Help

Vim

Welcome! Connect to start

...or sign up using your email

Sign up using your email

You’ll love Katacoda

Guided Path

Learn By Doing

Stay up-to-date

Welcome back! Connect to start

...or log in using your email

Log in using your email

You’ll love Katacoda

Guided Path

Learn By Doing

Stay up-to-date

Welcome! Enter your email address to connect

😺

Have some feedback for us? Please tell us what's happening so we can improve Katacoda.

Creating Katacoda Scenarios

Debugging Scenarios

Tips

Debug Information