address review comments

Signed-off-by: Ashima-Ashima1 <[email protected]>

Author: ashimagarg27

.secrets.baseline

@@ -3,7 +3,7 @@
     "files": "go.sum|^.secrets.baseline$",
     "lines": null
   },
-  "generated_at": "2024-11-21T04:40:19Z",
+  "generated_at": "2024-11-25T03:29:33Z",
   "plugins_used": [
     {
       "name": "AWSKeyDetector"
@@ -76,7 +76,17 @@
       "name": "TwilioKeyDetector"
     }
   ],
-  "results": {},
+  "results": {
+    "README.md": [
+      {
+        "hashed_secret": "325778ab9d49a6df7bc13a83563bec2de2a84c95",
+        "is_verified": false,
+        "line_number": 36,
+        "type": "Secret Keyword",
+        "verified_result": null
+      }
+    ]
+  },
   "version": "0.13.1+ibm.62.dss",
   "word_list": {
     "file": null,

README.md

@@ -29,12 +29,39 @@ make deploy IMG=<image-registry>/ibm-object-csi-driver-operator:<image-tag>
 kubectl apply -k config/samples/
 ```
 
-**Note**: By default, in the IBM Object CSI Driver, the secret name is not tied to the PVC name. This allows you to use a single secret across multiple PVCs. For this, you’ll need to add two specific annotations in the PVC YAML. These annotations help the driver map the PVC to the correct secret.
+**Note**: 
+- By default, in the IBM Object CSI Driver, the secret name is not tied to the PVC name. This allows you to use a single secret across multiple PVCs. For this, you’ll need to add two specific annotations in the PVC YAML. These annotations help the driver map the PVC to the correct secret.
 ```
 annotations:
     cos.csi.driver/secret: "custom-secret"
     cos.csi.driver/secret-namespace: "default"
 ```
+- If you want to have 1-to-1 mapping between each PVC and secret(using same name for both) i.e., specific secret tied to respective PVC, then you need to create a custom storage class as below and use it to create PVC.
+```
+apiVersion: storage.k8s.io/v1
+kind: StorageClass
+metadata:
+  name: custom-object-csi-storage-class
+  labels:
+provisioner: cos.s3.csi.ibm.io
+mountOptions:
+    - "multipart_size=62"
+    - "max_dirty_data=51200"
+    - "parallel_count=8"
+    - "max_stat_cache_size=100000"
+    - "retries=5"
+    - "kernel_cache"
+parameters:
+  mounter: <"s3fs" or "rclone">
+  client: "awss3"
+  cosEndpoint: "https://s3.direct.us-west.cloud-object-storage.appdomain.cloud"
+  locationConstraint: "us-west-smart"
+  csi.storage.k8s.io/provisioner-secret-name: ${pvc.name}
+  csi.storage.k8s.io/provisioner-secret-namespace: ${pvc.namespace}
+  csi.storage.k8s.io/node-publish-secret-name: ${pvc.name}
+  csi.storage.k8s.io/node-publish-secret-namespace: ${pvc.namespace}
+reclaimPolicy: <Retain or Delete>
+```
 
 ### Uninstall CRDs
 To delete the CRDs from the cluster: