Overview
- Migrate for Anthos (M4A)
- Transform VM-based workloads to containers running in Kubernetes Engine, optionally on GKE Enterprise
- Modernize legacy applications
- Fit assessment tool—determine which VMs are suitable for migration
- Console, API or CRD-based API
- Option to migrate to Autopilot clusters or Cloud Run
Considerations
- What about:
- VMs with multiple apps?
- Databases?
- Networking?
VMs with Multiple Apps
- Usually one process per pod in Kubernetes
- M4A doesn’t create separate images for each service within a VM
- Solution: ensure only one component is running when processing with M4A
- Re-run for each component
Databases
Networking
- Choose short service names
- Use ConfigMaps for service discovery
- Use network policies to restrict access to services
- e.g. Restrict which Pods can communicate with DB tier