Deploy Windows applications in Azure Kubernetes Service on Azure Stack HCI

Applies to: AKS on Azure Stack HCI, AKS runtime on Windows Server 2019 Datacenter

In this tutorial, you deploy an ASP.NET sample application in a Windows Server container to the Kubernetes cluster and learn how to see how to test and scale your application. You will also learn how to join a Windows nodes to an Active Directory domain. This tutorial assumes a basic understanding of Kubernetes concepts. For more information, see Kubernetes core concepts for Azure Kubernetes Service on Azure Stack HCI.

Before you begin

Verify you have the following requirements ready:

Deploy the application

A Kubernetes manifest file defines a desired state for the cluster, such as what container images to run. In this article, a manifest is used to create all objects needed to run the ASP.NET sample application in a Windows Server container. This manifest includes a Kubernetes deployment for the ASP.NET sample application and an external Kubernetes service to access the application from the internet.

The ASP.NET sample application is provided as part of the .NET Framework Samples and runs in a Windows Server container. Azure Kubernetes Service on Azure Stack HCI requires Windows Server containers to be based on images of Windows Server 2019.

The Kubernetes manifest file must also define a node selector to tell your AKS cluster to run your ASP.NET sample application's pod on a node that can run Windows Server containers.

Create a file named sample.yaml and copy in the following YAML definition.

apiVersion: apps/v1
kind: Deployment
  name: sample
    app: sample
  replicas: 1
      name: sample
        app: sample
        "": windows
      - name: sample
            cpu: 1
            memory: 800M
            cpu: .1
            memory: 300M
          - containerPort: 80
      app: sample
apiVersion: v1
kind: Service
  name: sample
  type: LoadBalancer
  - protocol: TCP
    port: 80
    app: sample

Deploy the application using the kubectl apply command and specify the name of your YAML manifest:

kubectl apply -f sample.yaml

The following example output shows the deployment and service created successfully:

deployment.apps/sample created
service/sample created

Test the application

When the application runs, a Kubernetes service exposes the application front end to the internet. This process can take a few minutes to complete. Occasionally the service can take longer than a few minutes to provision. Allow up to 10 minutes in these cases.

To monitor progress, use the kubectl get service command with the --watch argument.

kubectl get service sample --watch

Initially the EXTERNAL-IP for the sample service is shown as pending.

sample  LoadBalancer   <pending>     80:30572/TCP   6s

When the EXTERNAL-IP address changes from pending to an actual public IP address, use CTRL-C to stop the kubectl watch process. The following example output shows a valid public IP address assigned to the service:

NAME    TYPE           CLUSTER-IP   EXTERNAL-IP     PORT(S)        AGE
sample  LoadBalancer   80:30572/TCP   2m

To see the sample app in action, open a web browser to the external IP address of your service.

Image of browsing to ASP.NET sample application

If you receive a connection timeout when trying to load the page, verify if the sample app is ready with kubectl get pods --watch command. Sometimes, the external IP address is available before the windows container has started.

Scale application pods

We have created a single replica of the application front-end. To see the number and state of pods in your cluster, use the kubectl get command as follows:

kubectl get pods -n default

To change the number of pods in the sample deployment, use the kubectl scale command. The following example increases the number of front-end pods to 3:

kubectl scale --replicas=3 deployment/sample

Run kubectl get pods again to verify that additional pods have been created. After a minute or so, the additional pods are available in your cluster:

kubectl get pods -n default

Next steps