Secret naming (#1171)

content/docs/csidriver/troubleshooting/powerflex.md

@@ -31,6 +31,7 @@ description: Troubleshooting PowerFlex Driver
 | In version v2.6.0, when a cluster node goes down, the block volumes attached to the node cannot be attached to another node. | This is a known issue reported at [kubernetes-csi/external-attacher#215](https://github.com/kubernetes-csi/external-attacher/issues/215). Workaround: <br/> 1. Force delete the pod running on the node that went down. <br/> 2. Delete the pod's persistent volume attachment on the node that went down. Now the volume can be attached to the new node.
 A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-vxflexos.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."` | This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in [csidriver.yaml](https://github.com/dell/helm-charts/blob/csi-vxflexos-2.8.0/charts/csi-vxflexos/templates/csidriver.yaml) file with the required security profile value should be provided. Follow [OpenShift 4.13 documentation for CSI Ephemeral Volumes](https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html) for more information. |
 | Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>``` |
+|CSM object `vxflexos` is in falied state and CSI-Powerflex driver is not in running state | Verify the secret name: `kubectl get secret -n <namespace_name>` it should be in `<CR-name>-config` format. 1. Retrieve the existing secret: `kubectl get secret old-secret-name -n <namespace_name> -o yaml > secret.yaml` <br> 2. Edit the secret.yaml file: Change metadata.name to <CR-name>-Config <br> 3. Apply the new secret: `kubectl apply -f secret.yaml` <br> 4. Delete the old secret: kubectl delete secret old-secret-name|
 
 >
 

content/docs/deployment/csmoperator/drivers/powerflex.md

@@ -111,7 +111,7 @@ For detailed PowerFlex installation procedure, see the [Dell PowerFlex Deploymen
 
     If replication feature is enabled, ensure the secret includes all the PowerFlex arrays involved in replication.
 
-    After editing the file, run this command to create a secret called `vxflexos-config`. If you are using a different namespace/secret name, just substitute those into the command.
+    After editing the file, run this command to create a secret called `vxflexos-config`.
     ```bash
     
     kubectl create secret generic vxflexos-config -n vxflexos --from-file=config=secret.yaml

content/v1/deployment/csmoperator/drivers/powerflex.md

@@ -111,7 +111,7 @@ For detailed PowerFlex installation procedure, see the _Dell PowerFlex Deploymen
 
     If replication feature is enabled, ensure the secret includes all the PowerFlex arrays involved in replication.
 
-    After editing the file, run this command to create a secret called `vxflexos-config`. If you are using a different namespace/secret name, just substitute those into the command.
+    After editing the file, run this command to create a secret called `vxflexos-config`.
     ```bash
     
     kubectl create secret generic vxflexos-config -n vxflexos --from-file=config=secret.yaml

content/v2/deployment/csmoperator/drivers/powerflex.md

@@ -112,7 +112,7 @@ For detailed PowerFlex installation procedure, see the _Dell PowerFlex Deploymen
       mdm: "10.0.0.3,10.0.0.4"
     ```
 
-    After editing the file, run this command to create a secret called `vxflexos-config`. If you are using a different namespace/secret name, just substitute those into the command.
+    After editing the file, run this command to create a secret called `vxflexos-config`.
     ```bash
     
     kubectl create secret generic vxflexos-config -n vxflexos --from-file=config=secret.yaml

content/v3/deployment/csmoperator/drivers/powerflex.md

@@ -114,7 +114,7 @@ For detailed PowerFlex installation procedure, see the _Dell PowerFlex Deploymen
       AllSystemNames: "name1,name2"
     ```
 
-    After editing the file, run this command to create a secret called `test-vxflexos-config`. If you are using a different namespace/secret name, just substitute those into the command.
+    After editing the file, run this command to create a secret called `test-vxflexos-config`.
     ```bash
     
     kubectl create secret generic test-vxflexos-config -n test-vxflexos --from-file=config=config.yaml