Deploy a Windows Server container on an Azure Kubernetes Service (AKS) cluster using the Azure portal

Artikkel
11/01/2024

Azure Kubernetes Service (AKS) is a managed Kubernetes service that lets you quickly deploy and manage clusters. In this article, you deploy an AKS cluster that runs Windows Server containers using the Azure portal. You also deploy an ASP.NET sample application in a Windows Server container to the cluster.

Note

To get started with quickly provisioning an AKS cluster, this article includes steps to deploy a cluster with default settings for evaluation purposes only. Before deploying a production-ready cluster, we recommend that you familiarize yourself with our baseline reference architecture to consider how it aligns with your business requirements.

Before you begin

This quickstart assumes a basic understanding of Kubernetes concepts. For more information, see Kubernetes core concepts for Azure Kubernetes Service (AKS).

If you don't have an Azure subscription, create an Azure free account before you begin.
If you're unfamiliar with the Azure Cloud Shell, review Overview of Azure Cloud Shell.
Make sure that the identity you're using to create your cluster has the appropriate minimum permissions. For more details on access and identity for AKS, see Access and identity options for Azure Kubernetes Service (AKS).

Create an AKS cluster

Sign in to the Azure portal.
On the Azure portal home page, select Create a resource.
In the Categories section, select Containers > Azure Kubernetes Service (AKS).
On the Basics tab, configure the following settings:
- Under Project details:
  - Subscription: Select the Azure subscription you want to use for this AKS cluster.
  - Resource group: Select Create new, enter a resource group name, such as myResourceGroup, and then select Ok. While you can select an existing resource group, for testing or evaluation purposes, we recommend creating a resource group to temporarily host these resources and avoid impacting your production or development workloads.
- Under Cluster details:
  - Cluster preset configuration: Select Dev/Test. For more details on preset configurations, see Cluster configuration presets in the Azure portal.
    
    Note
    
    You can change the preset configuration when creating your cluster by selecting Compare presets and choosing a different option.
  - Kubernetes cluster name: Enter a cluster name, such as myAKSCluster.
  - Region: Select a region, such as East US 2.
  - Availability zones: Select None.
  - AKS pricing tier: Select Free.
  - Leave the default values for the remaining settings, and select Next.
On the Node pools tab, configure the following settings:
- Select Add node pool and enter a Node pool name, such as npwin. For a Windows node pool, the name must be six characters or fewer.
- Mode: Select User.
- OS SKU: Select Windows 2022.
- Availability zones: Select None.
- Leave the Enable Azure Spot instances checkbox unchecked.
- Node size: Select Choose a size. On the Select a VM size page, select D2s_v3, and then select Select.
- Leave the default values for the remaining settings, and select Add.
Select Review + create to run validation on the cluster configuration. After validation completes, select Create.

It takes a few minutes to create the AKS cluster. When your deployment is complete, navigate to your resource by selecting Go to resource, or by browsing to the AKS cluster resource group and selecting the AKS resource.

Connect to the cluster

You use kubectl, the Kubernetes command-line client, to manage your Kubernetes clusters. kubectl is already installed if you use Azure Cloud Shell. If you're unfamiliar with the Cloud Shell, review Overview of Azure Cloud Shell.

Azure CLI
Azure PowerShell

Open Cloud Shell by selecting the >_ button at the top of the Azure portal page.
Configure kubectl to connect to your Kubernetes cluster using the az aks get-credentials command. The following command downloads credentials and configures the Kubernetes CLI to use them.
```
az aks get-credentials --resource-group myResourceGroup --name myAKSCluster
```

Verify the connection to your cluster using the kubectl get nodes command, which returns a list of the cluster nodes.

kubectl get nodes

The following sample output shows all the nodes in the cluster. Make sure the status of all nodes is Ready:

NAME                                STATUS   ROLES   AGE     VERSION
aks-agentpool-11741175-vmss000000   Ready    agent   8m17s   v1.29.9
aks-agentpool-11741175-vmss000001   Ready    agent   8m17s   v1.29.9
aksnpwin000000                      Ready    agent   8m17s   v1.29.9
aks-userpool-11741175-vmss000000    Ready    agent   8m17s   v1.29.9
aks-userpool-11741175-vmss000001    Ready    agent   8m17s   v1.29.9

