Help in evaluating Azure storage solutions for use inside AKS

Kailash 51 Reputation points

Hello everyone,
We are trying to pick a storage solution for persistent data within our AKS cluster. We will have 4-5 instances of an application, (one for each business unit) within a cluster under different namespaces. This is for an enterprise-wide implementation. And cost is not a factor here. We are mainly looking at performance, reliability and ability to scale in future. The associated applications performs heavy read/writes of files/artifacts/binaries. We want to have a robust & automated backup plan also in place.

I am leaning towards AZ disks. Basically, create a persistent volume and volume claim for each namespace and mount it with the corresponding application instance. I understand that the max nodes the disk can be shared with is 10. And that with sharing enabled, on-demand bursting is not available. We are fine with creating a separate disk for each instance of the application as well if it would be better than using a single disk and slicing it up for sharing with multiple instances.

Does anyone have any suggestions? Are there advantages of using AZ file share instead of AZ disks? Are there restrictions in using AZ disks over file share? Any other things that we should consider? Any inputs will be greatly appreciated.


Azure Files
Azure Files
An Azure service that offers file shares in the cloud.
1,184 questions
Azure Kubernetes Service (AKS)
Azure Kubernetes Service (AKS)
An Azure service that provides serverless Kubernetes, an integrated continuous integration and continuous delivery experience, and enterprise-grade security and governance.
1,890 questions
Azure Disk Storage
Azure Disk Storage
A high-performance, durable block storage designed to be used with Azure Virtual Machines and Azure VMware Solution.
583 questions
{count} votes

Accepted answer
  1. shiva patpi 13,146 Reputation points Microsoft Employee
    0 comments No comments

1 additional answer

Sort by: Most helpful
  1. Kailash 51 Reputation points

    Thanks Shiva for the response. On a related note, I am seeing this error with AZ disk. I created a single PV and PVC, mounted it on a single pod. Not sure why I am getting this error. Any idea? This is for POC only so no risk with data. But trying to understand what is the root cause here.

    Warning FailedMount 54s (x9 over 3m5s) kubelet MountVolume.MountDevice failed for volume "kailash-jenkinspv" : azureDisk - mountDevice:FormatAndMount failed with 'fsck' found errors on device /dev/disk/azure/scsi1/lun2 but could not correct them: fsck from util-linux 2.31.1
    /dev/sde contains a file system with errors, check forced.
    /dev/sde: Duplicate or bad block in use!
    /dev/sde: Multiply-claimed block(s) in inode 3932309: 15788928--15788983
    /dev/sde: Multiply-claimed block(s) in inode 3932549: 15781294
    /dev/sde: Multiply-claimed block(s) in inode 3932550: 15781295--15781356
    /dev/sde: Multiply-claimed block(s) in inode 3932551: 15781357
    /dev/sde: Multiply-claimed block(s) in inode 3934171: 15777787
    /dev/sde: Multiply-claimed block(s) in inode 3934176: 15777788
    /dev/sde: (There are 79 inodes containing multiply-claimed blocks.)

    /dev/sde: File /plugins/trilead-api.jpi (inode #3932309, mod time Thu Feb 24 11:44:14 2022)
    has 56 multiply-claimed block(s), shared with 3 file(s):
    /dev/sde: ... (inode #3934023, mod time Wed Jan 12 04:50:06 2022)
    /dev/sde: /plugins/workflow-support/WEB-INF/lib/jboss-marshalling-river-2.0.12.Final.jar (inode #3934021, mod time Wed Jan 12 04:49:38 2022)
    /dev/sde: /plugins/workflow-support/WEB-INF/lib/workflow-support.jar (inode #3934020, mod time Wed Jan 12 04:50:30 2022)

    (i.e., without -a or -p options)