From 92fd6aac0e1994a222a59e36a5f3ba87c5da2d6f Mon Sep 17 00:00:00 2001 From: NeverBehave Date: Fri, 24 Jun 2022 14:54:02 -0700 Subject: [PATCH] fix(docs): managed-nfs-storage -> nfs-client Changed at https://github.com/kubernetes-sigs/nfs-subdir-external-provisioner/commit/65b3ac93b6e8f621fc6b42dd1d2cb1d7a6be2b9e But it missed the one in README.md --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 50e8dccf..2a874a9a 100644 --- a/README.md +++ b/README.md @@ -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