

The following blog will explain your key matrix, insights of this type of OS Disk, and use case with Windows Virtual Desktop environment. If your VM is stateless, however, you can use an ephemeral OS disk, which has no additional storage cost beyond the base compute cost of. A Kubernetes volume can be a mounted storage service in Azure, such as a managed disk or Azure Files. You can have ephemeral volumes that live and die with a pod, or you can have persistent volumes, where the lifecycle is not attached to a pod. In order to resize the worker nodes within AKS you can use ARM to change the size of the OS disk to the 2tb maximum (however, that also has a hard IOPS. When working with storage in Kubernetes, there are some key concepts to consider. Remote Data disk storage is billed separately from virtual machines. Dsv4-series VMs feature Intel® Hyper-Threading Technology. If you need low read/to write latency to the OS layer and faster OS reimage consider Ephemeral Disk types. AKS itself does not support the mutation or remounting the disks of the underlying Virtual machine (the VMs are managed by AKS) and ephemeral OS disks are not yet supported (shipping this year). The Dv4-series sizes offer a combination of vCPU, memory and remote storage options for most production workloads. Stateless workloads like Windows Virtual Desktops work well and cost benefits by using such OS Disk type. Having said that it’s super faster than other disk types currently. Ephemeral type of disk is part of the local virtual machine and it’s not saved any Azure storage. AKS now supports the ability to create clusters with BYOK enabled for nodes using ephemeral OS disk if the chosen VM SKU supports ephemeral.
