Migrating a Tomcat workload
This topic describes how to migrate Tomcat clusters to GKE with Migrate to Containers. Migrate to Containers helps accelerate the containerization of traditional workloads and their deployment into GKE and Anthos clusters.
To perform the migration, you will use a processing cluster you created with the steps in Installing Migrate to Containers.
When you use Migrate to Containers to migrate your Tomcat workloads, you can leverage Tomcat's features and architecture to:
- Automatically separate subsets of applications into individual containers.
- Retain your Tomcat application's existing keystores, truststores, and certificates from the source VM.
- Dynamically determine optimal memory allocation for JVM applications.
- Copy specific data volumes and data volume claims from your source VMs.
- A Linux VM based Apache Tomcat app server v8.5 and later.
- Determine your workload's fit for migration by using the fit assessment tool.
- Configure a Cloud cluster for migrating Linux VMs.
- Install Migrate to Containers.
The following Tomcat features are not supported:
Windows support for Tomcat migrations using Windows workloads.
Password extraction: Migrate to Containers does not extract passwords embedded in the Tomcat server configuration files. We recommend consuming these passwords from environment variables, provided by mounted secrets. For more information, see using secrets as environment variables
The steps to migrate with Migrate to Containers:
You start a migration by configuring a source that represents the source platform from which you are migrating. If you already have a source from a previous migration and the VMs you're migrating are from the same source, you can re-use it.
Create the migration plan that you then review and customize before executing the migration.
Edit the migration plan for your specific requirements before executing the migration.
Execute the migration to extract the container artifacts, which include the Dockerfile and other files necessary to build a container image.
Monitor the progress of a migration and inspect migration activity logs.
Use the generated artifacts to build a container that you can then deploy to a cluster.
The steps to deploy with Migrate to Containers:
Deploy your container to a testing or production cluster.
Use Cloud Logging or
kubectlto view container logs.