How can I migrate a AKS cluster to another region?

Question

How can I migrate a AKS cluster to another region?

Ronyedson 20

I have this quite large AKS instance and would like to move it to the eastus region so that it would be in the same region as the rest of my infrastructure. What are my options on this? I recognize that was my mistake creating it in the wrong region but the cluster rapidly grew and now requesting quotas and creating and configuring the cluster from zero again would be too troublesome

0 comments

Answer accepted by question author

0 additional answers

Your answer

Answer 1

Hey Ronyedson,

I think there's no direct "move" or "migrate" option for AKS. You'll need to create a new cluster in East US and redeploy your workloads. But it doesn't have to be as painful as starting from scratch:

Export your current cluster config — You can export your cluster as an ARM template (Portal → Export template) and redeploy it targeting East US. This saves you from reconfiguring everything manually.

Redeploy workloads — If you're using GitOps (Flux/ArgoCD), just point the new cluster at the same repo. If not, export your manifests with kubectl get deployment -o yaml > deployments.yaml and apply them to the new cluster.

Migrate stateful data — If you have persistent volumes, use AKS Backup to back up the source cluster and restore to the target.

Don't forget dependent resources — ACR, Key Vault, VNet, DNS, managed identities, Private Endpoints, etc. all need to exist in (or be accessible from) the target region.

Quota — Request quota in East US before you start. This way you avoid getting blocked mid-migration.

Cut over DNS — Once validated, update your DNS/Traffic Manager to point to the new cluster's ingress IP.

Full guide here: Relocate an AKS cluster to another region

It's a bit of work, but with IaC templates and GitOps it's very manageable. Good luck!

Share via

How can I migrate a AKS cluster to another region?

0 additional answers

Your answer