From d4edadb771c5e70dd1d0f79246840ca918628d38 Mon Sep 17 00:00:00 2001 From: Adarsh Kumar Yadav <109620911+adarsh-dell@users.noreply.github.com> Date: Wed, 10 Jul 2024 20:20:57 +0530 Subject: [PATCH] Secret naming (#1171) --- content/docs/csidriver/troubleshooting/powerflex.md | 1 + content/docs/deployment/csmoperator/drivers/powerflex.md | 2 +- content/v1/deployment/csmoperator/drivers/powerflex.md | 2 +- content/v2/deployment/csmoperator/drivers/powerflex.md | 2 +- content/v3/deployment/csmoperator/drivers/powerflex.md | 2 +- 5 files changed, 5 insertions(+), 4 deletions(-) diff --git a/content/docs/csidriver/troubleshooting/powerflex.md b/content/docs/csidriver/troubleshooting/powerflex.md index fef8967ba3..11b7af93f3 100644 --- a/content/docs/csidriver/troubleshooting/powerflex.md +++ b/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:
1. Force delete the pod running on the node that went down.
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 --replicas=1 -n ``` | +|CSM object `vxflexos` is in falied state and CSI-Powerflex driver is not in running state | Verify the secret name: `kubectl get secret -n ` it should be in `-config` format. 1. Retrieve the existing secret: `kubectl get secret old-secret-name -n -o yaml > secret.yaml`
2. Edit the secret.yaml file: Change metadata.name to -Config
3. Apply the new secret: `kubectl apply -f secret.yaml`
4. Delete the old secret: kubectl delete secret old-secret-name| > diff --git a/content/docs/deployment/csmoperator/drivers/powerflex.md b/content/docs/deployment/csmoperator/drivers/powerflex.md index 41b01e5c19..4e99b16686 100644 --- a/content/docs/deployment/csmoperator/drivers/powerflex.md +++ b/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 diff --git a/content/v1/deployment/csmoperator/drivers/powerflex.md b/content/v1/deployment/csmoperator/drivers/powerflex.md index 583d30a902..dd4b0631fb 100644 --- a/content/v1/deployment/csmoperator/drivers/powerflex.md +++ b/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 diff --git a/content/v2/deployment/csmoperator/drivers/powerflex.md b/content/v2/deployment/csmoperator/drivers/powerflex.md index ec320816f3..b948253f8a 100644 --- a/content/v2/deployment/csmoperator/drivers/powerflex.md +++ b/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 diff --git a/content/v3/deployment/csmoperator/drivers/powerflex.md b/content/v3/deployment/csmoperator/drivers/powerflex.md index 715995194b..318a3ccc8a 100644 --- a/content/v3/deployment/csmoperator/drivers/powerflex.md +++ b/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