Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSI PowerStore : Update file name from config.yaml to secret.yaml #454

Merged
merged 2 commits into from
Feb 9, 2023
Merged

CSI PowerStore : Update file name from config.yaml to secret.yaml #454

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
988b5a3
Updated file name from config.yaml to secret.yaml
rishabhatdell Feb 9, 2023
53c833f
updated file
rishabhatdell Feb 9, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/csidriver/upgradation/drivers/powerstore.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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 <path_to_storageclass_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 `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`.
Expand Down