Skip to content

Commit 42e3116

Browse files
authored
Fix ensureUniqueDirectory paramater at docs
I notice the name for `ensureUniqueDirectory` is wrong in the README, its correct at the example, but wrong here.
1 parent b00bf67 commit 42e3116

File tree

1 file changed

+1
-1
lines changed
  • examples/kubernetes/dynamic_provisioning

1 file changed

+1
-1
lines changed

examples/kubernetes/dynamic_provisioning/README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,7 @@ This example requires Kubernetes 1.17 or later and a driver version of 1.2.0 or
4141
* `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.
4242
* `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
4343
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
4545
any dynamically provisioned path, as in the above example. This can be turned off but this requires you as the
4646
administrator to ensure that your storage classes are set up correctly. Otherwise, it's possible that 2 pods could
4747
end up writing to the same directory by accident. **Please think very carefully before setting this to false!**

0 commit comments

Comments
 (0)