VMware Velero Demos and Deep Dives, 24 Jun 2019

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: How to migrate applications between Kubernetes providers using Velero

Description

How do you migrate an application running on Kubernetes between providers?
In this demo, we'll show how to move an application from AWS to GKE.

Want more info about the open source project Velero?
Head over to https://velero.io.

A

A

Showed you how we could migrate applications from one AWS cluster to another, using Valero's built-in support for cloud provider snapshots in this kids EBS snapshots. So let's move on to the second example, where I'd actually like to migrate this application out of AWS and into a cluster running on gke on Google's kubernetes engine. Now we can't use EBS snapshots to do this migration because Google's cloud doesn't understand anything about EBS snapshots and so Valero has a generic mechanism for backing up volume.

A

Contents called rustic rustic is an open source tool for doing file level backups, and so what I'd actually like to do now is take a backup from cluster to using rustic to backup the contents of those volumes.

A

So I'm gonna clear my screen here so the first thing I need to do is to tell Valero to use rustic to backup the volumes and the way that that's is done is by annotating the pods that have those volumes that you want to backup and I have these commands saved in my buffer because they are a little bit long.

A

So first I'll annotate the WordPress, my sequel, pod and then I'll annotate, the WordPress pod, and this is telling Valero that next time it runs, it should use rustic backup these volumes rather than taking EPS snapshots.

A

So what I'll do now is I'll staple arrow back up, create I'll call this backup, WP, rustic and I'd like to again include the default namespace and I'll use that Dutch wave flag, so Valero again is is getting all those API resources that exist, but rather than taking EBS snapshots of the persistent volumes it finds, it will be using rustic to backup the contents of those volumes. So I'll give this a few more seconds and it should complete great. So now, if I run the Bolero backup this command.

A

4Wq rustic and I pass details. What we see at the bottom is rather than having information about EBS snapshots. We have a section about rustic backups and we see those two volumes that we ask to be backed up are included there. So that's great I'm gonna! Stop my port forwarding command here and I'm gonna go ahead and delete again. The deployment the service and the persistent volume claims from this cluster and I'll switch back to the browser and show that we no longer have a connection there.

A

All right, so that deletion is complete. So now I'll switch over to my third terminal window here, and you can see that this is a cluster that's running in gke, so an entirely different provider.

A

Now, if I look at the backup locations that are configured here again, we see two backup locations and the first one is called AWS, and it's pointed to that velaro backups bucket, which is where all backups that were created in cluster two we're going and so because that's configured I should be able to see the backup that I just created if I run velaro backup get so we see WP rustic. So what I'd like to do now is just do a restore from that backup.

A

So again, we'll save Valero restore create from backup, WP rustic and we'll wait for this to complete as well, and so now the Valero instance, that's running in cluster 3 here running in gke, is going out to the s3 bucket pulling that backup down, and it's additionally pulling down the rustic backups of the volumes that we backed up from cluster 2 and because the rustic backup is in a generic cloud provider, agnostic format that data can be restored into new persistent volumes in gke.

A

So this should take a few more seconds to.

A

Great, so the restore is completed now and so just take a quick look and see if our deployments have appeared. We have both of our deployments and if we look for persistent volume, claims we'll see those as well and finally I'll look and see if our pods are up and running. So we have two running pods now in our gke cluster, so I'll set up the port forward and command one more time from this cluster great and so now, if I switch back to my browser and refresh this page, Steve's awesome blog comes back up.

A

So this is now being served from GK Guinea and if I scroll down we'll see my blog post hello world that was written hello from cluster 1, that's up and running now in G, ke and just now, I showed you how you could migrate an application running in a cluster on AWS into a cluster running on gke using boleros rustic integration. So that concludes the demo and thanks a lot.