Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS

You can migrate from Automation Suite deployed on a Linux machine to Automation Suite on EKS/AKS. To do that, you must move your data from one Automation Suite flavor to another using uipathctl.

One of the advantages of this migration process is that you can attempt to perform it multiple times with no impact on your existing cluster.

Important:

You can only migrate to a new installation of Automation on EKS/AKS. Migrating to an existing installation of Automation on EKS/AKS is currently not supported.

To migrate from Automation Suite on Linux to Automation Suite on EKS/AKS, take the following steps:

#	Migration step
1.	Mandatory. Download uipathctl. For download instructions, see uipathctl.
2.	Mandatory. Download versions.json. For download instructions, see versions.json.
3.	Prepare the docker images for both source and target cluster. Optional. If your deployment is offline or if you use a private OCI registry, make sure the required images are available.
4.	Prepare the target cluster: Create the input.json file. Run the prerequisites check.
5.	Run the migration and move the data. The migration executes pods on both the source and target clusters. The external object storage configured for the source cluster, specifically the Platform bucket, is used as an intermediate migration storage location. Source cluster: general-migration-* pods are responsible for exporting Kubernetes objects from the source cluster into the target cluster. volume-migration-* pods are responsible for copying PVC data into the intermediate external storage. Target cluster: inbound-pvc-migration-* pods are responsible for creating PVCs in the target cluster and copying the source data into them.
6.	Run the installation of Automation Suite on AKS or EKS.

For detailed migration instructions, see the Automation Suite on EKS/AKS Installation Guide.