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: docs/howto.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -216,7 +216,7 @@ to its documentation on how to install the csi driver.
216
216
First create a (non provisioning) storage class to differentiate SMB shares
217
217
from other storage.
218
218
219
-
```
219
+
```yaml
220
220
apiVersion: storage.k8s.io/v1
221
221
kind: StorageClass
222
222
metadata:
@@ -233,7 +233,7 @@ username/password pair that exists in your AD. When using pre-defined users &
233
233
groups the username/password pair must match one that is defined in the JSON
234
234
embedded in the secret associated with your SmbSecurityConfig.
235
235
236
-
```
236
+
```yaml
237
237
apiVersion: v1
238
238
kind: Secret
239
239
metadata:
@@ -248,7 +248,7 @@ stringData:
248
248
The following persistent volume will allow mounting the share.
249
249
Note the `spec.csi.volumeAttributes.source`: `myshare`is the share's service name, `mynamespace` the namespace the `SmbShare` is in and `My Great Share` is the share's `shareName` as configured or the share's name if not.
250
250
251
-
```
251
+
```yaml
252
252
apiVersion: v1
253
253
kind: PersistentVolume
254
254
metadata:
@@ -280,7 +280,7 @@ spec:
280
280
```
281
281
282
282
Then the volume claim can be created and should bind shorty after to the persistent volume.
0 commit comments