From eaf6b3ac583311dedbded1ec8cbc74e279623e4e Mon Sep 17 00:00:00 2001 From: Randeep Sharma Date: Fri, 12 Aug 2022 18:55:41 +0530 Subject: [PATCH 1/3] doc-update-2.4-powerscale-driver --- content/docs/csidriver/installation/helm/isilon.md | 8 ++++---- content/docs/csidriver/release/powerscale.md | 8 ++------ content/docs/csidriver/upgradation/drivers/isilon.md | 4 ++-- 3 files changed, 8 insertions(+), 12 deletions(-) diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md index d1ba801503..49736cf997 100644 --- a/content/docs/csidriver/installation/helm/isilon.md +++ b/content/docs/csidriver/installation/helm/isilon.md @@ -121,7 +121,7 @@ CRDs should be configured during replication prepare stage with repctl as descri ## Install the Driver **Steps** -1. Run `git clone -b v2.3.0 https://github.com/dell/csi-powerscale.git` to clone the git repository. +1. Run `git clone -b v2.4.0 https://github.com/dell/csi-powerscale.git` to clone the git repository. 2. Ensure that you have created the namespace where you want to install the driver. You can run `kubectl create namespace isilon` to create a new one. The use of "isilon" as the namespace is just an example. You can choose any name for the namespace. 3. Collect information from the PowerScale Systems like IP address, IsiPath, username, and password. Make a note of the value for these parameters as they must be entered in the *secret.yaml*. 4. Copy *the helm/csi-isilon/values.yaml* into a new location with name say *my-isilon-settings.yaml*, to customize settings for installation. @@ -267,7 +267,7 @@ The CSI driver for Dell PowerScale version 1.5 and later, `dell-csi-helm-install ### What happens to my existing storage classes? -*Upgrading from CSI PowerScale v2.2 driver*: +*Upgrading from CSI PowerScale v2.3 driver*: The storage classes created as part of the installation have an annotation - "helm.sh/resource-policy": keep set. This ensures that even after an uninstall or upgrade, the storage classes are not deleted. You can continue using these storage classes if you wish so. *NOTE*: @@ -289,9 +289,9 @@ Starting CSI PowerScale v1.6, `dell-csi-helm-installer` will not create any Volu ### What happens to my existing Volume Snapshot Classes? -*Upgrading from CSI PowerScale v2.2 driver*: +*Upgrading from CSI PowerScale v2.3 driver*: The existing volume snapshot class will be retained. *Upgrading from an older version of the driver*: -It is strongly recommended to upgrade the earlier versions of CSI PowerScale to 1.6 or higher before upgrading to 2.2. +It is strongly recommended upgrading the earlier versions of CSI PowerScale to 1.6 or higher before upgrading to 2.32. diff --git a/content/docs/csidriver/release/powerscale.md b/content/docs/csidriver/release/powerscale.md index 1a14c62bb6..4aa05ca21a 100644 --- a/content/docs/csidriver/release/powerscale.md +++ b/content/docs/csidriver/release/powerscale.md @@ -3,15 +3,11 @@ title: PowerScale description: Release notes for PowerScale CSI driver --- -## Release Notes - CSI Driver for PowerScale v2.3.0 +## Release Notes - CSI Driver for PowerScale v2.4.0 ### New Features/Changes -- Removed beta volumesnapshotclass sample files. -- Added support for Kubernetes 1.24. -- Added support to increase volume path limit. -- Added support for OpenShift 4.10. -- Added support for CSM Resiliency sidecar via Helm. +- Added support to add client only to root clients when RO volume is created from snapshot and RootClientEnabled is set to true. ### Fixed Issues diff --git a/content/docs/csidriver/upgradation/drivers/isilon.md b/content/docs/csidriver/upgradation/drivers/isilon.md index 75fca2acda..5fcdd65f99 100644 --- a/content/docs/csidriver/upgradation/drivers/isilon.md +++ b/content/docs/csidriver/upgradation/drivers/isilon.md @@ -8,12 +8,12 @@ Description: Upgrade PowerScale CSI driver --- You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSI Operator. -## Upgrade Driver from version 2.2.0 to 2.3.0 using Helm +## Upgrade Driver from version 2.3.0 to 2.4.0 using Helm **Note:** While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes. **Steps** -1. Clone the repository using `git clone -b v2.3.0 https://github.com/dell/csi-powerscale.git`, copy the helm/csi-isilon/values.yaml into a new location with a custom name say _my-isilon-settings.yaml_, to customize settings for installation. Edit _my-isilon-settings.yaml_ as per the requirements. +1. Clone the repository using `git clone -b v2.4.0 https://github.com/dell/csi-powerscale.git`, copy the helm/csi-isilon/values.yaml into a new location with a custom name say _my-isilon-settings.yaml_, to customize settings for installation. Edit _my-isilon-settings.yaml_ as per the requirements. 2. Change to directory dell-csi-helm-installer to install the Dell PowerScale `cd dell-csi-helm-installer` 3. Upgrade the CSI Driver for Dell PowerScale using following command: From 217a797cfefef427cef23f223dc3eddf8b14adc8 Mon Sep 17 00:00:00 2001 From: Randeep Sharma Date: Fri, 12 Aug 2022 18:57:36 +0530 Subject: [PATCH 2/3] update-label-resiliency --- content/docs/resiliency/_index.md | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/content/docs/resiliency/_index.md b/content/docs/resiliency/_index.md index ab043bc23d..9b930be5bd 100644 --- a/content/docs/resiliency/_index.md +++ b/content/docs/resiliency/_index.md @@ -144,7 +144,13 @@ pmtu3 podmontest-0 1/1 Running 0 3m6s ... ``` - CSM for Resiliency may also generate events if it is unable to cleanup a pod for some reason. For example, it may not clean up a pod because the pod is still doing I/O to the array. + CSM for Resiliency may also generate events if it is unable to clean up a pod for some reason. For example, it may not clean up a pod because the pod is still doing I/O to the array. + + Similarly, the label selector for csi-powerscale and csi-unity would be as below respectively. + ``` + labelSelector: {map[podmon.dellemc.com/driver:csi-isilon] + labelSelector: {map[podmon.dellemc.com/driver:csi-unity] + ``` #### Important Before putting an application into production that relies on CSM for Resiliency monitoring, it is important to do a few test failovers first. To do this take the node that is running the pod offline for at least 2-3 minutes. Verify that there is an event message similar to the one above is logged, and that the pod recovers and restarts normally with no loss of data. (Note that if the node is running many CSM for Resiliency protected pods, the node may need to be down longer for CSM for Resiliency to have time to evacuate all the protected pods.) From 196e26895b73245cbd2c257db84a0dabe33439bb Mon Sep 17 00:00:00 2001 From: Randeep Sharma Date: Wed, 17 Aug 2022 15:43:42 +0530 Subject: [PATCH 3/3] address comments --- content/docs/csidriver/installation/helm/isilon.md | 2 +- content/docs/resiliency/_index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md index 49736cf997..f0f38f9452 100644 --- a/content/docs/csidriver/installation/helm/isilon.md +++ b/content/docs/csidriver/installation/helm/isilon.md @@ -293,5 +293,5 @@ Starting CSI PowerScale v1.6, `dell-csi-helm-installer` will not create any Volu The existing volume snapshot class will be retained. *Upgrading from an older version of the driver*: -It is strongly recommended upgrading the earlier versions of CSI PowerScale to 1.6 or higher before upgrading to 2.32. +It is strongly recommended upgrading the earlier versions of CSI PowerScale to 1.6 or higher before upgrading to 2.3. diff --git a/content/docs/resiliency/_index.md b/content/docs/resiliency/_index.md index 9b930be5bd..e945bea855 100644 --- a/content/docs/resiliency/_index.md +++ b/content/docs/resiliency/_index.md @@ -146,7 +146,7 @@ pmtu3 podmontest-0 1/1 Running 0 3m6s CSM for Resiliency may also generate events if it is unable to clean up a pod for some reason. For example, it may not clean up a pod because the pod is still doing I/O to the array. - Similarly, the label selector for csi-powerscale and csi-unity would be as below respectively. + Similarly, the label selector for csi-powerscale and csi-unity would be as shown respectively. ``` labelSelector: {map[podmon.dellemc.com/driver:csi-isilon] labelSelector: {map[podmon.dellemc.com/driver:csi-unity]