From 62ff474248720fc64bf808e3cd8e99f90ef5c42e Mon Sep 17 00:00:00 2001 From: Rishabh Raj <120644626+rishabh-dell@users.noreply.github.com> Date: Thu, 9 Feb 2023 17:46:55 +0530 Subject: [PATCH] CSI PowerStore : Update file name from config.yaml to secret.yaml (#454) * Updated file name from config.yaml to secret.yaml * updated file --- content/docs/csidriver/upgradation/drivers/powerstore.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/csidriver/upgradation/drivers/powerstore.md b/content/docs/csidriver/upgradation/drivers/powerstore.md index 4bac7a474c..0dbb2c5abf 100644 --- a/content/docs/csidriver/upgradation/drivers/powerstore.md +++ b/content/docs/csidriver/upgradation/drivers/powerstore.md @@ -15,7 +15,7 @@ Note: While upgrading the driver via helm, controllerCount variable in myvalues. **Steps** 1. Run `git clone -b v2.5.0 https://github.com/dell/csi-powerstore.git` to clone the git repository and get the driver. -2. Edit `helm/config.yaml` file and configure connection information for your PowerStore arrays changing the following parameters: +2. Edit `samples/secret/secret.yaml` file and configure connection information for your PowerStore arrays changing the following parameters: - *endpoint*: defines the full URL path to the PowerStore API. - *globalID*: specifies what storage cluster the driver should use - *username*, *password*: defines credentials for connecting to array. @@ -28,7 +28,7 @@ Note: While upgrading the driver via helm, controllerCount variable in myvalues. Add more blocks similar to above for each PowerStore array if necessary. 3. (optional) create new storage classes using ones from `samples/storageclass` folder as an example and apply them to the Kubernetes cluster by running `kubectl create -f ` - >Storage classes created by v1.4/v2.0/v2.1/v2.2/v2.3/v2.4 driver will not be deleted, v2.5 driver will use default array to manage volumes provisioned with old storage classes. Thus, if you still have volumes provisioned by v1.4/v2.0/v2.1/v2.2/v2.3/v2.4 in your cluster then be sure to include the same array you have used for the v1.4/v2.0/v2.1/v2.2/v2.3/v2.4 driver and make it default in the `config.yaml` file. + >Storage classes created by v1.4/v2.0/v2.1/v2.2/v2.3/v2.4 driver will not be deleted, v2.5 driver will use default array to manage volumes provisioned with old storage classes. Thus, if you still have volumes provisioned by v1.4/v2.0/v2.1/v2.2/v2.3/v2.4 in your cluster then be sure to include the same array you have used for the v1.4/v2.0/v2.1/v2.2/v2.3/v2.4 driver and make it default in the `secret.yaml` file. 4. Create the secret by running ```kubectl create secret generic powerstore-config -n csi-powerstore --from-file=config=secret.yaml``` 5. Copy the default values.yaml file `cd dell-csi-helm-installer && cp ../helm/csi-powerstore/values.yaml ./my-powerstore-settings.yaml` and update parameters as per the requirement. 6. Run the `csi-install` script with the option _\-\-upgrade_ by running: `./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade`.