Skip to content

NFS on AKS

“Use NFS” is not a single AKS design. In practice, AKS operators choose among Azure Files NFS, Azure NetApp Files, and the exceptional case of self-hosted NFS. The right answer depends on latency, data-management expectations, and how much storage control plane you want to own yourself.

Main Content

Pick the NFS service by operational goal

flowchart TD
    A[AKS workload needs NFS] --> B{Need advanced NAS features or very low latency?}
    B -->|Yes| C[Choose Azure NetApp Files]
    B -->|No| D{Need built-in AKS CSI simplicity?}
    D -->|Yes| E[Choose Azure Files NFS]
    D -->|No| F[Self-hosted NFS only by explicit exception]

Option comparison

Option Best fit Strengths Watch-outs
Azure Files NFS Shared Linux file storage on AKS with built-in CSI flow Native AKS storage-class workflow, full POSIX support, easier operational model than running your own NFS servers Premium shares only, VNet-enabled storage account required, not the right fit for the most latency-sensitive NAS workloads.
Azure NetApp Files Enterprise NAS, very low latency, rich data-management features NFSv3/NFSv4.1, advanced management, stronger fit for demanding shared-state workloads Separate service and operating model; dynamic provisioning uses Trident rather than the built-in AKS drivers.
Self-hosted NFS Exception path for legacy or specialized constraints Maximum protocol-level control You own patching, HA, export policy, scale, backup, and incident recovery.

Azure Files NFS on AKS

Use Azure Files NFS when you want the AKS-native CSI experience and the workload needs shared Linux file storage.

Key implications:

  • Requires premium file shares.
  • Requires a virtual-network-enabled storage account.
  • Works well for shared files, RWX Linux state, and container-native file patterns.
  • Tuning usually starts with nconnect=4, noresvport, and metadata-aware mount options.

Azure NetApp Files on AKS

Use Azure NetApp Files when NFS is part of a broader enterprise NAS requirement, not just a PVC request.

It is the stronger fit when you need:

  • Lower latency and more demanding performance envelopes.
  • Richer NAS data-management features.
  • NFSv3 or NFSv4.1 with more advanced storage expectations.

AKS note: dynamic provisioning is typically done through Trident, not the built-in AKS Azure Files/Azure Disk/Azure Blob CSI path.

Self-hosted NFS on AKS

Self-hosted NFS is an exception path, not the default recommendation. Consider it only when a managed Azure NFS service does not satisfy a hard technical requirement.

If you choose it, you inherit:

  • NFS server patching and lifecycle
  • export-policy governance
  • failover and HA design
  • backup and restore ownership
  • performance troubleshooting down to the server tier

That trade-off is sometimes necessary, but it is almost never the simplest day-2 model.

Decision guidance

  • Choose Azure Files NFS when you want AKS-native simplicity and the workload fits premium shared file storage.
  • Choose Azure NetApp Files when the workload is truly NAS-centric and needs richer performance or management capabilities.
  • Choose self-hosted NFS only when you are intentionally accepting infrastructure ownership.

See Also

Sources