From 0e0968b352992bebbd1c26fb080da8d77b249b5d Mon Sep 17 00:00:00 2001
From: duynguyen <huonghaiduynhim@gmail.com>
Date: Wed, 29 Jul 2026 23:15:53 +0700
Subject: [PATCH] fix: drop unsupported nfs-retain StorageClass via
 extraObjects

nfs-subdir-external-provisioner chart v4.0.18 has no extraObjects
values key - it was silently ignored, so nfs-retain never actually
existed. Only nfs-delete (native storageClass.* key) is real.
Updated README expected output to match.
---
 README.md                             |  5 ++---
 manifests/nfs-provisioner/values.yaml | 12 ------------
 2 files changed, 2 insertions(+), 15 deletions(-)

diff --git a/README.md b/README.md
index cb9a206..038c863 100644
--- a/README.md
+++ b/README.md
@@ -169,9 +169,8 @@ kubectl get storageclass
 Expected:
 
 ```
-NAME          PROVISIONER                                     RECLAIMPOLICY
-nfs-delete    cluster.local/nfs-subdir-external-provisioner  Delete
-nfs-retain    cluster.local/nfs-subdir-external-provisioner  Retain
+NAME                   PROVISIONER                                                     RECLAIMPOLICY
+nfs-delete (default)   cluster.local/nfs-provisioner-nfs-subdir-external-provisioner   Delete
 ```
 
 Test PVC provisioning:
diff --git a/manifests/nfs-provisioner/values.yaml b/manifests/nfs-provisioner/values.yaml
index 4912a20..56444e2 100644
--- a/manifests/nfs-provisioner/values.yaml
+++ b/manifests/nfs-provisioner/values.yaml
@@ -9,15 +9,3 @@ storageClass:
   defaultClass: true
   reclaimPolicy: Delete
   archiveOnDelete: false
-
-# Second StorageClass with Retain policy is created via extraObjects below
-extraObjects:
-  - apiVersion: storage.k8s.io/v1
-    kind: StorageClass
-    metadata:
-      name: nfs-retain
-    provisioner: cluster.local/nfs-subdir-external-provisioner
-    parameters:
-      archiveOnDelete: "false"
-    reclaimPolicy: Retain
-    volumeBindingMode: Immediate