Migrate Azure classic cloud service to AKS under .net 4.7 framework

Gupta, Rohit 0 Reputation points
2023-01-20T16:43:24.7466667+00:00

My application architecture is

1-A project library is on .net 4.7 framework.

2-A azure cloud service which is calling project library as web role

Question-I need to move on from this azure classic cloud service since it is getting out of support from Microsoft next year in Jan 2024.

2-Please suggest architectural changes should I move into webapp or .net core or ???

Not Monitored
Not Monitored
Tag not monitored by Microsoft.
35,938 questions
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. SanthiSwaroopNaikBukke-4908 595 Reputation points
    2023-01-20T16:48:34.96+00:00

    Migrate Azure classic cloud service to AKS under .net 4.7 framework

    Migrating an Azure classic cloud service (also known as a Cloud Service Web/Worker Role) to an Azure Kubernetes Service (AKS) cluster can be a complex process, especially if the cloud service is running under the .NET 4.7 framework. Here is an overview of the steps you can take to migrate your classic cloud service to AKS:

    1. Assess your application: Before migrating, it's important to understand the requirements and dependencies of your cloud service, including the .NET framework version, any third-party libraries, and any other services it relies on. This information will help you plan the migration and ensure that your application will run correctly in the new environment.
    2. Containerize your application: To run your application in AKS, you will need to containerize it. This involves creating a Dockerfile that describes how to build an image of your application and its dependencies. You can use the .NET 4.7 runtime image from the Microsoft container registry as a base image for your application.
    3. Test your container: Once your application is containerized, you should test the container to ensure that it runs correctly and all dependencies are present. This step is crucial to ensure that your application will work as expected in the AKS cluster.
    4. Deploy to AKS: Once your application is containerized and tested, you can deploy it to your AKS cluster. You can use the kubectl command-line tool to deploy your container and create the necessary Kubernetes objects such as pods, services, and ingress.
    5. Monitor and Scale: Once your application is running in AKS, you should monitor its performance and scale it as needed to ensure that it can handle the load. AKS provides built-in monitoring and scaling capabilities that can be used to manage your application.