Sok3t/nfs-subdir-external-provisioner
1
0
Fork 0
Code Packages Releases Activity

fix(docs): managed-nfs-storage -> nfs-client

Browse Source 
Changed at 65b3ac93b6 

But it missed the one in README.md
This commit is contained in:
NeverBehave
2022-06-24 14:54:02 -07:00
committed by GitHub
parent 0bd4e87b34
commit 92fd6aac0e
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
README.md
View File

@@ -125,7 +125,7 @@ Now check the PVC's directory has been deleted.
**Step 7: Deploying your own PersistentVolumeClaims**
To deploy your own PVC, make sure that you have the correct `storageClassName` (by default `managed-nfs-storage`). You can also patch the StorageClass resource to change it, like so:
To deploy your own PVC, make sure that you have the correct `storageClassName` (by default `nfs-client`). You can also patch the StorageClass resource to change it, like so:
```yaml
# kustomization.yaml
@@ -136,7 +136,7 @@ resources:
patches:
- target:
kind: StorageClass
name: managed-nfs-storage
name: nfs-client
patch: |-
- op: replace
path: /metadata/name