Edit

Use Azure ultra disks on Azure Kubernetes Service

  • Article

Azure ultra disks offer high throughput, high IOPS, and consistent low latency disk storage for your stateful applications. One major benefit of ultra disks is the ability to dynamically change the performance of the SSD along with your workloads without the need to restart your agent nodes. Ultra disks are suited for data-intensive workloads.

This article describes how to configure a new or existing AKS cluster to use Azure ultra disks.

Before you begin

This feature can only be set at cluster creation or when creating a node pool.

Limitations

  • Azure ultra disks require node pools deployed in availability zones and regions that support these disks, and are only supported by specific VM series. Review the corresponding table under the Ultra disk limitations section for more information.
  • Ultra disks can't be used with some features and functionality, such as availability sets or Azure Disk Encryption. Review the Ultra disk limitations for the latest information.

Create a cluster that can use ultra disks

Create an AKS cluster that is able to leverage Azure ultra Disks by using the following CLI commands. Use the --enable-ultra-ssd parameter to set the EnableUltraSSD feature.

az aks create -g MyResourceGroup -n myAKSCluster -l westus2 --node-vm-size Standard_D2s_v3 --zones 1 2 --node-count 2 --enable-ultra-ssd

If you want to create a cluster without ultra disk support, you can do so by omitting the --enable-ultra-ssd parameter.

Enable ultra disks on an existing cluster

You can enable ultra disks on an existing cluster by adding a new node pool to your cluster that support ultra disks. Configure a new node pool to use ultra disks by using the --enable-ultra-ssd parameter with the az aks nodepool add command.

If you want to create new node pools without support for ultra disks, you can do so by excluding the --enable-ultra-ssd parameter.

Use ultra disks dynamically with a storage class

To use ultra disks in your deployments or stateful sets, you can use a storage class for dynamic provisioning.

Create the storage class

A storage class is used to define how a unit of storage is dynamically created with a persistent volume. For more information on Kubernetes storage classes, see Kubernetes storage classes. In this example, we'll create a storage class that references ultra disks.

  1. Create a file named azure-ultra-disk-sc.yaml and copy in the following manifest:

    kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
  name: ultra-disk-sc
provisioner: disk.csi.azure.com # replace with "kubernetes.io/azure-disk" if aks version is less than 1.21
volumeBindingMode: WaitForFirstConsumer # optional, but recommended if you want to wait until the pod that will use this disk is created 
parameters:
  skuname: UltraSSD_LRS
  kind: managed
  cachingMode: None
  diskIopsReadWrite: "2000"  # minimum value: 2 IOPS/GiB 
  diskMbpsReadWrite: "320"   # minimum value: 0.032/GiB

  2. Create the storage class using the kubectl apply command and specify your azure-ultra-disk-sc.yaml file.

    kubectl apply -f azure-ultra-disk-sc.yaml

    Your output should resemble the following example output:

    storageclass.storage.k8s.io/ultra-disk-sc created

Create a persistent volume claim

A persistent volume claim (PVC) is used to automatically provision storage based on a storage class. In this case, a PVC can use the previously created storage class to create an ultra disk.

  1. Create a file named azure-ultra-disk-pvc.yaml and copy in the following manifest:

    apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: ultra-disk
spec:
  accessModes:
 - ReadWriteOnce
  storageClassName: ultra-disk-sc
  resources:
    requests:
      storage: 1000Gi

    The claim requests a disk named ultra-disk that is 1000 GB in size with ReadWriteOnce access. The ultra-disk-sc storage class is specified as the storage class.

  2. Create the persistent volume claim using the kubectl apply command and specify your azure-ultra-disk-pvc.yaml file.

    kubectl apply -f azure-ultra-disk-pvc.yaml

    Your output should resemble the following example output:

    persistentvolumeclaim/ultra-disk created

Use the persistent volume

Once the persistent volume claim has been created and the disk successfully provisioned, a pod can be created with access to the disk. The following manifest creates a basic NGINX pod that uses the persistent volume claim named ultra-disk to mount the Azure disk at the path /mnt/azure.

  1. Create a file named nginx-ultra.yaml and copy in the following manifest:

    kind: Pod
apiVersion: v1
metadata:
  name: nginx-ultra
spec:
  containers:
 - name: nginx-ultra
    image: mcr.microsoft.com/oss/nginx/nginx:1.15.5-alpine
    resources:
      requests:
        cpu: 100m
        memory: 128Mi
      limits:
        cpu: 250m
        memory: 256Mi
    volumeMounts:
    - mountPath: "/mnt/azure"
      name: volume
  volumes:
    - name: volume
      persistentVolumeClaim:
        claimName: ultra-disk

  2. Create the pod using kubectl apply command and specify your nginx-ultra.yaml file.

    kubectl apply -f nginx-ultra.yaml

    Your output should resemble the following example output:

    pod/nginx-ultra created

    You now have a running pod with your Azure disk mounted in the /mnt/azure directory.

  3. See your configuration details using the kubectl describe pod command and specify your nginx-ultra.yaml file.

    kubectl describe pod nginx-ultra

    Your output should resemble the following example output:

    [...]
Volumes:
  volume:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  azure-managed-disk
    ReadOnly:   false
  default-token-smm2n:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-smm2n
    Optional:    false
[...]
Events:
  Type    Reason                 Age   From                               Message
  ----    ------                 ----  ----                               -------
  Normal  Scheduled              2m    default-scheduler                  Successfully assigned mypod to aks-nodepool1-79590246-0
  Normal  SuccessfulMountVolume  2m    kubelet, aks-nodepool1-79590246-0  MountVolume.SetUp succeeded for volume "default-token-smm2n"
  Normal  SuccessfulMountVolume  1m    kubelet, aks-nodepool1-79590246-0  MountVolume.SetUp succeeded for volume "pvc-faf0f176-8b8d-11e8-923b-deb28c58d242"
[...]

Next steps