You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/openshift/howto-create-a-storageclass.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -86,6 +86,15 @@ apiVersion: storage.k8s.io/v1
86
86
metadata:
87
87
name: azure-file
88
88
provisioner: kubernetes.io/azure-file
89
+
mountOptions:
90
+
- dir_mode=0777
91
+
- file_mode=0777
92
+
- uid=0
93
+
- gid=0
94
+
- mfsymlinks
95
+
- cache=strict
96
+
- actimeo=30
97
+
- noperm
89
98
parameters:
90
99
location: $LOCATION
91
100
secretNamespace: kube-system
@@ -99,6 +108,17 @@ EOF
99
108
oc create -f azure-storageclass-azure-file.yaml
100
109
```
101
110
111
+
Mount options for Azure Files will generally be dependent on the workload that you are deploying and the requirements of the application. Specifically for Azure files, there are additional parameters that you should consider using.
112
+
113
+
Mandatory parameters:
114
+
- "mfsymlinks" to map symlinks to a form the client can use
115
+
- "noperm" to disable permission checks on the client side
116
+
117
+
Recommended parameters:
118
+
- "nossharesock" to disable reusing sockets if the client is already connected via an existing mount point
119
+
- "actimeo=30" (or higher) to increase the time the CIFS client caches file and directory attributes
120
+
- "nobrl" to disable sending byte range lock requests to the server and for applications which have challenges with posix locks
121
+
102
122
## Change the default StorageClass (optional)
103
123
104
124
The default StorageClass on ARO is called managed-premium and uses the azure-disk provisioner. Change this by issuing patch commands against the StorageClass manifests.
0 commit comments