![]() |
VOOZH | about |
In this article, we will introduce you to Migrate for Anthos. Migrate for Anthos is a set of tools that inspects existing workloads running in virtual machines and automatically creates the needed container artifacts for modernization. Let us break down that last sentence into two parts and talk separately about where these virtual machines might be running and what types of artifacts Migrate for Anthos creates.
Migrate for Anthos can migrate both Windows and Linux applications. Windows applications can be running on a Google Compute Engine VM. In addition to Google Compute Engine, Linux applications can also be hosted on-prem with one of the following:
In Migrate for Anthos, where your VM currently resides is called the migration source. For this article, the source will be an application running in a VM on Compute Engine. The output from Migrate for Anthos is a comprehensive set of artifacts that you can use to deploy your newly containerized application. These artifacts include:
Once you have these artifacts, you can deploy the containerized version of your application to an Anthos cluster or to the various flavors of Google Kubernetes Engine, including GKE running on Google Cloud, on-prem, or on AWS.
There are several key benefits to migrating your workloads. They are discussed and listed below:
So now you have a general idea of what Migrate for Anthos does and why you might choose to use it, let's jump into an actual migration. Migrate for Anthos has three primary components-- the Discovery tool, which assesses how successful migration of a given application might be; the Processing Cluster, a Kubernetes cluster that is used to examine the source VM and create the migration plan, as well as execute the actual migration; and migctl, a command-line tool, like kubctl, for interacting with the processing cluster. Migctl is already installed in Cloud Shell.