Version and support matrix update for Unity XT (#366)

dell · Nov 25, 2022 · f8c499f · f8c499f
1 parent 389490d
commit f8c499f
Show file tree

Hide file tree

Showing 9 changed files with 48 additions and 46 deletions.
diff --git a/content/docs/csidriver/_index.md b/content/docs/csidriver/_index.md
@@ -16,12 +16,12 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 {{<table "table table-striped table-bordered table-sm">}}
 |               | PowerMax         | PowerFlex           | Unity XT         | PowerScale        | PowerStore       |
 |---------------|:----------------:|:-------------------:|:----------------:|:-----------------:|:----------------:|
-| Kubernetes    | 1.23, 1.24, 1.25 | 1.22, 1.23, 1.24    | 1.22, 1.23, 1.24 | 1.22, 1.23, 1.24  | 1.23, 1.24, 1.25 |
+| Kubernetes    | 1.23, 1.24, 1.25 | 1.22, 1.23, 1.24    | 1.23, 1.24, 1.25 | 1.22, 1.23, 1.24  | 1.23, 1.24, 1.25 |
 | RHEL          |     7.x,8.x      |     7.x,8.x         |     7.x,8.x      |     7.x,8.x       |     7.x,8.x      |
 | Ubuntu        |       20.04      |       20.04         |  18.04, 20.04    | 18.04, 20.04      |        20.04     |
 | CentOS        |     7.8, 7.9     |      7.8, 7.9       |     7.8, 7.9     |      7.8, 7.9     |     7.8, 7.9     |
 | SLES          |        15SP3     |        15SP3        |       15SP3      |         15SP3     |       15SP3      |
-| Red Hat OpenShift | 4.10, 4.10 EUS, 4.11 | 4.9, 4.10, 4.10 EUS | 4.9, 4.10, 4.10 EUS | 4.9, 4.10, 4.10 EUS | 4.9, 4.10, 4.10 EUS |
+| Red Hat OpenShift | 4.10, 4.10 EUS, 4.11 | 4.9, 4.10, 4.10 EUS | 4.10, 4.10 EUS, 4.11 | 4.9, 4.10, 4.10 EUS | 4.9, 4.10, 4.10 EUS |
 | Mirantis Kubernetes Engine | 3.5.x |      3.5.x        |       3.5.x      |        3.5.x      |        3.5.x     |
 | Google Anthos |        1.12       |          1.12        |        no        |         1.12       |        1.12       |
 | VMware Tanzu  |        no        |          no         |        NFS       |         NFS       |      NFS,iSCSI         |
@@ -33,7 +33,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 {{<table "table table-striped table-bordered table-sm">}}
 | Features                 | PowerMax | PowerFlex | Unity XT  | PowerScale | PowerStore |
 |--------------------------|:--------:|:---------:|:---------:|:----------:|:----------:|
-| CSI Driver version       | 2.4.0    | 2.4.0     | 2.4.0     | 2.4.0      | 2.4.0      |
+| CSI Driver version       | 2.4.0    | 2.4.0     | 2.5.0     | 2.4.0      | 2.4.0      |
 | Static Provisioning      | yes      | yes       | yes       | yes        | yes        |
 | Dynamic Provisioning     | yes      | yes       | yes       | yes        | yes        |
 | Expand Persistent Volume | yes      | yes       | yes       | yes        | yes        |

diff --git a/content/docs/csidriver/installation/helm/unity.md b/content/docs/csidriver/installation/helm/unity.md
@@ -88,7 +88,7 @@ Install CSI Driver for Unity XT using this procedure.
 
 *Before you begin*
 
- * You must have the downloaded files, including the Helm chart from the source [git repository](https://github.com/dell/csi-unity) with the command ```git clone -b v2.4.0 https://github.com/dell/csi-unity.git```, as a pre-requisite for running this procedure.
+ * You must have the downloaded files, including the Helm chart from the source [git repository](https://github.com/dell/csi-unity) with the command ```git clone -b v2.5.0 https://github.com/dell/csi-unity.git```, as a pre-requisite for running this procedure.
  * In the top-level dell-csi-helm-installer directory, there should be two scripts, `csi-install.sh` and `csi-uninstall.sh`.
  * Ensure _unity_ namespace exists in Kubernetes cluster. Use the `kubectl create namespace unity` command to create the namespace if the namespace is not present.
 
@@ -102,7 +102,7 @@ Procedure
       * ArrayId corresponds to the serial number of Unity XT array.
       * Unity XT Array username must have role as Storage Administrator to be able to perform CRUD operations.
       * If the user is using complex K8s version like "v1.21.3-mirantis-1", use below kubeVersion check in helm/csi-unity/Chart.yaml file.
-            kubeVersion: ">= 1.21.0-0 < 1.25.0-0"
+            kubeVersion: ">= 1.21.0-0 < 1.26.0-0"
 
 2. Copy the `helm/csi-unity/values.yaml` into a file named `myvalues.yaml` in the same directory of `csi-install.sh`, to customize settings for installation.
 
@@ -283,64 +283,65 @@ Procedure
     A successful installation must display messages that look similar to the following samples:
     ```
     ------------------------------------------------------
-    > Installing CSI Driver: csi-unity on 1.22
+    > Installing CSI Driver: csi-unity on 1.25
     ------------------------------------------------------
     ------------------------------------------------------
     > Checking to see if CSI Driver is already installed
     ------------------------------------------------------
     ------------------------------------------------------
     > Verifying Kubernetes and driver configuration
     ------------------------------------------------------
-    |- Kubernetes Version: 1.22
+    |- Kubernetes Version: 1.25
     |
     |- Driver: csi-unity                                                
     |
     |- Verifying Kubernetes version                                     
+      |
+      |--> Verifying minimum Kubernetes version                         Success
+      |
+      |--> Verifying maximum Kubernetes version                         Success
     |
-    |--> Verifying minimum Kubernetes version                         Success
+    |- Verifying that required namespaces have been created             Success
     |
-    |--> Verifying maximum Kubernetes version                         Success
+    |- Verifying that required secrets have been created                Success
     |
-    |- Verifying that required namespaces have been created           Success
-    |
-    |- Verifying that required secrets have been created              Success
-    |
-    |- Verifying that optional secrets have been created              Success
-    |
-    |- Verifying alpha snapshot resources                               
-    |
-    |--> Verifying that alpha snapshot CRDs are not installed         Success
+    |- Verifying that optional secrets have been created                Success
+      |
+      |- Verifying alpha snapshot resources
+      |
+      |--> Verifying that alpha snapshot CRDs are not installed         Success
     |
     |- Verifying sshpass installation..                                 |
-    |- Verifying iSCSI installation                                     
+    |- Verifying iSCSI installation
     Enter the root password of 10.**.**.**:
     
     Enter the root password of 10.**.**.**:
     Success
     |
-    |- Verifying snapshot support                                       
-    |
-    |--> Verifying that snapshot CRDs are available                   Success
-    |
-    |--> Verifying that the snapshot controller is available          Success
+    |- Verifying snapshot support
+      |
+      |--> Verifying that snapshot CRDs are available                   Success
+      |
+      |--> Verifying that the snapshot controller is available          Success
     |
-    |- Verifying helm version                                         Success
+    |- Verifying helm version                                           Success
     |
-    |- Verifying helm values version                                  Success
-    
+    |- Verifying helm values version                                    Success
+
     ------------------------------------------------------
     > Verification Complete - Success
     ------------------------------------------------------
     |
-    |- Installing Driver                                              Success
-    |
-    |--> Waiting for Deployment unity-controller to be ready          Success
-    |
-    |--> Waiting for DaemonSet unity-node to be ready                 Success
+    |- Installing Driver                                                Success
+      |
+      |--> Waiting for Deployment unity-controller to be ready          Success
+      |
+      |--> Waiting for DaemonSet unity-node to be ready                 Success
     ------------------------------------------------------
     > Operation complete
     ------------------------------------------------------
     ```
+
     Results:
 
     At the end of the script unity-controller Deployment and DaemonSet unity-node will be ready, execute command `kubectl get pods -n unity` to get the status of the pods and you will see the following:

diff --git a/content/docs/csidriver/installation/operator/_index.md b/content/docs/csidriver/installation/operator/_index.md
@@ -62,6 +62,7 @@ If you have installed an old version of the `dell-csi-operator` which was availa
 | CSI Unity XT       | 2.2.0     | v2.2.0         | 1.21, 1.22, 1.23     | 4.8, 4.8 EUS, 4.9     |
 | CSI Unity XT       | 2.3.0     | v2.3.0         | 1.22, 1.23, 1.24     | 4.9, 4.10, 4.10 EUS   |
 | CSI Unity XT       | 2.4.0     | v2.4.0         | 1.22, 1.23, 1.24     | 4.9, 4.10, 4.10 EUS   |
+| CSI Unity XT       | 2.5.0     | v2.5.0         | 1.23, 1.24, 1.25     | 4.10, 4.10 EUS, 4.11  |
 | CSI PowerStore     | 2.2.0     | v2.2.0         | 1.21, 1.22, 1.23     | 4.8, 4.8 EUS, 4.9     |
 | CSI PowerStore     | 2.3.0     | v2.3.0         | 1.22, 1.23, 1.24     | 4.9, 4.10, 4.10 EUS   |
 | CSI PowerStore     | 2.4.0     | v2.4.0         | 1.22, 1.23, 1.24     | 4.9, 4.10, 4.10 EUS   |
@@ -97,7 +98,7 @@ $ kubectl create configmap dell-csi-operator-config --from-file config.tar.gz -n
 #### Steps
 
 >**Skip step 1 for "offline bundle installation" and continue using the workspace created by untar of dell-csi-operator-bundle.tar.gz.**
-1. Clone and checkout the required dell-csi-operator version using `git clone -b v1.9.0 https://github.com/dell/dell-csi-operator.git`.
+1. Clone and checkout the required dell-csi-operator version using `git clone -b v1.10.0 https://github.com/dell/dell-csi-operator.git`.
 2. cd dell-csi-operator
 3. Run `bash scripts/install.sh` to install the operator.
 >NOTE: Dell CSI Operator version 1.4.0 and higher would install to the 'dell-csi-operator' namespace by default.
@@ -126,7 +127,7 @@ For installation of the supported drivers, a `CustomResource` has to be created
 ### Pre-requisites for upstream Kubernetes Clusters
 On upstream Kubernetes clusters, make sure to install
 * VolumeSnapshot CRDs
-  * On clusters running v1.22,v1.23 & v1.24, make sure to install v1 VolumeSnapshot CRDs
+  * On clusters running v1.23,v1.24 & v1.25, make sure to install v1 VolumeSnapshot CRDs
 * External Volume Snapshot Controller with the correct version
 
 ### Pre-requisites for Red Hat OpenShift Clusters
@@ -274,7 +275,7 @@ The below notes explain some of the general items to take care of.
 1. If you are trying to upgrade the CSI driver from an older version, make sure to modify the _configVersion_ field if required.
    ```yaml
       driver:
-        configVersion: v2.4.0
+        configVersion: v2.5.0
    ```
 2. Volume Health Monitoring feature is optional and by default this feature is disabled for drivers when installed via operator.
    To enable this feature, we will have to modify the below block while upgrading the driver.To get the volume health state add 

diff --git a/content/docs/csidriver/installation/operator/unity.md b/content/docs/csidriver/installation/operator/unity.md
@@ -97,12 +97,12 @@ metadata:
   namespace: test-unity
 spec:
   driver:
-    configVersion: v2.4.0
+    configVersion: v2.5.0
     replicas: 2
     dnsPolicy: ClusterFirstWithHostNet
     forceUpdate: false
     common:
-      image: "dellemc/csi-unity:v2.4.0"
+      image: "dellemc/csi-unity:v2.5.0"
       imagePullPolicy: IfNotPresent
     sideCars:
       - name: provisioner

diff --git a/content/docs/csidriver/release/operator.md b/content/docs/csidriver/release/operator.md
@@ -3,9 +3,9 @@ title: Operator
 description: Release notes for Dell CSI Operator
 ---
 
-## Release Notes - Dell CSI Operator 1.9.0
+## Release Notes - Dell CSI Operator 1.10.0
 
->**Note:** There will be a delay in certification of Dell CSI Operator 1.9.0 and it will not be available for download from the Red Hat OpenShift certified catalog right away. The operator will still be available for download from the Red Hat OpenShift Community Catalog soon after the 1.9.0 release.
+>**Note:** There will be a delay in certification of Dell CSI Operator 1.10.0 and it will not be available for download from the Red Hat OpenShift certified catalog right away. The operator will still be available for download from the Red Hat OpenShift Community Catalog soon after the 1.10.0 release.
 
 ### Fixed Issues
 There are no fixed issues in this release.

diff --git a/content/docs/csidriver/release/unity.md b/content/docs/csidriver/release/unity.md
@@ -3,11 +3,11 @@ title: Unity XT
 description: Release notes for Unity XT CSI driver
 ---
 
-## Release Notes - CSI Unity XT v2.4.0
+## Release Notes - CSI Unity XT v2.5.0
 
 ### New Features/Changes
 
-- [Added support to configure fsGroupPolicy](https://github.com/dell/csm/issues/361)
+- [Added support to kubernetes 1.25](https://github.com/dell/csm/issues/478)
 
 ### Known Issues
 

diff --git a/content/docs/csidriver/troubleshooting/unity.md b/content/docs/csidriver/troubleshooting/unity.md
@@ -12,6 +12,6 @@ description: Troubleshooting Unity XT Driver
 | Dynamic array detection will not work in Topology based environment | Whenever a new array is added or removed, then the driver controller and node pod should be restarted with command **kubectl get pods -n unity --no-headers=true \| awk '/unity-/{print $1}'\| xargs kubectl delete -n unity pod** when **topology-based storage classes are used**. For dynamic array addition without topology, the driver will detect the newly added or removed arrays automatically|
 | If source PVC is deleted when cloned PVC exists, then source PVC will be deleted in the cluster but on array, it will still be present and marked for deletion. | All the cloned PVC should be deleted in order to delete the source PVC from the array. |
 | PVC creation fails on a fresh cluster with **iSCSI** and **NFS** protocols alone enabled with error **failed to provision volume with StorageClass "unity-iscsi": error generating accessibility requirements: no available topology found**. | This is because iSCSI initiator login takes longer than the node pod startup time. This can be overcome by bouncing the node pods in the cluster using the below command the driver pods with **kubectl get pods -n unity --no-headers=true \| awk '/unity-/{print $1}'\| xargs kubectl delete -n unity pod** |
-| Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.21.0 < 1.25.0 which is incompatible with Kubernetes V1.21.11-mirantis-1` | If you are using an extended Kubernetes version, please see the helm Chart at `helm/csi-unity/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. *Please note* that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported. |
+| Driver install or upgrade fails because of an incompatible Kubernetes version, even though the version seems to be within the range of compatibility. For example: `Error: UPGRADE FAILED: chart requires kubeVersion: >= 1.21.0 < 1.26.0 which is incompatible with Kubernetes V1.21.11-mirantis-1` | If you are using an extended Kubernetes version, please see the helm Chart at `helm/csi-unity/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. *Please note* that this is not meant to be used to enable the use of pre-release alpha and beta versions, which is not supported. |
 | When a node goes down, the block volumes attached to the node cannot be attached to another node | 1. Force delete the pod running on the node that went down <br /> 2. Delete the VolumeAttachment to the node that went down. <br /> Now the volume can be attached to the new node. |
 | Volume attachments are not removed after deleting the pods | If you are using Kubernetes version < 1.24, assign the volume name prefix such that the total length of volume name created in array should be more than 68 bytes. From Kubernetes version >= 1.24, this issue is taken care.<br /> Please refer the kubernetes issue https://github.com/kubernetes/kubernetes/issues/97230 which has detailed explanation. |
diff --git a/content/docs/csidriver/upgradation/drivers/operator.md b/content/docs/csidriver/upgradation/drivers/operator.md
@@ -13,7 +13,7 @@ Dell CSI Operator can be upgraded based on the supported platforms in one of the
 
 
 ### Using Installation Script
-1. Clone and checkout the required dell-csi-operator version using `git clone -b v1.9.0 https://github.com/dell/dell-csi-operator.git`.
+1. Clone and checkout the required dell-csi-operator version using `git clone -b v1.10.0 https://github.com/dell/dell-csi-operator.git`.
 2. cd dell-csi-operator
 3. Execute `bash scripts/install.sh --upgrade`  . This command will install the latest version of the operator.
 >Note: Dell CSI Operator version 1.4.0 and higher would install to the 'dell-csi-operator' namespace by default.
@@ -25,5 +25,5 @@ The `Update approval` (**`InstallPlan`** in OLM terms) strategy plays a role whi
   - If the **`Update approval`** is set to `Automatic`, OpenShift automatically detects whenever the latest version of dell-csi-operator is available in the **`Operator hub`**, and upgrades it to the latest available version.
   - If the upgrade policy is set to `Manual`, OpenShift notifies of an available upgrade. This notification can be viewed by the user in the **`Installed Operators`** section of the OpenShift console. Clicking on the hyperlink to `Approve` the installation would trigger the dell-csi-operator upgrade process.
 
-**NOTE**: The recommended version of OLM for Upstream Kubernetes is **`v0.18.3`** when upgrading operator to `v1.9.0`.
+**NOTE**: The recommended version of OLM for Upstream Kubernetes is **`v0.18.3`** when upgrading operator to `v1.10.0`.
 
diff --git a/content/docs/csidriver/upgradation/drivers/unity.md b/content/docs/csidriver/upgradation/drivers/unity.md
@@ -20,9 +20,9 @@ You can upgrade the CSI Driver for Dell Unity XT using Helm or Dell CSI Operator
 
 Preparing myvalues.yaml is the same as explained in the install section.
 
-To upgrade the driver from csi-unity v2.3.0 to csi-unity v2.4.0
+To upgrade the driver from csi-unity v2.4.0 to csi-unity v2.5.0
 
-1. Get the latest csi-unity v2.4.0 code from Github using using `git clone -b v2.4.0 https://github.com/dell/csi-unity.git`.
+1. Get the latest csi-unity v2.5.0 code from Github using using `git clone -b v2.5.0 https://github.com/dell/csi-unity.git`.
 2. Copy the helm/csi-unity/values.yaml to the new location csi-unity/dell-csi-helm-installer and rename it to myvalues.yaml. Customize settings for installation by editing myvalues.yaml as needed.
 3. Navigate to csi-unity/dell-csi-hem-installer folder and execute this command:
   `./csi-install.sh --namespace unity --values ./myvalues.yaml --upgrade`