Skip to content

[enterprise-4.13] OCPBUGS-17558 & 17559: Adding NFS support to Azure File CSI #66211

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Oct 13, 2023
Merged

[enterprise-4.13] OCPBUGS-17558 & 17559: Adding NFS support to Azure File CSI #66211

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
40 changes: 40 additions & 0 deletions modules/persistent-storage-csi-azure-file-nfs.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,40 @@
// Module included in the following assemblies:
//
// * storage/container_storage_interface/persistent_storage-csi-azure-file.adoc
//

:_content-type: CONCEPT
[id="persistent-storage-csi-azure-file-nfs_{context}"]
= NFS support

{product-title} supports the Azure File Container Storage Interface (CSI) Driver Operator with Network File System (NFS) with the following restrictions:

* Creating pods with Azure File NFS volumes that are scheduled to the control plane node causes the mount to be denied.
+
To work around this issue: If your control plane nodes are schedulable, and the pods can run on worker nodes, use `nodeSelector` or Affinity to schedule the pod in worker nodes.

* FS Group policy behavior:
+
[IMPORTANT]
=====
Azure File CSI with NFS does not honor the `fsGroupChangePolicy` requested by pods. Azure File CSI with NFS applies a default `OnRootMismatch` FS Group policy regardless of the policy requested by the pod.
=====

* The Azure File CSI Operator does not automatically create a storage class for NFS. You must create it manually. Use a file similar to the following:
+
[source, yaml]
----
apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: <storage-class-name> <1>
provisioner: file.csi.azure.com <2>
parameters:
protocol: nfs <3>
skuName: Premium_LRS # available values: Premium_LRS, Premium_ZRS
mountOptions:
- nconnect=4
----
<1> Storage class name.
<2> Specifies the Azure File CSI provider.
<3> Specifies NFS as the storage backend protocol.
4 changes: 3 additions & 1 deletion storage/container_storage_interface/persistent-storage-csi-azure-file.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ To create CSI-provisioned PVs that mount to Azure File storage assets, {product-

* 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:
Azure File CSI Driver Operator does _not_ support:

* Virtual hard disks (VHD)

Expand All @@ -27,6 +27,8 @@ Azure File CSI Driver Operator does not support:

For more information about supported features, see xref:../../storage/container_storage_interface/persistent-storage-csi.adoc#csi-drivers-supported_persistent-storage-csi[Supported CSI drivers and features].

include::modules/persistent-storage-csi-azure-file-nfs.adoc[leveloffset=+1]

include::modules/persistent-storage-csi-about.adoc[leveloffset=+1]

.Additional resources
Expand Down