Migrate to Containers includes Custom Resource Definitions (CRDs) that enable you to easily create and manage migrations using an API automation solution or code. For example, you can use these CRDs to build your own automated tools.
Steps to using the CRDs
The sequence of steps that you use to perform a migration by using the CRDs is similar
to the process you use with
migctl and the Google Cloud console. The steps in this process are:
Apply a SourceProvider CRD that represents the source platform from which you are migrating.
Apply the SourceProvider CRD for either:
Apply the Migration CRD for either:
These CRDs contain the details of the migration plan. Review and update these generated CRDs as necessary before executing the migration:
The GenerateArtifactsTask CRD or the WindowsGenerateArtifactsTask CRD reference the Migration CRD used to generate the migration resources.
Apply the CRD for either:
Deploy the migrated workload for either: