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: examples/kubernetes/dynamic_provisioning/README.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -41,7 +41,7 @@ This example requires Kubernetes 1.17 or later and a driver version of 1.2.0 or
41
41
*`basePath` (Optional) - The path on the file system under which the access point root directory is created. If the path isn't provided, the access points root directory is created under the root of the file system.
42
42
* `subPathPattern` (Optional) - A pattern that describes the subPath under which an access point should be created. So if the pattern were `${.PVC.namespace}/${PVC.name}`, the PVC namespace is `foo` and the PVC name is `pvc-123-456`, and the `basePath` is `/dynamic_provisioner` the access point would be
43
43
created at `/dynamic_provisioner/foo/pvc-123-456`.
44
-
* `ensureUniqueDirectories` (Optional) - A boolean that ensures that, if set, a UUID is appended to the final element of
44
+
* `ensureUniqueDirectory` (Optional) - A boolean that ensures that, if set, a UUID is appended to the final element of
45
45
any dynamically provisioned path, as in the above example. This can be turned off but this requires you as the
46
46
administrator to ensure that your storage classes are set up correctly. Otherwise, it's possible that 2 pods could
47
47
end up writing to the same directory by accident. **Please think very carefully before setting this to false!**
0 commit comments