Open Cloud Shell by selecting the >_ button at the top of the Azure portal page.
Configure kubectl to connect to your Kubernetes cluster using the Import-AzAksCredential cmdlet. The following command downloads credentials and configures the Kubernetes CLI to use them.
```
Import-AzAksCredential -ResourceGroupName myResourceGroup -Name myAKSCluster
```

Verify the connection to your cluster using the kubectl get nodes command, which returns a list of the cluster nodes.

kubectl get nodes

The following sample output shows all the nodes in the cluster. Make sure the status of all nodes is Ready:

NAME                                STATUS   ROLES   AGE     VERSION
aks-agentpool-11741175-vmss000000   Ready    agent   8m17s   v1.29.9
aks-agentpool-11741175-vmss000001   Ready    agent   8m17s   v1.29.9
aksnpwin000000                      Ready    agent   8m17s   v1.29.9
aks-userpool-11741175-vmss000000    Ready    agent   8m17s   v1.29.9
aks-userpool-11741175-vmss000001    Ready    agent   8m17s   v1.29.9

Deploy the application

A Kubernetes manifest file defines a desired state for the cluster, such as which container images to run. In this quickstart, you use a manifest file to create all objects needed to run the ASP.NET sample application in a Windows Server container. This manifest file 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. The Kubernetes manifest file must 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 paste in the following YAML definition.

apiVersion: apps/v1
kind: Deployment
metadata:
  name: sample
  labels:
    app: sample
spec:
  replicas: 1
  template:
    metadata:
      name: sample
      labels:
        app: sample
    spec:
      nodeSelector:
        "kubernetes.io/os": windows
      containers:
      - name: sample
        image: mcr.microsoft.com/dotnet/framework/samples:aspnetapp
        resources:
          limits:
            cpu: 1
            memory: 800M
        ports:
          - containerPort: 80
  selector:
    matchLabels:
      app: sample
---
apiVersion: v1
kind: Service
metadata:
  name: sample
spec:
  type: LoadBalancer
  ports:
  - protocol: TCP
    port: 80
  selector:
    app: sample

For a breakdown of YAML manifest files, see Deployments and YAML manifests.

If you create and save the YAML file locally, then you can upload the manifest file to your default directory in CloudShell by selecting the Upload/Download files button and selecting the file from your local file system.

Deploy the application using the kubectl apply command and specify the name of your YAML manifest.
```
kubectl apply -f sample.yaml
```
The following sample 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 for provisioning.

Check the status of the deployed pods using the kubectl get pods command. Make all pods are Running before proceeding.
```
kubectl get pods
```

Monitor progress using the kubectl get service command with the --watch argument.

kubectl get service sample --watch

Initially, the output shows the EXTERNAL-IP for the sample service as pending:

NAME               TYPE           CLUSTER-IP   EXTERNAL-IP   PORT(S)        AGE
sample             LoadBalancer   10.0.37.27   <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.
See the sample app in action by opening a web browser to the external IP address of your service.

Delete resources

If you don't plan on going through the AKS tutorial, you should delete your cluster to avoid incurring Azure charges.

In the Azure portal, navigate to your resource group.
Select Delete resource group.
Enter the name of your resource group to confirm deletion and select Delete.
In the Delete confirmation dialog box, select Delete.

Note

The AKS cluster was created with system-assigned managed identity (default identity option used in this quickstart), the identity is managed by the platform and does not require removal.

Next steps

In this quickstart, you deployed a Kubernetes cluster and then deployed an ASP.NET sample application in a Windows Server container to it. This sample application is for demo purposes only and doesn't represent all the best practices for Kubernetes applications. For guidance on creating full solutions with AKS for production, see AKS solution guidance.

To learn more about AKS, and to walk through a complete code-to-deployment example, continue to the Kubernetes cluster tutorial.

AKS tutorial

Jagamisviis: