Migrating workloads across container clusters with different processor architectures
Techniques for migrating a workload between two container clusters (i.e., source and destination container clusters) that use different processor architectures are provided. In one set of embodiments, these techniques involve implementing a migration container cluster that (1) creates a backup of the workload from the source container cluster, where the backup includes metadata regarding one or more objects or resources of the workload, and (2) restores the backup on the destination container cluster, where the restoring causes a worker node of the destination container cluster to automatically retrieve, from an image repository, a container image for the workload that is specific to the second processor architecture and deploy the container image as a running container on the worker node.
1 . A method comprising:
receiving, by a migration container cluster, a request to migrate a workload from a source container cluster to a destination container cluster, wherein the source container cluster uses a first processor architecture and wherein the destination container cluster uses a second processor architecture different from the first processor architecture; and
creating, by the migration container cluster in response to the request, a backup of the workload from the source container cluster, the backup including metadata regarding one or more objects or resources of the workload; and
restoring, by the migration container cluster, the backup of the workload on the destination container cluster, wherein the restoring causes a worker node of the destination container cluster to automatically:
retrieve, from an image repository, a container image for the workload that is specific to the second processor architecture; and
deploy the container image as a running container on the worker node.
2 . The method of claim 1 wherein the request comprises a migration specification that includes access credentials for the source container cluster, access credentials for the destination container cluster, and a list of the one or more objects or resources.
3 . The method of claim 1 wherein the worker node retrieves the container image specific to the second processor architecture based on a node specification associated with the worker node that identifies the second processor architecture.
4 . The method of claim 1 wherein the source container cluster and the destination container cluster reside on different cloud infrastructures.
5 . The method of claim 1 wherein the migration container cluster is automatically decommissioned once the backup has been restored on the destination container cluster.
6 . The method of claim 1 wherein the backup is stored in an intermediary storage location separate from the migration container cluster prior to being restored.
7 . The method of claim 1 wherein the migration container cluster, the source container cluster, and the destination container cluster are Kubernetes clusters.
8 . A non-transitory computer readable storage medium having stored thereon program code executable by a migration container cluster, the program code embodying a method comprising:
receiving a request to migrate a workload from a source container cluster to a destination container cluster, wherein the source container cluster uses a first processor architecture and wherein the destination container cluster uses a second processor architecture different from the first processor architecture; and
creating, in response to the request, a backup of the workload from the source container cluster, the backup including metadata regarding one or more objects or resources of the workload; and
restoring the backup of the workload on the destination container cluster, wherein the restoring causes a worker node of the destination container cluster to automatically:
retrieve, from an image repository, a container image for the workload that is specific to the second processor architecture; and
deploy the container image as a running container on the worker node.
9 . The non-transitory computer readable storage medium of claim 8 wherein the request comprises a migration specification that includes access credentials for the source container cluster, access credentials for the destination container cluster, and a list of the one or more objects or resources.
10 . The non-transitory computer readable storage medium of claim 8 wherein the worker node retrieves the container image specific to the second processor architecture based on a node specification associated with the worker node that identifies the second processor architecture.
11 . The non-transitory computer readable storage medium of claim 8 wherein the source container cluster and the destination container cluster reside on different cloud infrastructures.
12 . The non-transitory computer readable storage medium of claim 8 wherein the migration container cluster is automatically decommissioned once the backup has been restored on the destination container cluster.
13 . The non-transitory computer readable storage medium of claim 8 wherein the backup is stored in an intermediary storage location separate from the migration container cluster prior to being restored.
14 . The non-transitory computer readable storage medium of claim 8 wherein the migration container cluster, the source container cluster, and the destination container cluster are Kubernetes clusters.
15 . A migration container cluster comprising:
a processor; and
a non-transitory computer readable medium having stored thereon program code that causes the processor to
receive a request to migrate a workload from a source container cluster to a destination container cluster, wherein the source container cluster uses a first processor architecture and wherein the destination container cluster uses a second processor architecture different from the first processor architecture; and
create, in response to the request, a backup of the workload from the source container cluster, the backup including metadata regarding one or more objects or resources of the workload; and
restore the backup of the workload on the destination container cluster,
wherein the restoring causes a worker node of the destination container cluster to automatically:
retrieve, from an image repository, a container image for the workload that is specific to the second processor architecture; and
deploy the container image as a running container on the worker node.
16 . The migration container cluster of claim 15 wherein the request comprises a migration specification that includes access credentials for the source container cluster, access credentials for the destination container cluster, and a list of the one or more objects or resources.
17 . The migration container cluster of claim 15 wherein the worker node retrieves the container image specific to the second processor architecture based on a node specification associated with the worker node that identifies the second processor architecture.
18 . The migration container cluster of claim 15 wherein the source container cluster and the destination container cluster reside on different cloud infrastructures.
19 . The migration container cluster of claim 15 wherein the migration container cluster is automatically decommissioned once the backup has been restored on the destination container cluster.
20 . The migration container cluster of claim 15 wherein the backup is stored in an intermediary storage location separate from the migration container cluster prior to being restored.
21 . The migration container cluster of claim 15 wherein the migration container cluster, the source container cluster, and the destination container cluster are Kubernetes clusters.