dell · suryagupta4 · Apr 4, 2024 · Mar 29, 2024 · Apr 3, 2024 · Apr 4, 2024
@@ -172,7 +172,7 @@ enable = false
 #	icon = "fa fa-envelope"
 #        desc = "Discuss development issues around the project"
 [[params.versions]]
-  version = "Current(v1.10.0)"
+  version = "Current(v1.10.1)"
   url = "https://dell.github.io/csm-docs/docs/"
 
 [[params.versions]]

@@ -15,9 +15,6 @@ Description: >
 
 
 
-
-
-
 ### New Features/Changes
 
 - [#926 - [FEATURE]: Fixing the linting, formatting and vetting issues](https://github.com/dell/csm/issues/926)
@@ -26,5 +23,6 @@ Description: >
 
 
 ### Known Issues
-
-There are no known issues in this release.
+| Issue | Workaround |
+|-------|------------|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|
@@ -24,6 +24,7 @@ description: Release notes for PowerFlex CSI driver
 - [#1140 - [BUG]: Cert-csi tests are not reporting the passed testcases in K8S E2E tests ](https://github.com/dell/csm/issues/1140)
 - [#1163 - [BUG]: Resource quota bypass](https://github.com/dell/csm/issues/1163)
 - [#1174 - [BUG]: Kubelet Configuration Directory setting should not have a comment about default value being None](https://github.com/dell/csm/issues/1174)
+- [#1210 - [BUG]: Helm deployment of PowerFlex driver is failing](https://github.com/dell/csm/issues/1210)
 
 ### Known Issues
 
@@ -38,6 +39,8 @@ A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the erro
 | The PowerFlex Dockerfile is incorrectly labeling the version as 2.7.0 for the 2.8.0 version. | Describe the driver pod using ```kubectl describe pod $podname -n vxflexos``` to ensure v2.8.0 is installed. |
 | Resource quotas may not work properly with the CSI PowerFlex driver. PowerFlex is only able to assign storage in 8Gi chunks, so if a create volume call is made with a size not divisible by 8Gi, CSI-PowerFlex will round up to the next 8Gi boundary when it provisions storage -- however, the resource quota will not record this size but rather the original size in the create request. This means that, for example, if a 10Gi resource quota is set, and a user provisions 10 1Gi PVCs, 80Gi of storage will actually be allocated, which is well over the amount specified in the resource quota. | For now, users should only provision volumes in 8Gi-divisible chunks if they want to use resource quotas. |
 
+
 ### Note:
 
 - Support for Kubernetes alpha features like Volume Health Monitoring and RWOP (ReadWriteOncePod) access mode will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters.
+- For fixing [#1210 - [BUG]: Helm deployment of PowerFlex driver is failing](https://github.com/dell/csm/issues/1210), a new helm-chart has been released. In order to install this helm chart, we need to pass the flag `--helm-charts-version` during helm installation and flag `-v` during offline bundle installation with value `csi-vxflexos-2.10.1`.
@@ -1,4 +1,4 @@
-csmVersion=1.10.0
+csmVersion=1.10.1
 imageRepository=dellemc
 controllerCount=1
 nodeSelectorLabel=node-role.kubernetes.io/control-plane:

@@ -93,7 +93,7 @@
                         <option value="1.7.0">CSM 1.7</option>
                         <option value="1.8.0">CSM 1.8</option>                        
                         <option value="1.9.3">CSM 1.9</option>
-                        <option value="1.10.0" selected>CSM 1.10</option>
+                        <option value="1.10.1" selected>CSM 1.10.1</option>
                       </select>
                     </div>
                   </div>

@@ -43,7 +43,7 @@ const CONSTANTS = {
 	CSM_HELM_V170: "1.0.0",
 	CSM_HELM_V180: "1.1.0",
 	CSM_HELM_V190: "1.2.1",
-	CSM_HELM_V1100: "1.3.0",
+	CSM_HELM_V1101: "1.3.1",
 	HELM_TAINTS: `
      - key: "$KEY"
        operator: "Exists"

@@ -472,11 +472,11 @@ function displayCommands(releaseNameValue, commandTitleValue, commandNoteValue,
 		case "1.9.3":
 			helmChartVersion = CONSTANTS.CSM_HELM_V193;
 			break;
-		case "1.10.0":
-			helmChartVersion = CONSTANTS.CSM_HELM_V1100;
+		case "1.10.1":
+			helmChartVersion = CONSTANTS.CSM_HELM_V1101;
 			break;
 		default:
-			helmChartVersion = CONSTANTS.CSM_HELM_V1100;
+			helmChartVersion = CONSTANTS.CSM_HELM_V1101;
 			break;
 	}
 	$("#command-text-area").show();

@@ -81,7 +81,7 @@ kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/relea
    | enabled | Enable/Disable deployment of cert-manager. Set to false if you already have cert-manager installed. | No | true |
 
 >__Note__:  
-> - If you specify `REDIS_STORAGE_CLASS`, the storage class must NOT be provisioned by the Dell CSI Driver to be configured with this installation of CSM Authorization.
+> - If you specify `REDIS_STORAGE_CLASS`, the storage class must NOT be provisioned by the Dell CSI Driver to be configured with this installation of CSM Authorization. 
 
 **Optional:**
 To enable reporting of trace data with [Zipkin](https://zipkin.io/), use the `csm-config-params` configMap in the sample CR or dynamically by editing the configMap.

@@ -31,3 +31,4 @@ Description: >
 | Issue | Workaround |
 |-------|------------|
 | When CSM Operator creates a deployment that includes secrets (e.g., application-mobility, observability, cert-manager, velero), these secrets are not deleted on uninstall and will be left behind. For example, the `karavi-topology-tls`, `otel-collector-tls`, and `cert-manager-webhook-ca` secrets will not be deleted. | This should not cause any issues on the system, but all secrets present on the cluster can be found with `kubectl get secrets -A`, and any unwanted secrets can be deleted with `kubectl delete secret -n <secret-namespace> <secret-name>`|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|
@@ -213,10 +213,11 @@ Use the below command to replace or update the secret:
 | skipCertificateValidation | A boolean that enables/disables certificate validation of the csm-authorization proxy server. | No | true |
 
 
-10. Install the driver using `csi-install.sh` bash script by running `cd dell-csi-helm-installer && ./csi-install.sh --namespace vxflexos --values myvalues.yaml`. You may modify the release name with the `--release` arg. If arg is not provided, release will be named `vxflexos` by default. 
+10. Install the driver using `csi-install.sh` bash script by running `cd dell-csi-helm-installer && ./csi-install.sh --namespace vxflexos --values myvalues.yaml --helm-charts-version csi-vxflexos-2.10.1`. You may modify the release name with the `--release` arg. If arg is not provided, release will be named `vxflexos` by default. 
 Alternatively, to do a helm install solely with Helm charts (without shell scripts), refer to `helm/README.md`.
 
  *NOTE:*
+- If you do not specify the `--helm-charts-version` flag, by default the `csi-install.sh` script will clone the version of the helm chart that is specified in the driver's [csi-install.sh](https://github.com/dell/csi-powerflex/blob/main/dell-csi-helm-installer/csi-install.sh#L24) file. If you wish to install the driver using a different version of the helm chart, you need to include this flag. Also, remember to delete the `helm-charts` repository present in the `csi-powerflex` directory if it was cloned before.
 - For detailed instructions on how to run the install scripts, refer to the README.md  in the dell-csi-helm-installer folder.
 - Install script will validate MDM IP(s) in `vxflexos-config` secret and creates a new field consumed by the init container and sdc-monitor container
 - This install script also runs the `verify.sh` script. You will be prompted to enter the credentials for each of the Kubernetes nodes. 

@@ -10,23 +10,24 @@ Description: Upgrade PowerFlex CSI driver
 
 You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSM Operator.
 
-## Update Driver from v2.9.0 to v2.10.0 using Helm
+## Update Driver from v2.9.2 to v2.10.0 using Helm
 **Steps**
 1. Run `git clone -b v2.10.0 https://github.com/dell/csi-powerflex.git` to clone the git repository and get the v2.10.0 driver.
 2. You need to create secret.yaml with the configuration of your system.
 3. Update myvalues file as needed.
 4. Run the `csi-install` script with the option _\-\-upgrade_ by running: 
    ```bash
 
-   cd ../dell-csi-helm-installer && ./csi-install.sh --namespace vxflexos --values ./myvalues.yaml --upgrade
+   cd ../dell-csi-helm-installer && ./csi-install.sh --namespace vxflexos --values ./myvalues.yaml --helm-charts-version csi-vxflexos-2.10.1 --upgrade
    ```
 
 *NOTE:*
+- If you do not specify the `--helm-charts-version` flag, by default the `csi-install.sh` script will clone the version of the helm chart that is specified in the driver's [csi-install.sh](https://github.com/dell/csi-powerflex/blob/main/dell-csi-helm-installer/csi-install.sh#L24) file. If you wish to upgrade the driver using a different version of the helm chart, you need to include this flag. Also, remember to delete the `helm-charts` repository present in the `csi-powerflex` directory if it was cloned before.
 - If you are upgrading from a driver version that was installed using Helm v2, ensure that you install Helm3 before installing the driver.
 - To update any installation parameter after the driver has been installed, change the `myvalues.yaml` file and run the install script with the option _\-\-upgrade_, for example: 
   ```bash
 
-  ./csi-install.sh --namespace vxflexos --values ./myvalues.yaml --upgrade
+  ./csi-install.sh --namespace vxflexos --values ./myvalues.yaml --helm-charts-version csi-vxflexos-2.10.1 --upgrade
   ```
 - The logging configuration from v1.5 will not work in v2.1, since the log configuration parameters are now set in the myvalues.yaml file located at dell-csi-helm-installer/myvalues.yaml. Please set the logging configuration parameters in the myvalues.yaml file.
 

@@ -10,7 +10,7 @@ weight: 1
 {{<table "table table-striped table-bordered table-sm">}}
 | Platform      | Version          | OS Dependencies          |
 |---------------|:----------------:|:------------------------:|
-| PowerMax    | PowerMax 2500/8500 PowerMaxOS 10 (6079)<br>PowerMaxOS 10.0.1 (6079)<br>PowerMaxOS 10.1 (6079)<br>PowerMax 2000/8000 - 5978.711.xxx<br>5978.479.xxx<br>Unisphere 10.0,10.0.1,10.1 | iscsi-initiator-utils<br>multipathd or powerpath<br>nvme-cli<br>nfs-utils |
+| PowerMax    | PowerMax 2500/8500 PowerMaxOS 10 (6079)<br>PowerMaxOS 10.0.1 (6079)<br>PowerMaxOS 10.1 (6079)<br>PowerMax 2000/8000 - 5978.711.711, 5978.714.714<br>5978.479.479<br>Unisphere 10.0,10.0.1,10.1 | iscsi-initiator-utils<br>multipathd or powerpath<br>nvme-cli<br>nfs-utils |
 | PowerFlex | 3.6.x, 4.0.x, 4.5.x | [SDC](https://www.dell.com/support/home/en-us/product-support/product/scaleio/drivers)|
 | Unity XT | 5.1.x, 5.2.x, 5.3.0 | iscsi-initiator-utils<br>multipathd<br>nfs-utils |
 | PowerScale | OneFS 9.3, 9.4, 9.5.0.x (x >= 5) | nfs-utils |

@@ -27,5 +27,6 @@ Description: >
 
 
 ### Known Issues
-
-There are no known issues in this release.
+| Issue | Workaround |
+|-------|------------|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|
@@ -46,6 +46,7 @@ Description: >
 |-------|------------|
 | The status field of a csm object as deployed by CSM Operator may, in limited cases, display an incorrect status for a deployment. | As a workaround, the health of the deployment can be determined by checking the health of the pods. |
 | When CSM Operator creates a deployment that includes secrets (e.g., application-mobility, observability, cert-manager, velero), these secrets are not deleted on uninstall and will be left behind. For example, the `karavi-topology-tls`, `otel-collector-tls`, and `cert-manager-webhook-ca` secrets will not be deleted. | This should not cause any issues on the system, but all secrets present on the cluster can be found with `kubectl get secrets -A`, and any unwanted secrets can be deleted with `kubectl delete secret -n <secret-namespace> <secret-name>`|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|
 | The images of sideCars are currently missing in the sample YAMLs in the offline bundle. As a consequence, the csm-operator is pulling them from registry.k8s.io. | We recommend manually updating the images of sideCars in the sample YAML file, for example, `storage_csm_powerflex_v291.yaml`, before proceeding with the driver installation. Here is an example snippet for the sideCars section in the YAML file:
 
   ```yaml

@@ -20,5 +20,6 @@ Description: >
 - [#916 - [BUG]: Remove references to deprecated io/ioutil package](https://github.com/dell/csm/issues/916)
 
 ### Known Issues
-
-There are no known issues in this release.
+| Issue | Workaround |
+|-------|------------|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|
@@ -24,4 +24,6 @@ Description: >
 - [#898 - [BUG]: Unable to pull podmon image from local repository for offline install](https://github.com/dell/csm/issues/898)
 
 ### Known Issues
-There are no known issues in this release.
+| Issue | Workaround |
+|-------|------------|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|
@@ -21,3 +21,7 @@ Description: >
 - Authorization RPM installation should use nogpgcheck for k3s-selinux package. ([#772](https://github.com/dell/csm/issues/772))
 - CSM Authorization - karavictl generate token should output valid yaml. ([#767](https://github.com/dell/csm/issues/767))
 
+### Known Issues
+| Issue | Workaround |
+|-------|------------|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|
@@ -27,4 +27,6 @@ CSM 1.7.1 is applicable to helm based installations of PowerFlex driver.
 
 
 ### Known Issues
-There are no known issues in this release.
+| Issue | Workaround |
+|-------|------------|
+| CSM Operator does not support dynamic namespaces for Authorization. Despite successful installation in a namespace other than "authorization", errors may arise during volume creation. | Use the default namespace "authorization" for installing Authorization using CSM Operator|