We released Migrate to Containers 1.15.0. The use of migration sources based on Migrate to Virtual Machines v4 is no longer supported

## Announcement On May 22, 2023 we released Migrate to Containers 1.15.0. ## Deprecate The use of migration sources based on Migrate to Virtual Machines v4 is no longer supported. To migrate application components from VMs running on VMWare clusters, you can use Migrate to Virtual Machines v5 integration. For more information, see [Adding Migrate to Virtual Machines as a migration source](https://cloud.google.com/migrate/containers/docs/adding-a-migration-source#adding%5Fas%5Fa%5Fmigration%5Fsource). To migrate application components from AWS or Azure use Migrate to Virtual Machines v5 to migrate VMs to Compute Engine, and then use Migrate to Containers to perform a migration from the created Compute Engine instance. For more information, see the [Migrate to Virtual Machines version 5.0 documentation](https://cloud.google.com/migrate/virtual-machines/docs/5.0). ## Deprecate In-place processing on Anthos on AWS is no longer supported. You cannot install new versions of Migrate to Containers on Anthos on AWS clusters. To migrate application components of VMs on AWS, you can migrate VMs from AWS to Compute Engine using Migrate to Virtual Machines v5, and then use Migrate to Containers to perform a migration from the created Compute Engine instance. For more information, see the [Migrate to Virtual Machines version 5.0 documentation](https://cloud.google.com/migrate/virtual-machines/docs/5.0). ## Deprecate In-place processing on Anthos on VMware is no longer supported. You cannot install new versions of Migrate to Containers on Anthos on VMWare clusters. Instead, you can migrate application components to GKE or Anthos clusters on bare metal using Migrate to Virtual Machines v5 or the local VMWare source respectively. ## Deprecate The legacy Linux runtime is now deprecated. The generated migration plan now uses the enhanced Linux runtime by default. You can choose to use the legacy Linux runtime, which is planned to be supported until August 2023, by setting the value of the `v2kServiceManager` flag in the migration plan to false. To see how to convert existing migrations to the new Linux runtime, see [Upgrade container workloads for enhanced runtime](https://cloud.google.com/migrate/containers/docs/convert-runtime). If you have migrated applications using the legacy runtime, you can install the legacy runtime support using the following command: migctl setup install --runtime For more information, see [Before you begin deploying a Linux workload to a target cluster](https://cloud.google.com/migrate/containers/docs/deploying-to-target-cluster#before%5Fyou%5Fbegin). ## Fix Enhanced the Windows features filtering to only allow features supported by Windows Docker images to work.