Google Cloud to Azure AKS

Question

We need to migrate this service https://github.com/peter-evans/nominatim-k8s ; from Google Cloud to Azure AKS, so all the configurations which are for Google cloud for this service needs to be changed it according to Azure.

Thank you for all the help

Answer 1

*anonymous user*

As it is kubernetes everything should work in similar way on both the cloud.

You can setup similar (compatible) cluster from Infra standpoint and move over pods to AKS.

However, from the link you shared I see this service uses storage. Check this documentation to create the required storage in Azure.

Answer 2

There are a few things

1. Services (If you GCP based LB, then you need to have similar Azure load balancer). In case you are using an Ingress instead (like nginx) you can move across straight
2. CNI - Do you use any GCP based CNI ? or something portable like kubernetic native or Istio/linkered. The later is very portable
3. Mounts - Volume mounts to cloud storage , they need to be recreated
4. Do you use cloud native services (such Cloud SQL?) - Azure has a different SQL. Also any No-SQL database services (may have to port to cosmos db)
5. Have you integrated to any GCP keyvaults - they need to be migrated
6. The underlying nodes - the Horizontal Pod Autoscaler work - but if you use Node based autoscaler /ephimeral nodes - Then your node infra is different
7. What version K8S you use GKE and AKS ( Now , I think both are 1.17 - Else there could be some compatibility issue)
8. Is this integrated to registry and any binary auth is done ? (For example Grafeas - it does not work on AKS , you may go for OPA- Open Policy Agent or Azure kubernetes polices)
9. The RBAC - This can be easy or difficult depends how are linking the IAM with K8S. The IAM are different
10. Cluster networking & Pod network ? They are different
11. Do you have to migrate the etcd . Its normally not very difficult . But it gets complex when control plane is managed

How do you create Infra ?- If you use terrafom, then you can create different provision modules make. Then you use tools like kitchen to test it.

So migration can be simple of complex ?

The kubernetes makes it platform agnostic - provided that factor is thought of. I would suggest using CNCF tasks which makes it really portable

Answer 3

Depending on which services you use, the scope of the migration may vary. If you are not dependent on platform-specific tools and don't need to move at the VM level, migrating at that level is relatively straightforward. There will be some coding work required if you rely on Google App Engine and Cloud Functions.

The ease of moving SaaS will depend on whether the same application is available on both platforms. In addition to the application, you need to consider underlying services. The migration of an app that is integrated with platform-specific analytics may be challenging.

Azure Migrate from Microsoft is a platform that migrates virtual machines to Azure. Versions of the product that worked only with on-premises servers have been replaced by versions that permit cloud-to-cloud migration as well. These are the tools that it consists of:

1. Server Assessment
2. Server Migration
3. Database Assessment
4. Database Migration

The first step is to calculate the scope of the migration. Discovering servers in your infrastructure is made easier thanks to Microsoft Assessment and Planning (MAP) tools. It allows you to determine what you need from Azure.
It is possible to move Azure Server Migration to a test environment before the live deployment begins. Any dependencies can be identified, fixed, and then switched over with minimal or no downtime.