Journey of an App: How to create an AKS cluster to deploy a Windows Container application

Welcome to the third and final video/blog post in this series where we are modernizing a web application from 2012 R2 running on-premises to Azure Services using Windows Containers. In case you missed it, here are part one and part two of the video series.

In this third part of our series we cover create an AKS and deploy our containerized application on top of it. We start by using the Azure portal to create a new AKS with most of the default options, but with key changes to include Windows Server worker nodes, and to ensure we have set up against our Azure Container Registry, so the image we uploaded can be pulled into the nodes running our application. I highly recommend you check the AKS documentation to see more details on the deployment and operation options of AKS.

After creating the AKS , we used this sample YAML file to describe how the application should be deployed. Finally, instead of connecting remotely using Kubectl, we used the recently announced feature (under preview) resource management from the Azure Portal. This new feature allows you to manage resources directly from the portal, so we were able to paste our YAML file directly from there.

To validate everything, we looked at the deployment and opened the application running on AKS and the application worked the same way it was working before.

Hopefully, this gave you an idea on how the end to end process of modernizing your application works. We're looking forward to seeing what you think of this video series and what you want to see next!


Twitter: @vrapolinario


This article was originally published by Microsoft's Core Infrastructure and Security Blog. You can find the original article here.