This is a cache of https://docs.okd.io/4.11/storage/container_storage_interface/persistent-storage-csi-azure-file.html. It is a snapshot of the page at 2024-11-21T20:29:44.309+0000.
Azure File CSI Driver Operator - Using Container Storage Interface (CSI) | Storage | OKD 4.11
  1. Documentation
×

Azure File CSI Driver Operator

Overview

OKD is capable of provisioning persistent volumes (PVs) by using the Container Storage Interface (CSI) driver for Microsoft Azure File Storage.

Familiarity with persistent storage and configuring CSI volumes is recommended when working with a CSI Operator and driver.

To create CSI-provisioned PVs that mount to Azure File storage assets, OKD installs the Azure File CSI Driver Operator and the Azure File CSI driver by default in the openshift-cluster-csi-drivers namespace.

  • The Azure File CSI Driver Operator provides a storage class that is named azurefile-csi that you can use to create persistent volume claims (PVCs).

  • The Azure File CSI driver enables you to create and mount Azure File PVs. The Azure File CSI driver supports dynamic volume provisioning by allowing storage volumes to be created on-demand, eliminating the need for cluster administrators to pre-provision storage.

Azure File CSI Driver Operator does not support:

  • Virtual hard disks (VHD)

  • Network File System (NFS): OKD does not deploy a NFS-backed storage class.

  • Running on nodes with fips mode enabled.

For more information about supported features, see Supported CSI drivers and features.

About CSI

Storage vendors have traditionally provided storage drivers as part of Kubernetes. With the implementation of the Container Storage Interface (CSI), third-party providers can instead deliver storage plugins using a standard interface without ever having to change the core Kubernetes code.

CSI Operators give OKD users storage options, such as volume snapshots, that are not possible with in-tree volume plugins.

Additional resources