From 108a5ece696b2e5c8ca5a76cc4922bb8abce931e Mon Sep 17 00:00:00 2001 From: Aaron Tye Date: Fri, 29 Mar 2024 07:28:23 -0400 Subject: [PATCH 01/49] Add notes about non-default namespace for Authorization and Operator (#1044) --- .../deployment/csmoperator/modules/authorization.md | 11 +++++++++-- 1 file changed, 9 insertions(+), 2 deletions(-) diff --git a/content/docs/deployment/csmoperator/modules/authorization.md b/content/docs/deployment/csmoperator/modules/authorization.md index 6aaddeb2e3..2db1d421a4 100644 --- a/content/docs/deployment/csmoperator/modules/authorization.md +++ b/content/docs/deployment/csmoperator/modules/authorization.md @@ -60,6 +60,9 @@ kubectl apply --validate=false -f https://github.com/jetstack/cert-manager/relea kubectl create -f samples/authorization/karavi-storage-secret.yaml ``` +>__Note__: +> - If you are installing CSM Authorization in a different namespace than `authorization`, edit the `namespace` field in this file to your namespace. + ### Install CSM Authorization Proxy Server 1. Follow all the [prerequisites](#prerequisite). @@ -81,7 +84,8 @@ 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. +> - If you are installing CSM Authorization in a different namespace than `authorization`, edit the `namespace` fields in this file to your namespace. **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. @@ -119,11 +123,14 @@ To enable reporting of trace data with [Zipkin](https://zipkin.io/), use the `cs kubectl create -f ``` +>__Note__: +> - If you are installing CSM Authorization in a different namespace than `authorization`, edit the `namespace` field in this file to your namespace. + ### Verify Installation of the CSM Authorization Proxy Server Once the Authorization CR is created, you can verify the installation as mentioned below: ```bash - kubectl describe csm/ -n + kubectl describe csm/ -n authorization ``` ### Install Karavictl From 0f40a4d7038ff054c1b8691f73abd4e862989472 Mon Sep 17 00:00:00 2001 From: HarishH-DELL <109663924+HarishH-DELL@users.noreply.github.com> Date: Fri, 29 Mar 2024 18:04:23 +0530 Subject: [PATCH 02/49] Snapshot ingestion procedure for CSI Unity Driver (#1043) * Snapshot ingestion procedure for CSI Unity Driver * Addressed review comments * Review commnets addressed * Review commnets addressed --- content/docs/csidriver/features/unity.md | 60 ++++++++++++++++++++++++ 1 file changed, 60 insertions(+) diff --git a/content/docs/csidriver/features/unity.md b/content/docs/csidriver/features/unity.md index 188f5a3232..087544f5eb 100644 --- a/content/docs/csidriver/features/unity.md +++ b/content/docs/csidriver/features/unity.md @@ -211,6 +211,66 @@ spec: >The Kubernetes Volume Expansion feature can only be used to increase the size of a volume. It cannot be used to shrink a volume. + +## Snapshot Ingestion procedure + +The Snapshot Ingestion procedure outlines the steps required to effectively integrate existing snapshots from Unity XT into your Kubernetes cluster. This procedure ensures the seamless acquisition, processing, and utilization of snapshots. +Below are the key steps involved + +1. Create a snapshot for existing volume using Unisphere + +2. Create a VolumeSnapshotContent as explained below + + ```yaml + apiVersion: snapshot.storage.k8s.io/v1 + kind: VolumeSnapshotContent + metadata: + name: snap1-content + spec: + deletionPolicy: Delete + driver: csi-unity.dellemc.com + volumeSnapshotClassName: unity-snapclass + source: + snapshotHandle: snap1--- + volumeSnapshotRef: + name: snap1 + namespace: unity + ``` +>Example snapshot handle format: snap1-FC-apm00123456789-3865491234567 + +3. Create a VolumeSnapshot as explained below + + ```yaml + apiVersion: snapshot.storage.k8s.io/v1 + kind: VolumeSnapshot + metadata: + name: snap1 + namespace: unity + spec: + volumeSnapshotClassName: unity-snapclass + source: + volumeSnapshotContentName: snap1-content + ``` + +4. Create a PersistentVolumeClaim as explained below +```yaml + apiVersion: v1 + kind: PersistentVolumeClaim + metadata: + name: restore-pvc-from-snap + spec: + storageClassName: unity-nfs + dataSource: + name: snap1 + kind: VolumeSnapshot + apiGroup: snapshot.storage.k8s.io + accessModes: + - ReadWriteOnce + resources: + requests: + storage: 5Gi +``` + ## Raw block support The CSI Unity XT driver supports Raw Block Volumes. From 1c80ca6acaf86d392fbd9a2779f7246b791eeb53 Mon Sep 17 00:00:00 2001 From: boyamurthy <92081029+boyamurthy@users.noreply.github.com> Date: Fri, 5 Apr 2024 17:45:06 +0530 Subject: [PATCH 03/49] Adding helm-charts-version flag (#1059) --- .../docs/deployment/helm/drivers/installation/powermax.md | 3 ++- .../docs/deployment/helm/drivers/installation/powerstore.md | 3 ++- content/docs/deployment/helm/drivers/upgrade/powermax.md | 3 ++- content/docs/deployment/helm/drivers/upgrade/powerstore.md | 5 +++-- content/v1/csidriver/installation/helm/powermax.md | 3 ++- content/v1/csidriver/installation/helm/powerstore.md | 3 ++- content/v1/csidriver/upgradation/drivers/powermax.md | 3 ++- content/v1/csidriver/upgradation/drivers/powerstore.md | 4 +++- content/v2/csidriver/installation/helm/powermax.md | 3 ++- content/v2/csidriver/installation/helm/powerstore.md | 3 ++- content/v2/csidriver/upgradation/drivers/powermax.md | 3 ++- content/v2/csidriver/upgradation/drivers/powerstore.md | 5 +++-- 12 files changed, 27 insertions(+), 14 deletions(-) diff --git a/content/docs/deployment/helm/drivers/installation/powermax.md b/content/docs/deployment/helm/drivers/installation/powermax.md index 1c3a2e7c08..43faee391d 100644 --- a/content/docs/deployment/helm/drivers/installation/powermax.md +++ b/content/docs/deployment/helm/drivers/installation/powermax.md @@ -346,7 +346,7 @@ CRDs should be configured during replication prepare stage with repctl as descri 8. Install the driver using `csi-install.sh` bash script by running ```bash - cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml + cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --helm-charts-version ``` 9. Or you can also install the driver using standalone helm chart using the command ```bash @@ -354,6 +354,7 @@ CRDs should be configured during replication prepare stage with repctl as descri ``` *Note:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powermax/blob/main/dell-csi-helm-installer/csi-install.sh#L52) 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-powermax` directory if it was cloned before. - For detailed instructions on how to run the install scripts, see the readme document in the dell-csi-helm-installer folder. - There are a set of samples provided [here](#sample-values-file) to help you configure the driver with reverse proxy - This script also runs the verify.sh script in the same directory. You will be prompted to enter the credentials for each of the Kubernetes nodes. The `verify.sh` script needs the credentials to check if the iSCSI initiators have been configured on all nodes. You can also skip the verification step by specifying the `--skip-verify-node` option diff --git a/content/docs/deployment/helm/drivers/installation/powerstore.md b/content/docs/deployment/helm/drivers/installation/powerstore.md index 2bba421810..a392f1155e 100644 --- a/content/docs/deployment/helm/drivers/installation/powerstore.md +++ b/content/docs/deployment/helm/drivers/installation/powerstore.md @@ -249,11 +249,12 @@ CRDs should be configured during replication prepare stage with repctl as descri 8. Install the driver using `csi-install.sh` bash script by running ```bash - ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml + ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --helm-charts-version ``` - After that the driver should be installed, you can check the condition of driver pods by running `kubectl get all -n csi-powerstore` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerstore/blob/main/dell-csi-helm-installer/csi-install.sh#L13) 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-powerstore` directory if it was cloned before. - For detailed instructions on how to run the install scripts, refer to the readme document in the dell-csi-helm-installer folder. - By default, the driver scans available SCSI adapters and tries to register them with the storage array under the SCSI hostname using `node.nodeNamePrefix` and the ID read from the file pointed to by `node.nodeIDPath`. If an adapter is already registered with the storage under a different hostname, the adapter is not used by the driver. - A hostname the driver uses for registration of adapters is in the form `--`. By default, these are csi-node and the machine ID read from the file `/etc/machine-id`. diff --git a/content/docs/deployment/helm/drivers/upgrade/powermax.md b/content/docs/deployment/helm/drivers/upgrade/powermax.md index cbbf1881f6..74dbe06368 100644 --- a/content/docs/deployment/helm/drivers/upgrade/powermax.md +++ b/content/docs/deployment/helm/drivers/upgrade/powermax.md @@ -24,10 +24,11 @@ You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSM Operator. 3. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash - cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --upgrade + cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --upgrade --helm-charts-version ``` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powermax/blob/main/dell-csi-helm-installer/csi-install.sh#L52) 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-powermax` 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 `my-powermax-settings.yaml` file and run the install script with the option _\-\-upgrade_, for example: ```bash diff --git a/content/docs/deployment/helm/drivers/upgrade/powerstore.md b/content/docs/deployment/helm/drivers/upgrade/powerstore.md index 6603b304c0..3f91c1b937 100644 --- a/content/docs/deployment/helm/drivers/upgrade/powerstore.md +++ b/content/docs/deployment/helm/drivers/upgrade/powerstore.md @@ -42,9 +42,10 @@ Note: While upgrading the driver via helm, controllerCount variable in myvalues. 6. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash - ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade + ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade --helm-charts-version ``` - +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerstore/blob/main/dell-csi-helm-installer/csi-install.sh#L13) 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-powerstore` directory if it was cloned before. ## Upgrade using Dell CSM Operator: **Note:** Upgrading the Operator does not upgrade the CSI Driver. diff --git a/content/v1/csidriver/installation/helm/powermax.md b/content/v1/csidriver/installation/helm/powermax.md index 3a20bdf840..238222780c 100644 --- a/content/v1/csidriver/installation/helm/powermax.md +++ b/content/v1/csidriver/installation/helm/powermax.md @@ -346,7 +346,7 @@ CRDs should be configured during replication prepare stage with repctl as descri 8. Install the driver using `csi-install.sh` bash script by running ```bash - cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml + cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --helm-charts-version ``` 9. Or you can also install the driver using standalone helm chart using the command ```bash @@ -354,6 +354,7 @@ CRDs should be configured during replication prepare stage with repctl as descri ``` *Note:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powermax/blob/main/dell-csi-helm-installer/csi-install.sh#L52) 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-powermax` directory if it was cloned before. - For detailed instructions on how to run the install scripts, see the readme document in the dell-csi-helm-installer folder. - There are a set of samples provided [here](#sample-values-file) to help you configure the driver with reverse proxy - This script also runs the verify.sh script in the same directory. You will be prompted to enter the credentials for each of the Kubernetes nodes. The `verify.sh` script needs the credentials to check if the iSCSI initiators have been configured on all nodes. You can also skip the verification step by specifying the `--skip-verify-node` option diff --git a/content/v1/csidriver/installation/helm/powerstore.md b/content/v1/csidriver/installation/helm/powerstore.md index 8d6b272e53..7a2ebba1db 100644 --- a/content/v1/csidriver/installation/helm/powerstore.md +++ b/content/v1/csidriver/installation/helm/powerstore.md @@ -249,11 +249,12 @@ CRDs should be configured during replication prepare stage with repctl as descri 8. Install the driver using `csi-install.sh` bash script by running ```bash - ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml + ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --helm-charts-version ``` - After that the driver should be installed, you can check the condition of driver pods by running `kubectl get all -n csi-powerstore` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerstore/blob/main/dell-csi-helm-installer/csi-install.sh#L13) 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-powerstore` directory if it was cloned before. - For detailed instructions on how to run the install scripts, refer to the readme document in the dell-csi-helm-installer folder. - By default, the driver scans available SCSI adapters and tries to register them with the storage array under the SCSI hostname using `node.nodeNamePrefix` and the ID read from the file pointed to by `node.nodeIDPath`. If an adapter is already registered with the storage under a different hostname, the adapter is not used by the driver. - A hostname the driver uses for registration of adapters is in the form `--`. By default, these are csi-node and the machine ID read from the file `/etc/machine-id`. diff --git a/content/v1/csidriver/upgradation/drivers/powermax.md b/content/v1/csidriver/upgradation/drivers/powermax.md index e76bb61eb2..d38f7b6f73 100644 --- a/content/v1/csidriver/upgradation/drivers/powermax.md +++ b/content/v1/csidriver/upgradation/drivers/powermax.md @@ -24,10 +24,11 @@ You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSM Operator. 3. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash - cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --upgrade + cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --upgrade --helm-charts-version ``` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powermax/blob/main/dell-csi-helm-installer/csi-install.sh#L52) 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-powermax` 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 `my-powermax-settings.yaml` file and run the install script with the option _\-\-upgrade_, for example: ```bash diff --git a/content/v1/csidriver/upgradation/drivers/powerstore.md b/content/v1/csidriver/upgradation/drivers/powerstore.md index 28204eaa21..40021a0296 100644 --- a/content/v1/csidriver/upgradation/drivers/powerstore.md +++ b/content/v1/csidriver/upgradation/drivers/powerstore.md @@ -42,8 +42,10 @@ Note: While upgrading the driver via helm, controllerCount variable in myvalues. 6. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash - ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade + ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade --helm-charts-version ``` + *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerstore/blob/main/dell-csi-helm-installer/csi-install.sh#L13) 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-powerstore` directory if it was cloned before. ## Upgrade using Dell CSM Operator: diff --git a/content/v2/csidriver/installation/helm/powermax.md b/content/v2/csidriver/installation/helm/powermax.md index 26970fadee..ea9f93b173 100644 --- a/content/v2/csidriver/installation/helm/powermax.md +++ b/content/v2/csidriver/installation/helm/powermax.md @@ -321,7 +321,7 @@ CRDs should be configured during replication prepare stage with repctl as descri 8. Install the driver using `csi-install.sh` bash script by running ```bash - cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml + cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --helm-charts-version ``` 9. Or you can also install the driver using standalone helm chart using the command ```bash @@ -329,6 +329,7 @@ CRDs should be configured during replication prepare stage with repctl as descri ``` *Note:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powermax/blob/main/dell-csi-helm-installer/csi-install.sh#L52) 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-powermax` directory if it was cloned before. - For detailed instructions on how to run the install scripts, see the readme document in the dell-csi-helm-installer folder. - There are a set of samples provided [here](#sample-values-file) to help you configure the driver with reverse proxy - This script also runs the verify.sh script in the same directory. You will be prompted to enter the credentials for each of the Kubernetes nodes. The `verify.sh` script needs the credentials to check if the iSCSI initiators have been configured on all nodes. You can also skip the verification step by specifying the `--skip-verify-node` option diff --git a/content/v2/csidriver/installation/helm/powerstore.md b/content/v2/csidriver/installation/helm/powerstore.md index 4a77564107..f83a8b6cce 100644 --- a/content/v2/csidriver/installation/helm/powerstore.md +++ b/content/v2/csidriver/installation/helm/powerstore.md @@ -214,11 +214,12 @@ CRDs should be configured during replication prepare stage with repctl as descri 8. Install the driver using `csi-install.sh` bash script by running ```bash - ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml + ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --helm-charts-version ``` - After that the driver should be installed, you can check the condition of driver pods by running `kubectl get all -n csi-powerstore` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerstore/blob/main/dell-csi-helm-installer/csi-install.sh#L13) 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-powerstore` directory if it was cloned before. - For detailed instructions on how to run the install scripts, refer to the readme document in the dell-csi-helm-installer folder. - By default, the driver scans available SCSI adapters and tries to register them with the storage array under the SCSI hostname using `node.nodeNamePrefix` and the ID read from the file pointed to by `node.nodeIDPath`. If an adapter is already registered with the storage under a different hostname, the adapter is not used by the driver. - A hostname the driver uses for registration of adapters is in the form `--`. By default, these are csi-node and the machine ID read from the file `/etc/machine-id`. diff --git a/content/v2/csidriver/upgradation/drivers/powermax.md b/content/v2/csidriver/upgradation/drivers/powermax.md index 9672a34819..57e4a88929 100644 --- a/content/v2/csidriver/upgradation/drivers/powermax.md +++ b/content/v2/csidriver/upgradation/drivers/powermax.md @@ -24,10 +24,11 @@ You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSI Operator. 3. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash - cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --upgrade + cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --upgrade --upgrade --helm-charts-version ``` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powermax/blob/main/dell-csi-helm-installer/csi-install.sh#L52) 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-powermax` 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 `my-powermax-settings.yaml` file and run the install script with the option _\-\-upgrade_, for example: ```bash diff --git a/content/v2/csidriver/upgradation/drivers/powerstore.md b/content/v2/csidriver/upgradation/drivers/powerstore.md index fddeeefe09..19bd54cebe 100644 --- a/content/v2/csidriver/upgradation/drivers/powerstore.md +++ b/content/v2/csidriver/upgradation/drivers/powerstore.md @@ -42,9 +42,10 @@ Note: While upgrading the driver via helm, controllerCount variable in myvalues. 6. Run the `csi-install` script with the option _\-\-upgrade_ by running: ```bash - ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade + ./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade --helm-charts-version ``` - +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerstore/blob/main/dell-csi-helm-installer/csi-install.sh#L13) 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-powerstore` directory if it was cloned before. ## Upgrade using Dell CSM Operator: **Note:** Upgrading the Operator does not upgrade the CSI Driver. From 9f81d884d2758987c97f0595b9503f122b7eb95c Mon Sep 17 00:00:00 2001 From: Surya Gupta <109594002+suryagupta4@users.noreply.github.com> Date: Mon, 8 Apr 2024 12:14:43 +0530 Subject: [PATCH 04/49] Update helm-charts-version flag (#1061) --- content/docs/deployment/helm/drivers/installation/isilon.md | 5 ++++- .../docs/deployment/helm/drivers/installation/powerflex.md | 3 ++- content/docs/deployment/helm/drivers/installation/unity.md | 5 ++++- content/docs/deployment/helm/drivers/upgrade/isilon.md | 5 ++++- content/docs/deployment/helm/drivers/upgrade/powerflex.md | 5 +++-- content/docs/deployment/helm/drivers/upgrade/unity.md | 5 ++++- content/v1/csidriver/installation/helm/isilon.md | 5 ++++- content/v1/csidriver/installation/helm/powerflex.md | 3 ++- content/v1/csidriver/installation/helm/unity.md | 5 ++++- content/v1/csidriver/upgradation/drivers/isilon.md | 5 ++++- content/v1/csidriver/upgradation/drivers/powerflex.md | 5 +++-- content/v1/csidriver/upgradation/drivers/unity.md | 5 ++++- content/v2/csidriver/installation/helm/isilon.md | 5 ++++- content/v2/csidriver/installation/helm/powerflex.md | 3 ++- content/v2/csidriver/installation/helm/unity.md | 5 ++++- content/v2/csidriver/upgradation/drivers/isilon.md | 5 ++++- content/v2/csidriver/upgradation/drivers/powerflex.md | 5 +++-- content/v2/csidriver/upgradation/drivers/unity.md | 5 ++++- 18 files changed, 63 insertions(+), 21 deletions(-) diff --git a/content/docs/deployment/helm/drivers/installation/isilon.md b/content/docs/deployment/helm/drivers/installation/isilon.md index 81c865aec6..b7b2d24964 100644 --- a/content/docs/deployment/helm/drivers/installation/isilon.md +++ b/content/docs/deployment/helm/drivers/installation/isilon.md @@ -211,9 +211,12 @@ Create isilon-creds secret using the following command: 8. Install the driver using `csi-install.sh` bash script and default yaml by running ```bash cd dell-csi-helm-installer && wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.10.0/charts/csi-isilon/values.yaml && - ./csi-install.sh --namespace isilon --values my-isilon-settings.yaml + ./csi-install.sh --namespace isilon --values my-isilon-settings.yaml --helm-charts-version ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerscale/blob/main/dell-csi-helm-installer/csi-install.sh#L16) 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-powerscale` directory if it was cloned before. + ## Certificate validation for OneFS REST API calls The CSI driver exposes an install parameter 'skipCertificateValidation' which determines if the driver diff --git a/content/docs/deployment/helm/drivers/installation/powerflex.md b/content/docs/deployment/helm/drivers/installation/powerflex.md index b799930851..8780da0870 100644 --- a/content/docs/deployment/helm/drivers/installation/powerflex.md +++ b/content/docs/deployment/helm/drivers/installation/powerflex.md @@ -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 `. 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:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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. diff --git a/content/docs/deployment/helm/drivers/installation/unity.md b/content/docs/deployment/helm/drivers/installation/unity.md index 04ffbebc48..2cff89c648 100644 --- a/content/docs/deployment/helm/drivers/installation/unity.md +++ b/content/docs/deployment/helm/drivers/installation/unity.md @@ -245,8 +245,11 @@ cd dell-csi-helm-installer && wget -O my-unity-settings.yaml https://github.com/ 7. Run the command to proceed with the installation using bash script. ```bash - ./csi-install.sh --namespace unity --values ./myvalues.yaml + ./csi-install.sh --namespace unity --values ./myvalues.yaml --helm-charts-version ``` + *NOTE:* + - The parameter `--helm-charts-version` is optional and if you do not specify the 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-unity/blob/main/dell-csi-helm-installer/csi-install.sh#L22) 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-unity` directory if it was cloned before. + A successful installation must display messages that look similar to the following samples: ``` ------------------------------------------------------ diff --git a/content/docs/deployment/helm/drivers/upgrade/isilon.md b/content/docs/deployment/helm/drivers/upgrade/isilon.md index 8385f34c2d..229890953f 100644 --- a/content/docs/deployment/helm/drivers/upgrade/isilon.md +++ b/content/docs/deployment/helm/drivers/upgrade/isilon.md @@ -27,9 +27,12 @@ You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSM Operat 4. Upgrade the CSI Driver for Dell PowerScale using following command: ```bash - ./csi-install.sh --namespace isilon --values ./my-isilon-settings.yaml --upgrade + ./csi-install.sh --namespace isilon --values ./my-isilon-settings.yaml --helm-charts-version --upgrade ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerscale/blob/main/dell-csi-helm-installer/csi-install.sh#L16) 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-powerscale` directory if it was cloned before. + ## Upgrade using Dell CSM Operator **Note:** Upgrading the Operator does not upgrade the CSI Driver. diff --git a/content/docs/deployment/helm/drivers/upgrade/powerflex.md b/content/docs/deployment/helm/drivers/upgrade/powerflex.md index 467f230b16..68fca334b8 100644 --- a/content/docs/deployment/helm/drivers/upgrade/powerflex.md +++ b/content/docs/deployment/helm/drivers/upgrade/powerflex.md @@ -18,15 +18,16 @@ You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSM Operato 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 --upgrade ``` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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. - 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 --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. diff --git a/content/docs/deployment/helm/drivers/upgrade/unity.md b/content/docs/deployment/helm/drivers/upgrade/unity.md index 77213b0e1c..2b0615c9ee 100644 --- a/content/docs/deployment/helm/drivers/upgrade/unity.md +++ b/content/docs/deployment/helm/drivers/upgrade/unity.md @@ -27,9 +27,12 @@ To upgrade the driver from csi-unity v2.9.0 to csi-unity v2.10.0 3. Navigate to csi-unity/dell-csi-hem-installer folder and execute this command: ```bash - ./csi-install.sh --namespace unity --values ./myvalues.yaml --upgrade + ./csi-install.sh --namespace unity --values ./myvalues.yaml --helm-charts-version --upgrade ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-unity/blob/main/dell-csi-helm-installer/csi-install.sh#L22) 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-unity` directory if it was cloned before. + ### Upgrade using Dell CSM Operator: **Note:** Upgrading the Operator does not upgrade the CSI Driver. diff --git a/content/v1/csidriver/installation/helm/isilon.md b/content/v1/csidriver/installation/helm/isilon.md index 31f3a4c38b..0c769c92c8 100644 --- a/content/v1/csidriver/installation/helm/isilon.md +++ b/content/v1/csidriver/installation/helm/isilon.md @@ -211,9 +211,12 @@ Create isilon-creds secret using the following command: 8. Install the driver using `csi-install.sh` bash script and default yaml by running ```bash cd dell-csi-helm-installer && wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.1/charts/csi-isilon/values.yaml && - ./csi-install.sh --namespace isilon --values my-isilon-settings.yaml + ./csi-install.sh --namespace isilon --values my-isilon-settings.yaml --helm-charts-version ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerscale/blob/main/dell-csi-helm-installer/csi-install.sh#L16) 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-powerscale` directory if it was cloned before. + ## Certificate validation for OneFS REST API calls The CSI driver exposes an install parameter 'skipCertificateValidation' which determines if the driver diff --git a/content/v1/csidriver/installation/helm/powerflex.md b/content/v1/csidriver/installation/helm/powerflex.md index 8a87470549..9c1b6a1152 100644 --- a/content/v1/csidriver/installation/helm/powerflex.md +++ b/content/v1/csidriver/installation/helm/powerflex.md @@ -211,10 +211,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 `. 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:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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. diff --git a/content/v1/csidriver/installation/helm/unity.md b/content/v1/csidriver/installation/helm/unity.md index 6b9cefabdf..a13e38c3d8 100644 --- a/content/v1/csidriver/installation/helm/unity.md +++ b/content/v1/csidriver/installation/helm/unity.md @@ -245,8 +245,11 @@ cd dell-csi-helm-installer && wget -O my-unity-settings.yaml https://github.com/ 7. Run the command to proceed with the installation using bash script. ```bash - ./csi-install.sh --namespace unity --values ./myvalues.yaml + ./csi-install.sh --namespace unity --values ./myvalues.yaml --helm-charts-version ``` + *NOTE:* + - The parameter `--helm-charts-version` is optional and if you do not specify the 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-unity/blob/main/dell-csi-helm-installer/csi-install.sh#L22) 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-unity` directory if it was cloned before. + A successful installation must display messages that look similar to the following samples: ``` ------------------------------------------------------ diff --git a/content/v1/csidriver/upgradation/drivers/isilon.md b/content/v1/csidriver/upgradation/drivers/isilon.md index b278408360..c57bfa7427 100644 --- a/content/v1/csidriver/upgradation/drivers/isilon.md +++ b/content/v1/csidriver/upgradation/drivers/isilon.md @@ -27,9 +27,12 @@ You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSM Operat 4. Upgrade the CSI Driver for Dell PowerScale using following command: ```bash - ./csi-install.sh --namespace isilon --values ./my-isilon-settings.yaml --upgrade + ./csi-install.sh --namespace isilon --values ./my-isilon-settings.yaml --helm-charts-version --upgrade ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerscale/blob/main/dell-csi-helm-installer/csi-install.sh#L16) 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-powerscale` directory if it was cloned before. + ## Upgrade using Dell CSM Operator **Note:** Upgrading the Operator does not upgrade the CSI Driver. diff --git a/content/v1/csidriver/upgradation/drivers/powerflex.md b/content/v1/csidriver/upgradation/drivers/powerflex.md index 4e51d479ba..7708c6582e 100644 --- a/content/v1/csidriver/upgradation/drivers/powerflex.md +++ b/content/v1/csidriver/upgradation/drivers/powerflex.md @@ -19,15 +19,16 @@ You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSM Operato 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 --upgrade ``` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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. - 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 --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. diff --git a/content/v1/csidriver/upgradation/drivers/unity.md b/content/v1/csidriver/upgradation/drivers/unity.md index 3b8c0108d9..57c742b6a2 100644 --- a/content/v1/csidriver/upgradation/drivers/unity.md +++ b/content/v1/csidriver/upgradation/drivers/unity.md @@ -27,9 +27,12 @@ To upgrade the driver from csi-unity v2.8.0 to csi-unity v2.9.1 3. Navigate to csi-unity/dell-csi-hem-installer folder and execute this command: ```bash - ./csi-install.sh --namespace unity --values ./myvalues.yaml --upgrade + ./csi-install.sh --namespace unity --values ./myvalues.yaml --helm-charts-version --upgrade ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-unity/blob/main/dell-csi-helm-installer/csi-install.sh#L22) 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-unity` directory if it was cloned before. + ### Upgrade using Dell CSM Operator: **Note:** Upgrading the Operator does not upgrade the CSI Driver. diff --git a/content/v2/csidriver/installation/helm/isilon.md b/content/v2/csidriver/installation/helm/isilon.md index db951501f2..31b820dad3 100644 --- a/content/v2/csidriver/installation/helm/isilon.md +++ b/content/v2/csidriver/installation/helm/isilon.md @@ -227,9 +227,12 @@ Create isilon-creds secret using the following command: 8. Install the driver using `csi-install.sh` bash script and default yaml by running ```bash cd dell-csi-helm-installer && wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.8.0/charts/csi-isilon/values.yaml && - ./csi-install.sh --namespace isilon --values my-isilon-settings.yaml + ./csi-install.sh --namespace isilon --values my-isilon-settings.yaml --helm-charts-version ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerscale/blob/main/dell-csi-helm-installer/csi-install.sh#L16) 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-powerscale` directory if it was cloned before. + ## Certificate validation for OneFS REST API calls The CSI driver exposes an install parameter 'skipCertificateValidation' which determines if the driver diff --git a/content/v2/csidriver/installation/helm/powerflex.md b/content/v2/csidriver/installation/helm/powerflex.md index cd57eb886a..50343275c4 100644 --- a/content/v2/csidriver/installation/helm/powerflex.md +++ b/content/v2/csidriver/installation/helm/powerflex.md @@ -223,10 +223,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 `. 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:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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. diff --git a/content/v2/csidriver/installation/helm/unity.md b/content/v2/csidriver/installation/helm/unity.md index e7e0f12538..dabc542cb2 100644 --- a/content/v2/csidriver/installation/helm/unity.md +++ b/content/v2/csidriver/installation/helm/unity.md @@ -259,8 +259,11 @@ cd dell-csi-helm-installer && wget -O my-unity-settings.yaml https://github.com/ 7. Run the command to proceed with the installation using bash script. ```bash - ./csi-install.sh --namespace unity --values ./myvalues.yaml + ./csi-install.sh --namespace unity --values ./myvalues.yaml --helm-charts-version ``` + *NOTE:* + - The parameter `--helm-charts-version` is optional and if you do not specify the 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-unity/blob/main/dell-csi-helm-installer/csi-install.sh#L22) 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-unity` directory if it was cloned before. + A successful installation must display messages that look similar to the following samples: ``` ------------------------------------------------------ diff --git a/content/v2/csidriver/upgradation/drivers/isilon.md b/content/v2/csidriver/upgradation/drivers/isilon.md index c0b37f9221..805e212950 100644 --- a/content/v2/csidriver/upgradation/drivers/isilon.md +++ b/content/v2/csidriver/upgradation/drivers/isilon.md @@ -27,9 +27,12 @@ You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSI Operat 4. Upgrade the CSI Driver for Dell PowerScale using following command: ```bash - ./csi-install.sh --namespace isilon --values ./my-isilon-settings.yaml --upgrade + ./csi-install.sh --namespace isilon --values ./my-isilon-settings.yaml --helm-charts-version --upgrade ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-powerscale/blob/main/dell-csi-helm-installer/csi-install.sh#L16) 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-powerscale` directory if it was cloned before. + ## Upgrade using Dell CSM Operator **Note:** Upgrading the Operator does not upgrade the CSI Driver. diff --git a/content/v2/csidriver/upgradation/drivers/powerflex.md b/content/v2/csidriver/upgradation/drivers/powerflex.md index 4890384a19..b8c62a749c 100644 --- a/content/v2/csidriver/upgradation/drivers/powerflex.md +++ b/content/v2/csidriver/upgradation/drivers/powerflex.md @@ -19,15 +19,16 @@ You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSI Operato 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 --upgrade ``` *NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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. - 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 --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. diff --git a/content/v2/csidriver/upgradation/drivers/unity.md b/content/v2/csidriver/upgradation/drivers/unity.md index efab1b693f..25a5fd17e0 100644 --- a/content/v2/csidriver/upgradation/drivers/unity.md +++ b/content/v2/csidriver/upgradation/drivers/unity.md @@ -27,9 +27,12 @@ To upgrade the driver from csi-unity v2.7.0 to csi-unity v2.8.0 3. Navigate to csi-unity/dell-csi-hem-installer folder and execute this command: ```bash - ./csi-install.sh --namespace unity --values ./myvalues.yaml --upgrade + ./csi-install.sh --namespace unity --values ./myvalues.yaml --helm-charts-version --upgrade ``` +*NOTE:* +- The parameter `--helm-charts-version` is optional and if you do not specify the 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-unity/blob/main/dell-csi-helm-installer/csi-install.sh#L22) 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-unity` directory if it was cloned before. + ### Upgrade using Dell CSM Operator: **Note:** Upgrading the Operator does not upgrade the CSI Driver. From 4b16fc2cb929f8c5f2857daa56cfcc2e2d779eeb Mon Sep 17 00:00:00 2001 From: KshitijaKakde <111420075+KshitijaKakde@users.noreply.github.com> Date: Wed, 10 Apr 2024 18:38:43 +0530 Subject: [PATCH 05/49] Adding a note for 'clusterName' for CSI-PowerScale (#1062) --- content/docs/csidriver/features/powerscale.md | 2 +- content/docs/deployment/helm/drivers/installation/isilon.md | 3 +++ content/v1/csidriver/features/powerscale.md | 2 +- content/v1/csidriver/installation/helm/isilon.md | 3 +++ content/v2/csidriver/features/powerscale.md | 2 +- content/v2/csidriver/installation/helm/isilon.md | 3 +++ content/v3/csidriver/features/powerscale.md | 2 +- content/v3/csidriver/installation/helm/isilon.md | 3 +++ 8 files changed, 16 insertions(+), 4 deletions(-) diff --git a/content/docs/csidriver/features/powerscale.md b/content/docs/csidriver/features/powerscale.md index 23b02971a8..f66cb4740d 100644 --- a/content/docs/csidriver/features/powerscale.md +++ b/content/docs/csidriver/features/powerscale.md @@ -21,7 +21,7 @@ You can use existing volumes from the PowerScale array as Persistent Volumes in 1. Open your volume in One FS, and take a note of volume-id. 2. Create PersistentVolume and use this volume-id as a volumeHandle in the manifest. Modify other parameters according to your needs. -3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of `=_=_==_=_==_=_=` +3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of `=_=_==_=_==_=_=` 4. If Quotas are enabled in the driver, it is required to add the Quota ID to the description of the NFS export in this format: `CSI_QUOTA_ID:sC-kAAEAAAAAAAAAAAAAQEpVAAAAAAAA` 5. Quota ID can be identified by querying the PowerScale system. diff --git a/content/docs/deployment/helm/drivers/installation/isilon.md b/content/docs/deployment/helm/drivers/installation/isilon.md index b7b2d24964..5698734b49 100644 --- a/content/docs/deployment/helm/drivers/installation/isilon.md +++ b/content/docs/deployment/helm/drivers/installation/isilon.md @@ -97,6 +97,9 @@ CRDs should be configured during replication prepare stage with repctl as descri 1. Run `git clone -b v2.10.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*. + + **Note**: The 'clusterName' serves as a logical, unique identifier for the array that should remain unchanged once it is included in the volume handle. Altering this identifier is not advisable, as it would result in the failure of all operations associated with the volume that was created earlier. + 4. Download `wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.10.0/charts/csi-isilon/values.yaml` into `cd ../dell-csi-helm-installer` to customize settings for installation. 5. Edit *my-isilon-settings.yaml* to set the following parameters for your installation: The following table lists the primary configurable parameters of the PowerScale driver Helm chart and their default values. More detailed information can be diff --git a/content/v1/csidriver/features/powerscale.md b/content/v1/csidriver/features/powerscale.md index 0024fc9b52..0303d2127f 100644 --- a/content/v1/csidriver/features/powerscale.md +++ b/content/v1/csidriver/features/powerscale.md @@ -21,7 +21,7 @@ You can use existing volumes from the PowerScale array as Persistent Volumes in 1. Open your volume in One FS, and take a note of volume-id. 2. Create PersistentVolume and use this volume-id as a volumeHandle in the manifest. Modify other parameters according to your needs. -3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of `=_=_==_=_==_=_=` +3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of `=_=_==_=_==_=_=` 4. If Quotas are enabled in the driver, it is required to add the Quota ID to the description of the NFS export in this format: `CSI_QUOTA_ID:sC-kAAEAAAAAAAAAAAAAQEpVAAAAAAAA` 5. Quota ID can be identified by querying the PowerScale system. diff --git a/content/v1/csidriver/installation/helm/isilon.md b/content/v1/csidriver/installation/helm/isilon.md index 0c769c92c8..cd95c645c5 100644 --- a/content/v1/csidriver/installation/helm/isilon.md +++ b/content/v1/csidriver/installation/helm/isilon.md @@ -97,6 +97,9 @@ CRDs should be configured during replication prepare stage with repctl as descri 1. Run `git clone -b v2.9.1 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*. + + **Note**: The 'clusterName' serves as a logical, unique identifier for the array that should remain unchanged once it is included in the volume handle. Altering this identifier is not advisable, as it would result in the failure of all operations associated with the volume that was created earlier. + 4. Download `wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.9.1/charts/csi-isilon/values.yaml` into `cd ../dell-csi-helm-installer` to customize settings for installation. 5. Edit *my-isilon-settings.yaml* to set the following parameters for your installation: The following table lists the primary configurable parameters of the PowerScale driver Helm chart and their default values. More detailed information can be diff --git a/content/v2/csidriver/features/powerscale.md b/content/v2/csidriver/features/powerscale.md index 31b6198e81..ae3455753f 100644 --- a/content/v2/csidriver/features/powerscale.md +++ b/content/v2/csidriver/features/powerscale.md @@ -21,7 +21,7 @@ You can use existing volumes from the PowerScale array as Persistent Volumes in 1. Open your volume in One FS, and take a note of volume-id. 2. Create PersistentVolume and use this volume-id as a volumeHandle in the manifest. Modify other parameters according to your needs. -3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of `=_=_==_=_==_=_=` +3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of `=_=_==_=_==_=_=` 4. If Quotas are enabled in the driver, it is required to add the Quota ID to the description of the NFS export in this format: `CSI_QUOTA_ID:sC-kAAEAAAAAAAAAAAAAQEpVAAAAAAAA` 5. Quota ID can be identified by querying the PowerScale system. diff --git a/content/v2/csidriver/installation/helm/isilon.md b/content/v2/csidriver/installation/helm/isilon.md index 31b820dad3..216b21a91b 100644 --- a/content/v2/csidriver/installation/helm/isilon.md +++ b/content/v2/csidriver/installation/helm/isilon.md @@ -110,6 +110,9 @@ CRDs should be configured during replication prepare stage with repctl as descri 1. Run `git clone -b v2.8.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*. + + **Note**: The 'clusterName' serves as a logical, unique identifier for the array that should remain unchanged once it is included in the volume handle. Altering this identifier is not advisable, as it would result in the failure of all operations associated with the volume that was created earlier. + 4. Download `wget -O my-isilon-settings.yaml https://raw.githubusercontent.com/dell/helm-charts/csi-isilon-2.8.0/charts/csi-isilon/values.yaml` into `cd ../dell-csi-helm-installer` to customize settings for installation. 5. Edit *my-isilon-settings.yaml* to set the following parameters for your installation: The following table lists the primary configurable parameters of the PowerScale driver Helm chart and their default values. More detailed information can be diff --git a/content/v3/csidriver/features/powerscale.md b/content/v3/csidriver/features/powerscale.md index 70d581efed..0cc19f8209 100644 --- a/content/v3/csidriver/features/powerscale.md +++ b/content/v3/csidriver/features/powerscale.md @@ -21,7 +21,7 @@ You can use existing volumes from the PowerScale array as Persistent Volumes in 1. Open your volume in One FS, and take a note of volume-id. 2. Create PersistentVolume and use this volume-id as a volumeHandle in the manifest. Modify other parameters according to your needs. -3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of =_=_==_=_==_=_= +3. In the following example, the PowerScale cluster accessZone is assumed as 'System', storage class as 'isilon', cluster name as 'pscale-cluster' and volume's internal name as 'isilonvol'. The volume-handle should be in the format of =_=_==_=_==_=_= 4. If Quotas are enabled in the driver, it is required to add the Quota ID to the description of the NFS export in this format: `CSI_QUOTA_ID:sC-kAAEAAAAAAAAAAAAAQEpVAAAAAAAA` 5. Quota ID can be identified by querying the PowerScale system. diff --git a/content/v3/csidriver/installation/helm/isilon.md b/content/v3/csidriver/installation/helm/isilon.md index 24cf090b4a..ce822c4f5f 100644 --- a/content/v3/csidriver/installation/helm/isilon.md +++ b/content/v3/csidriver/installation/helm/isilon.md @@ -104,6 +104,9 @@ CRDs should be configured during replication prepare stage with repctl as descri 1. Run `git clone -b v2.7.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*. + + **Note**: The 'clusterName' serves as a logical, unique identifier for the array that should remain unchanged once it is included in the volume handle. Altering this identifier is not advisable, as it would result in the failure of all operations associated with the volume that was created earlier. + 4. Copy *the helm/csi-isilon/values.yaml* into a new location with name say *my-isilon-settings.yaml*, to customize settings for installation. 5. Edit *my-isilon-settings.yaml* to set the following parameters for your installation: The following table lists the primary configurable parameters of the PowerScale driver Helm chart and their default values. More detailed information can be From fa9ac597aaba4ee895033785c1bd04548f9cbf5e Mon Sep 17 00:00:00 2001 From: mdutka-dell <115641913+mdutka-dell@users.noreply.github.com> Date: Thu, 18 Apr 2024 11:41:54 +0200 Subject: [PATCH 06/49] docs: add configurable export IP in csi-unity (#1054) * docs: add configurable export IP in csi-unity * docs: change release version in template * fix docs folder * add parameter to csm operator installation page --------- Co-authored-by: Bartosz Ciesielczyk --- content/docs/csidriver/features/unity.md | 13 + .../templates/helm/csm-1.11.0-values.template | 426 ++++++++++++++++++ .../deployment/csmoperator/drivers/unity.md | 1 + .../helm/drivers/installation/unity.md | 1 + 4 files changed, 441 insertions(+) create mode 100644 content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template diff --git a/content/docs/csidriver/features/unity.md b/content/docs/csidriver/features/unity.md index 087544f5eb..8205ebf1ce 100644 --- a/content/docs/csidriver/features/unity.md +++ b/content/docs/csidriver/features/unity.md @@ -711,3 +711,16 @@ data: TENANT_NAME: "" ``` >Note: csi-unity supports Tenancy in multi-array setup, provided the TenantName is the same across Unity XT instances. + +## Support custom networks for NFS I/O traffic + +When `allowedNetworks` is specified for using custom networks to handle NFS traffic, and a user already +has workloads scheduled, there is a possibility that it might lead to backward compatibility issues. For example, ControllerUnPublish might not be able to completely remove clients from the NFS exports of previously created pods. + +Also, the previous workload will still be using the default network and not custom networks. For previous workloads to use custom networks, the recreation of pods is required. + +When csi-unity driver creates an NFS export, the traffic flows through the client specified in the export. By default, the client is the network interface for Kubernetes +communication (same IP/fqdn as k8s node) by default. + +For a cluster with multiple network interfaces and if a user wants to segregate k8s traffic from NFS traffic; you can use the `allowedNetworks` option. +`allowedNetworks` takes CIDR addresses as a parameter to match the IPs to be picked up by the driver to allow and route NFS traffic. diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template new file mode 100644 index 0000000000..bc9d4a123b --- /dev/null +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template @@ -0,0 +1,426 @@ +## K8S/DRIVER ATTRIBUTES +########################################## +## K8S/CSI-PowerStore ATTRIBUTES +########################################## +csi-powerstore: + enabled: $POWERSTORE_ENABLED + version: v2.10.0 + images: + # "driver" defines the container image, used for the driver container. + driver: dellemc/csi-powerstore:v2.10.0 + # CSI sidecars + attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 + provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0 + snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1 + resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0 + registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 + healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 + + # CSM sidecars + replication: dellemc/dell-csi-replicator:v1.8.0 + vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0 + podmon: dellemc/podmon:v1.9.0 + metadataretriever: dellemc/csi-metadata-retriever:v1.6.0 + ## Controller ATTRIBUTES + controller: + controllerCount: $CONTROLLER_COUNT + volumeNamePrefix: $VOLUME_NAME_PREFIX + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + nodeSelector: $CONTROLLER_POD_NODE_SELECTOR + tolerations: $CONTROLLER_TOLERATIONS + replication: + enabled: $REPLICATION_ENABLED + vgsnapshot: + enabled: $VG_SNAPSHOT_ENABLED + snapshot: + enabled: $SNAPSHOT_ENABLED + snapNamePrefix: $SNAP_NAME_PREFIX + resizer: + enabled: $RESIZER_ENABLED + ## Node ATTRIBUTES + node: + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + nodeSelector: $NODE_POD_NODE_SELECTOR + tolerations: $NODE_TOLERATIONS + # Uncomment if CSM for Resiliency and CSI Driver pods monitor are enabled + # - key: "offline.vxflexos.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "vxflexos.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.unity.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "unity.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.isilon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "isilon.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.powerstore.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "powerstore.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + storageCapacity: + enabled: $STORAGE_CAPACITY_ENABLED + podmon: + enabled: $RESILIENCY_ENABLED + + maxPowerstoreVolumesPerNode: $MAX_VOLUMES_PER_NODE + +## K8S/CSI-PowerMax ATTRIBUTES +########################################## +csi-powermax: + enabled: $POWERMAX_ENABLED + global: + storageArrays: + - storageArrayId: "$POWERMAX_STORAGE_ARRAY_ID" + endpoint: $POWERMAX_STORAGE_ARRAY_ENDPOINT_URL + backupEndpoint: $POWERMAX_STORAGE_ARRAY_BACKUP_ENDPOINT_URL + - storageArrayId: "$TARGET_ARRAY_ID" + endpoint: $TARGET_UNISPHERE + managementServers: + - endpoint: $POWERMAX_MANAGEMENT_SERVERS_ENDPOINT_URL + - endpoint: $TARGET_UNISPHERE + version: v2.10.0 + images: + # "driver" defines the container image, used for the driver container. + driver: dellemc/csi-powermax:v2.10.0 + csireverseproxy: dellemc/csipowermax-reverseproxy:v2.9.0 + # CSI sidecars + attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 + provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0 + snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1 + resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0 + registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 + healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 + # CSM sidecars + replication: dellemc/dell-csi-replicator:v1.8.0 + authorization: dellemc/csm-authorization-sidecar:v1.10.0 + migration: dellemc/dell-csi-migrator:v1.3.0 + noderescan: dellemc/dell-csi-node-rescanner:v1.2.0 + clusterPrefix: $POWERMAX_CLUSTER_PREFIX + portGroups: "$POWERMAX_PORT_GROUPS" + fsGroupPolicy: "$FSGROUP_POLICY" + maxPowerMaxVolumesPerNode: $MAX_VOLUMES_PER_NODE + enableCHAP: $ISCSI_CHAP_ENABLED + transportProtocol: "$NODE_TRANSPORT_PROTOCOL" + storageCapacity: + enabled: $STORAGE_CAPACITY_ENABLED + controller: + controllerCount: $CONTROLLER_COUNT + volumeNamePrefix: $VOLUME_NAME_PREFIX + snapshot: + enabled: $SNAPSHOT_ENABLED + snapNamePrefix: $SNAP_NAME_PREFIX + resizer: + enabled: $RESIZER_ENABLED + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + nodeSelector: $CONTROLLER_POD_NODE_SELECTOR + tolerations: $CONTROLLER_TOLERATIONS + node: + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + topologyControl: + enabled: $TOPOLOGY_ENABLED + nodeSelector: $NODE_POD_NODE_SELECTOR + tolerations: $NODE_TOLERATIONS + - key: "node.kubernetes.io/memory-pressure" + operator: "Exists" + effect: "NoExecute" + - key: "node.kubernetes.io/disk-pressure" + operator: "Exists" + effect: "NoExecute" + - key: "node.kubernetes.io/network-unavailable" + operator: "Exists" + effect: "NoExecute" + csireverseproxy: + deployAsSidecar: true + replication: + enabled: $REPLICATION_ENABLED + migration: + enabled: $MIGRATION_ENABLED + authorization: + enabled: $AUTHORIZATION_ENABLED + proxyHost: $AUTHORIZATION_PROXY_HOST + skipCertificateValidation: $AUTHORIZATION_SKIP_CERTIFICATE_VALIDATION + storageCapacity: + enabled: $STORAGE_CAPACITY_ENABLED + vSphere: + enabled: $VSPHERE_ENABLED + fcPortGroup: "$VSPHERE_FC_PORT_GROUP" + fcHostName: "$VSPHERE_FC_HOST_NAME" + vCenterHost: "$VSPHERE_VCENTER_HOST" + vCenterCredSecret: $VSPHERE_VCENTER_CRED_SECRET + +## K8S/CSI-PowerFlex ATTRIBUTES +########################################## +csi-vxflexos: + enabled: $POWERFLEX_ENABLED + version: v2.10.0 + images: + # "driver" defines the container image, used for the driver container. + driver: dellemc/csi-vxflexos:v2.10.0 + # "powerflexSdc" defines the SDC image for init container. + powerflexSdc: dellemc/sdc:4.5 + # CSI sidecars + attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 + provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0 + snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1 + resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0 + registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 + healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 + # CSM sidecars + replication: dellemc/dell-csi-replicator:v1.8.0 + vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0 + podmon: dellemc/podmon:v1.9.0 + authorization: dellemc/csm-authorization-sidecar:v1.10.0 + certSecretCount: $CERT_SECRET_COUNT + controller: + replication: + enabled: $REPLICATION_ENABLED + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + controllerCount: $CONTROLLER_COUNT + volumeNamePrefix: $VOLUME_NAME_PREFIX + snapshot: + enabled: $SNAPSHOT_ENABLED + resizer: + enabled: $RESIZER_ENABLED + nodeSelector: $CONTROLLER_POD_NODE_SELECTOR + tolerations: $CONTROLLER_TOLERATIONS + node: + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + nodeSelector: $NODE_POD_NODE_SELECTOR + renameSDC: + enabled: $RENAME_SDC_ENABLED + sdcPrefix: $SDC_PREFIX + approveSDC: + enabled: $APPROVE_SDC_ENABLED + tolerations: $NODE_TOLERATIONS + # Uncomment if CSM for Resiliency and CSI Driver pods monitor is enabled + # - key: "offline.vxflexos.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "vxflexos.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.unity.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "unity.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.isilon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "isilon.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + storageCapacity: + enabled: $STORAGE_CAPACITY_ENABLED + enableQuota: $QUOTA_ENABLED + externalAccess: + monitor: + enabled: $MONITOR_ENABLED + vgsnapshotter: + enabled: $VG_SNAPSHOT_ENABLED + podmon: + enabled: $RESILIENCY_ENABLED + authorization: + enabled: $AUTHORIZATION_ENABLED + proxyHost: $AUTHORIZATION_PROXY_HOST + skipCertificateValidation: $AUTHORIZATION_SKIP_CERTIFICATE_VALIDATION + maxPowerflexVolumesPerNode: $MAX_VOLUMES_PER_NODE + +## K8S/CSI-PowerScale ATTRIBUTES +########################################## +csi-isilon: + enabled: $POWERSCALE_ENABLED + version: "v2.10.0" + images: + # "driver" defines the container image, used for the driver container. + driver: dellemc/csi-isilon:v2.10.0 + # CSI sidecars + attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 + provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0 + snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1 + resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0 + registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 + healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 + # CSM sidecars + replication: dellemc/dell-csi-replicator:v1.8.0 + podmon: dellemc/podmon:v1.9.0 + authorization: dellemc/csm-authorization-sidecar:v1.10.0 + metadataretriever: dellemc/csi-metadata-retriever:v1.4.0 + encryption: dellemc/csm-encryption:v0.3.0 + + certSecretCount: $CERT_SECRET_COUNT + allowedNetworks: [] + verbose: 1 + enableCustomTopology: false + fsGroupPolicy: $FSGROUP_POLICY + storageCapacity: + enabled: $STORAGE_CAPACITY_ENABLED + maxIsilonVolumesPerNode: $MAX_VOLUMES_PER_NODE + controller: + controllerCount: $CONTROLLER_COUNT + volumeNamePrefix: $VOLUME_NAME_PREFIX + replication: + enabled: $REPLICATION_ENABLED + snapshot: + enabled: $SNAPSHOT_ENABLED + snapNamePrefix: $SNAP_NAME_PREFIX + resizer: + enabled: $RESIZER_ENABLED + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + nodeSelector: $CONTROLLER_POD_NODE_SELECTOR + tolerations: $CONTROLLER_TOLERATIONS + node: + nodeSelector: $NODE_POD_NODE_SELECTOR + tolerations: $NODE_TOLERATIONS + # - key: "node.kubernetes.io/memory-pressure" + # operator: "Exists" + # effect: "NoExecute" + # - key: "node.kubernetes.io/disk-pressure" + # operator: "Exists" + # effect: "NoExecute" + # - key: "node.kubernetes.io/network-unavailable" + # operator: "Exists" + # effect: "NoExecute" + # Uncomment if CSM for Resiliency and CSI Driver pods monitor are enabled + # - key: "offline.vxflexos.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "vxflexos.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.unity.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "unity.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.isilon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "isilon.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + authorization: + enabled: $AUTHORIZATION_ENABLED + proxyHost: $AUTHORIZATION_PROXY_HOST + skipCertificateValidation: $AUTHORIZATION_SKIP_CERTIFICATE_VALIDATION + # Enable this feature only after contact support for additional information + podmon: + enabled: $RESILIENCY_ENABLED + +## K8S/CSI-Unity ATTRIBUTES +########################################## +csi-unity: + enabled: $UNITY_ENABLED + version: v2.11.0 + images: + # "driver" defines the container image, used for the driver container. + driver: dellemc/csi-unity:v2.11.0 + # CSI sidecars + attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 + provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0 + snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1 + resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0 + registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 + healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 + # CSM sidecars + podmon: dellemc/podmon:v1.9.0 + certSecretCount: $CERT_SECRET_COUNT + allowedNetworks: [] + fsGroupPolicy: $FSGROUP_POLICY + controller: + controllerCount: $CONTROLLER_COUNT + volumeNamePrefix: $VOLUME_NAME_PREFIX + snapshot: + enabled: $SNAPSHOT_ENABLED + snapNamePrefix: $SNAP_NAME_PREFIX + resizer: + enabled: $RESIZER_ENABLED + nodeSelector: $CONTROLLER_POD_NODE_SELECTOR + tolerations: $CONTROLLER_TOLERATIONS + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + node: + healthMonitor: + enabled: $HEALTH_MONITOR_ENABLED + nodeSelector: $NODE_POD_NODE_SELECTOR + tolerations: $NODE_TOLERATIONS + # - key: "node.kubernetes.io/memory-pressure" + # operator: "Exists" + # effect: "NoExecute" + # - key: "node.kubernetes.io/disk-pressure" + # operator: "Exists" + # effect: "NoExecute" + # - key: "node.kubernetes.io/network-unavailable" + # operator: "Exists" + # effect: "NoExecute" + # Uncomment if CSM for Resiliency and CSI Driver pods monitor are enabled + # - key: "offline.vxflexos.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "vxflexos.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.unity.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "unity.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "offline.isilon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + # - key: "isilon.podmon.storage.dell.com" + # operator: "Exists" + # effect: "NoSchedule" + storageCapacity: + enabled: $STORAGE_CAPACITY_ENABLED + maxUnityVolumesPerNode: $MAX_VOLUMES_PER_NODE + podmon: + enabled: $RESILIENCY_ENABLED + +## K8S/Replication Module ATTRIBUTES +########################################## +csm-replication: + enabled: $REPLICATION_ENABLED + +## K8S/Observability Module ATTRIBUTES +########################################## +karavi-observability: + enabled: $OBSERVABILITY_ENABLED + karaviMetricsPowerstore: + enabled: $POWERSTORE_OBSERVABILITY_METRICS_ENABLED + karaviMetricsPowermax: + enabled: $POWERMAX_OBSERVABILITY_METRICS_ENABLED + karaviMetricsPowerflex: + enabled: $POWERFLEX_OBSERVABILITY_METRICS_ENABLED + karaviMetricsPowerscale: + enabled: $POWERSCALE_OBSERVABILITY_METRICS_ENABLED + cert-manager: + enabled: $OBSERVABILITY_CERT_MANAGER_ENABLED + +## K8S/Cert-manager ATTRIBUTES +########################################## +cert-manager: + enabled: $CERT_MANAGER_ENABLED diff --git a/content/docs/deployment/csmoperator/drivers/unity.md b/content/docs/deployment/csmoperator/drivers/unity.md index 3c936941fd..7d57c5907f 100644 --- a/content/docs/deployment/csmoperator/drivers/unity.md +++ b/content/docs/deployment/csmoperator/drivers/unity.md @@ -72,6 +72,7 @@ kubectl get csm --all-namespaces | X_CSI_HEALTH_MONITOR_ENABLED | Enable/Disable health monitor of CSI volumes from Controller plugin - volume condition | No | false | | ***Node parameters*** | | X_CSI_HEALTH_MONITOR_ENABLED | Enable/Disable health monitor of CSI volumes from Controller plugin - volume condition | No | false | +| X_CSI_ALLOWED_NETWORKS | Custom networks for Unity export. List of networks that can be used for NFS I/O traffic, CIDR format should be used "ip/prefix ip/prefix" | No | empty | 4. Execute the following command to create Unity XT custom resource: ```bash diff --git a/content/docs/deployment/helm/drivers/installation/unity.md b/content/docs/deployment/helm/drivers/installation/unity.md index 2cff89c648..02192f9ee3 100644 --- a/content/docs/deployment/helm/drivers/installation/unity.md +++ b/content/docs/deployment/helm/drivers/installation/unity.md @@ -114,6 +114,7 @@ cd dell-csi-helm-installer && wget -O my-unity-settings.yaml https://github.com/ | syncNodeInfoInterval | Time interval to add node info to the array. Default 15 minutes. The minimum value should be 1 minute. | No | 15 | | maxUnityVolumesPerNode | Maximum number of volumes that controller can publish to the node. | No | 0 | | certSecretCount | Represents the number of certificate secrets, which the user is going to create for SSL authentication. (unity-cert-0..unity-cert-n). The minimum value should be 1. | No | 1 | + | [allowedNetworks](../../../../../csidriver/features/unity/#support-custom-networks-for-nfs-io-traffic) | Defines the list of networks that can be used for NFS I/O traffic, CIDR format must be used. | No | [ ] | | imagePullPolicy | The default pull policy is IfNotPresent which causes the Kubelet to skip pulling an image if it already exists. | Yes | IfNotPresent | | podmon.enabled | service to monitor failing jobs and notify | No | false | | tenantName | Tenant name added while adding host entry to the array | No | | From 787f1e0bebe69f31ba704fcc0c0c18263308be20 Mon Sep 17 00:00:00 2001 From: boyamurthy <92081029+boyamurthy@users.noreply.github.com> Date: Wed, 24 Apr 2024 11:10:31 +0530 Subject: [PATCH 07/49] Adding resiliency support for PowerMax in installationwizard (#1076) --- .../src/static/js/ui-functions.js | 7 + .../templates/helm/csm-1.11.0-values.template | 26 + ....template => csm-powermax-1.10.0.template} | 0 .../operator/csm-powermax-1.11.0.template | 453 ++++++++++++++++++ 4 files changed, 486 insertions(+) rename content/docs/deployment/csminstallationwizard/src/templates/operator/{csm-powermax-1.10.0 .template => csm-powermax-1.10.0.template} (100%) create mode 100644 content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js index 8faae4f6a6..84511f55c2 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js @@ -402,6 +402,9 @@ function displayModules(installationType, driverName, CONSTANTS_PARAM) { $(".cluster-prefix").show(); $(".port-groups").show(); $(".resiliency").hide(); + if (document.getElementById("csm-version").value === "1.11.0") { + $(".resiliency").show(); + } $(".migration").show(); $(".vSphere").show(); $(".storage-capacity").show(); @@ -417,6 +420,10 @@ function displayModules(installationType, driverName, CONSTANTS_PARAM) { $(".observability-operator").show(); $(".observability").hide(); + $(".resiliency").hide(); + if (document.getElementById("csm-version").value === "1.11.0") { + $(".resiliency-operator").show(); + } $(".replication-operator-clusterid").hide(); $(".image-repository").hide(); $(".cert-manager").hide(); diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template index bc9d4a123b..aa90c48ace 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template @@ -111,6 +111,7 @@ csi-powermax: portGroups: "$POWERMAX_PORT_GROUPS" fsGroupPolicy: "$FSGROUP_POLICY" maxPowerMaxVolumesPerNode: $MAX_VOLUMES_PER_NODE + podmonAPIPort: 8083 enableCHAP: $ISCSI_CHAP_ENABLED transportProtocol: "$NODE_TRANSPORT_PROTOCOL" storageCapacity: @@ -147,6 +148,31 @@ csi-powermax: deployAsSidecar: true replication: enabled: $REPLICATION_ENABLED + podmon: + enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-powermax" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powermax.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/powermax-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/powermax.emc.dell.com/csi_sock" + - "--labelvalue=csi-powermax" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powermax.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/powermax-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" migration: enabled: $MIGRATION_ENABLED authorization: diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.0 .template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.0.template similarity index 100% rename from content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.0 .template rename to content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.0.template diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template new file mode 100644 index 0000000000..263561fb99 --- /dev/null +++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template @@ -0,0 +1,453 @@ +# +# Copyright © 2023 Dell Inc. or its subsidiaries. All Rights Reserved. +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# http://www.apache.org/licenses/LICENSE-2.0 +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# +# +apiVersion: storage.dell.com/v1 +kind: ContainerStorageModule +metadata: + name: powermax + namespace: $NAMESPACE +spec: + # Add fields here + driver: + csiDriverType: "powermax" + csiDriverSpec: + # fsGroupPolicy: Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. + # Allowed values: ReadWriteOnceWithFSType, File , None + # Default value: ReadWriteOnceWithFSType + fSGroupPolicy: "$FSGROUP_POLICY" + # storageCapacity: Helps the scheduler to schedule the pod on a node satisfying the topology constraints, only if the requested capacity is available on the storage array + # Allowed values: + # true: enable storage capacity tracking + # false: disable storage capacity tracking + storageCapacity: $STORAGE_CAPACITY_ENABLED + # Config version for CSI PowerMax v2.10.0 driver + configVersion: v2.10.0 + # replica: Define the number of PowerMax controller nodes + # to deploy to the Kubernetes release + # Allowed values: n, where n > 0 + # Default value: None + replicas: $CONTROLLER_COUNT + # Default credential secret for Powermax, if not set it to "" + authSecret: powermax-creds + dnsPolicy: ClusterFirstWithHostNet + forceUpdate: false + forceRemoveDriver: true + common: + # Image for CSI PowerMax driver v2.10.0 + image: dellemc/csi-powermax:v2.10.0 + # imagePullPolicy: Policy to determine if the image should be pulled prior to starting the container. + # Allowed values: + # Always: Always pull the image. + # IfNotPresent: Only pull the image if it does not already exist on the node. + # Never: Never pull the image. + # Default value: None + imagePullPolicy: IfNotPresent + envs: + # X_CSI_MANAGED_ARRAYS: Serial ID of the arrays that will be used for provisioning + # Default value: None + # Examples: "000000000001", "000000000002" + - name: X_CSI_MANAGED_ARRAYS + value: "$POWERMAX_MANAGE_ARRAY_ID" + # X_CSI_POWERMAX_ENDPOINT: Address of the Unisphere server that is managing the PowerMax arrays + # In case of multi-array, provide an endpoint of locally attached array + # Default value: None + # Example: https://0.0.0.1:8443 + - name: X_CSI_POWERMAX_ENDPOINT + value: "$POWERMAX_MANAGE_ARRAY_ENDPOINT_URL" + # X_CSI_K8S_CLUSTER_PREFIX: Define a prefix that is appended onto + # all resources created in the Array + # This should be unique per K8s/CSI deployment + # maximum length of this value is 3 characters + # Default value: None + # Examples: "XYZ", "EMC" + - name: X_CSI_K8S_CLUSTER_PREFIX + value: "$POWERMAX_CLUSTER_PREFIX" + # Specify kubelet config dir path. + # Ensure that the config.yaml file is present at this path. + # Default value: None + - name: KUBELET_CONFIG_DIR + value: /var/lib/kubelet + # X_CSI_POWERMAX_PORTGROUPS: Define the set of existing port groups that the driver will use. + # It is a comma separated list of portgroup names. + # Required only in case of iSCSI port groups + # Allowed values: iSCSI Port Group names + # Default value: None + # Examples: "pg1", "pg1, pg2" + - name: X_CSI_POWERMAX_PORTGROUPS + value: "$POWERMAX_PORT_GROUPS" + # "X_CSI_TRANSPORT_PROTOCOL" can be "FC" or "FIBRE" for fibrechannel, + # "ISCSI" for iSCSI, or "" for autoselection. + # Allowed values: + # "FC" - Fiber Channel protocol + # "FIBER" - Fiber Channel protocol + # "ISCSI" - iSCSI protocol + # "" - Automatic selection of transport protocol + # Default value: "" + - name: X_CSI_TRANSPORT_PROTOCOL + value: "$NODE_TRANSPORT_PROTOCOL" + # X_CSI_POWERMAX_PROXY_SERVICE_NAME: Refers to the name of the proxy service in kubernetes + # Allowed values: "csipowermax-reverseproxy" + # default values: "csipowermax-reverseproxy" + - name: X_CSI_POWERMAX_PROXY_SERVICE_NAME + value: "csipowermax-reverseproxy" + # VMware/vSphere virtualization support + # set X_CSI_VSPHERE_ENABLED to true, if you to enable VMware virtualized environment support via RDM + # Allowed values: + # "true" - vSphere volumes are enabled + # "false" - vSphere volumes are disabled + # Default value: "false" + - name: "X_CSI_VSPHERE_ENABLED" + value: "$VSPHERE_ENABLED" + # X_CSI_VSPHERE_PORTGROUP: An existing portGroup that driver will use for vSphere + # recommended format: csi-x-VC-PG, x can be anything of user choice + # Allowed value: valid existing port group on the array + # Default value: "" + - name: "X_CSI_VSPHERE_PORTGROUP" + value: "$VSPHERE_FC_PORT_GROUP" + # X_CSI_VSPHERE_HOSTNAME: An existing host(initiator group)/ host group(cascaded initiator group) that driver will use for vSphere + # this host should contain initiators from all the ESXs/ESXi host where the cluster is deployed + # recommended format: csi-x-VC-HN, x can be anything of user choice + # Allowed value: valid existing host/host group on the array + # Default value: "" + - name: "X_CSI_VSPHERE_HOSTNAME" + value: "$VSPHERE_FC_HOST_NAME" + # X_CSI_VCENTER_HOST: URL/endpoint of the vCenter where all the ESX are present + # Allowed value: valid vCenter host endpoint + # Default value: "" + - name: "X_CSI_VCENTER_HOST" + value: "$VSPHERE_VCENTER_HOST" + controller: + envs: + # X_CSI_HEALTH_MONITOR_ENABLED: Enable/Disable health monitor of CSI volumes from node plugin- volume usage, volume condition + # Allowed values: + # true: enable checking of health condition of CSI volumes + # false: disable checking of health condition of CSI volumes + # Default value: false + - name: X_CSI_HEALTH_MONITOR_ENABLED + value: "$HEALTH_MONITOR_ENABLED" + # nodeSelector: Define node selection constraints for controller pods. + # For the pod to be eligible to run on a node, the node must have each + # of the indicated key-value pairs as labels. + # Leave as blank to consider all nodes + # Allowed values: map of key-value pairs + # Default value: None + nodeSelector: $NODE_POD_NODE_SELECTOR + # Uncomment if nodes you wish to use have the node-role.kubernetes.io/control-plane taint + # node-role.kubernetes.io/control-plane: "" + + # tolerations: Define tolerations that would be applied to controller deployment + # Leave as blank to install controller on worker nodes + # Allowed values: map of key-value pairs + # Default value: None + tolerations: $NODE_TOLERATIONS + # Uncomment if nodes you wish to use have the node-role.kubernetes.io/control-plane taint + # - key: "node-role.kubernetes.io/control-plane" + # operator: "Exists" + # effect: "NoSchedule" + node: + envs: + # X_CSI_POWERMAX_ISCSI_ENABLE_CHAP: Determine if the driver is going to configure + # ISCSI node databases on the nodes with the CHAP credentials + # If enabled, the CHAP secret must be provided in the credentials secret + # and set to the key "chapsecret" + # Allowed values: + # "true" - CHAP is enabled + # "false" - CHAP is disabled + # Default value: "false" + - name: X_CSI_POWERMAX_ISCSI_ENABLE_CHAP + value: "$ISCSI_CHAP_ENABLED" + # X_CSI_HEALTH_MONITOR_ENABLED: Enable/Disable health monitor of CSI volumes from node plugin- volume usage, volume condition + # Allowed values: + # true: enable checking of health condition of CSI volumes + # false: disable checking of health condition of CSI volumes + # Default value: false + - name: X_CSI_HEALTH_MONITOR_ENABLED + value: "$HEALTH_MONITOR_ENABLED" + # X_CSI_TOPOLOGY_CONTROL_ENABLED provides a way to filter topology keys on a node based on array and transport protocol + # if enabled, user can create custom topology keys by editing node-topology-config configmap. + # Allowed values: + # true: enable the filtration based on config map + # false: disable the filtration based on config map + # Default value: false + - name: X_CSI_TOPOLOGY_CONTROL_ENABLED + value: "$TOPOLOGY_ENABLED" + # X_CSI_MAX_VOLUMES_PER_NODE: Defines the maximum PowerMax volumes that the controller can schedule on the node + # Allowed values: Any value greater than or equal to 0 + # Default value: "0" + - name: X_CSI_MAX_VOLUMES_PER_NODE + value: "$MAX_VOLUMES_PER_NODE" + # nodeSelector: Define node selection constraints for node pods. + # For the pod to be eligible to run on a node, the node must have each + # of the indicated key-value pairs as labels. + # Leave as blank to consider all nodes + # Allowed values: map of key-value pairs + # Default value: None + nodeSelector: $NODE_POD_NODE_SELECTOR + # Uncomment if nodes you wish to use have the node-role.kubernetes.io/control-plane taint + # node-role.kubernetes.io/control-plane: "" + + # tolerations: Define tolerations that would be applied to node daemonset + # Add/Remove tolerations as per requirement + # Leave as blank if you wish to not apply any tolerations + # Allowed values: map of key-value pairs + # Default value: None + tolerations: + - key: "node.kubernetes.io/memory-pressure" + operator: "Exists" + effect: "NoExecute" + - key: "node.kubernetes.io/disk-pressure" + operator: "Exists" + effect: "NoExecute" + - key: "node.kubernetes.io/network-unavailable" + operator: "Exists" + effect: "NoExecute" + sideCars: + # 'pmax' represents a string prepended to each volume created by the CSI driver + - name: provisioner + args: ["--volume-name-prefix=$VOLUME_NAME_PREFIX"] + # health monitor is disabled by default, refer to driver documentation before enabling it + - name: external-health-monitor + enabled: $HEALTH_MONITOR_ENABLED + args: [ "--monitor-interval=60s" ] + + # Uncomment the following to configure how often external-provisioner polls the driver to detect changed capacity + # Configure only when the storageCapacity is set as "true" + # Allowed values: 1m,2m,3m,...,10m,...,60m etc. Default value: 5m + #- name: provisioner + # args: ["--capacity-poll-interval=5m"] + + modules: + # CSI Powermax Reverseproxy is a mandatory module for Powermax + - name: csireverseproxy + # enabled: Always set to true + enabled: true + configVersion: v2.9.0 + forceRemoveModule: true + components: + - name: csipowermax-reverseproxy + # image: Define the container images used for the reverse proxy + # Default value: None + # Example: "csipowermax-reverseproxy:v2.9.0" + image: dellemc/csipowermax-reverseproxy:v2.9.0 + envs: + # "tlsSecret" defines the TLS secret that is created with certificate + # and its associated key + # Default value: None + # Example: "tls-secret" + - name: X_CSI_REVPROXY_TLS_SECRET + value: "csirevproxy-tls-secret" + - name: X_CSI_REVPROXY_PORT + value: "2222" + - name: X_CSI_CONFIG_MAP_NAME + value: "powermax-reverseproxy-config" + + # Authorization: enable csm-authorization for RBAC + - name: authorization + # enabled: Enable/Disable csm-authorization + enabled: $AUTHORIZATION_ENABLED + configVersion: v1.9.0 + components: + - name: karavi-authorization-proxy + image: dellemc/csm-authorization-sidecar:v1.10.0 + envs: + # proxyHost: hostname of the csm-authorization server + - name: "PROXY_HOST" + value: "$AUTHORIZATION_PROXY_HOST" + # skipCertificateValidation: Enable/Disable certificate validation of the csm-authorization server + - name: "SKIP_CERTIFICATE_VALIDATION" + value: "$AUTHORIZATION_SKIP_CERTIFICATE_VALIDATION" + + # Replication: allows configuring replication module + # Replication CRDs must be installed before installing driver + - name: replication + # enabled: Enable/Disable replication feature + # Allowed values: + # true: enable replication feature(install dell-csi-replicator sidecar) + # false: disable replication feature(do not install dell-csi-replicator sidecar) + # Default value: false + enabled: $REPLICATION_ENABLED + configVersion: v1.8.0 + components: + - name: dell-csi-replicator + # image: Image to use for dell-csi-replicator. This shouldn't be changed + # Allowed values: string + # Default value: None + image: dellemc/dell-csi-replicator:v1.8.0 + envs: + # replicationPrefix: prefix to prepend to storage classes parameters + # Allowed values: string + # Default value: replication.storage.dell.com + - name: "X_CSI_REPLICATION_PREFIX" + value: "replication.storage.dell.com" + # replicationContextPrefix: prefix to use for naming of resources created by replication feature + # Allowed values: string + # Default value: powermax + - name: "X_CSI_REPLICATION_CONTEXT_PREFIX" + value: "powermax" + + - name: dell-replication-controller-manager + # image: Defines controller image. This shouldn't be changed + # Allowed values: string + image: dellemc/dell-replication-controller:v1.7.0 + envs: + # TARGET_CLUSTERS_IDS: comma separated list of cluster IDs of the targets clusters. DO NOT include the source(wherever CSM Operator is deployed) cluster ID + # Set the value to "self" in case of stretched/single cluster configuration + # Allowed values: string + - name: "TARGET_CLUSTERS_IDS" + value: "$TARGET_CLUSTER_ID" + # Replication log level + # Allowed values: "error", "warn"/"warning", "info", "debug" + # Default value: "debug" + - name: "REPLICATION_CTRL_LOG_LEVEL" + value: "debug" + # replicas: Defines number of controller replicas + # Allowed values: int + # Default value: 1 + - name: "REPLICATION_CTRL_REPLICAS" + value: "1" + # retryIntervalMin: Initial retry interval of failed reconcile request. + # It doubles with each failure, upto retry-interval-max + # Allowed values: time + - name: "RETRY_INTERVAL_MIN" + value: "1s" + # RETRY_INTERVAL_MAX: Maximum retry interval of failed reconcile request + # Allowed values: time + - name: "RETRY_INTERVAL_MAX" + value: "5m" + + # observability: allows to configure observability + - name: observability + # enabled: Enable/Disable observability + enabled: $OBSERVABILITY_OPERATOR_ENABLED + configVersion: v1.7.0 + components: + - name: topology + # enabled: Enable/Disable topology + enabled: $OBSERVABILITY_OPERATOR_TOPOLOGY + # image: Defines karavi-topology image. This shouldn't be changed + # Allowed values: string + image: dellemc/csm-topology:v1.7.0 + envs: + # topology log level + # Valid values: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, PANIC + # Default value: "INFO" + - name: "TOPOLOGY_LOG_LEVEL" + value: "INFO" + + - name: otel-collector + # enabled: Enable/Disable OpenTelemetry Collector + enabled: $OBSERVABILITY_OPERATOR_OTEL + # image: Defines otel-collector image. This shouldn't be changed + # Allowed values: string + image: otel/opentelemetry-collector:0.42.0 + envs: + # image of nginx proxy image + # Allowed values: string + # Default value: "nginxinc/nginx-unprivileged:1.20" + - name: "NGINX_PROXY_IMAGE" + value: "nginxinc/nginx-unprivileged:1.20" + + - name: metrics-powermax + # enabled: Enable/Disable PowerMax metrics + enabled: $OBSERVABILITY_OPERATOR_METRICS + # image: Defines PowerMax metrics image. This shouldn't be changed + image: dellemc/csm-metrics-powermax:v1.2.0 + envs: + # POWERMAX_MAX_CONCURRENT_QUERIES: set the default max concurrent queries to PowerMax + # Allowed values: int + # Default value: 10 + - name: "POWERMAX_MAX_CONCURRENT_QUERIES" + value: "10" + # POWERMAX_CAPACITY_METRICS_ENABLED: enable/disable collection of capacity metrics + # Allowed values: ture, false + # Default value: true + - name: "POWERMAX_CAPACITY_METRICS_ENABLED" + value: "true" + # POWERMAX_PERFORMANCE_METRICS_ENABLED: enable/disable collection of volume performance metrics + # Allowed values: ture, false + # Default value: true + - name: "POWERMAX_PERFORMANCE_METRICS_ENABLED" + value: "true" + # POWERMAX_CAPACITY_POLL_FREQUENCY: set polling frequency to get capacity metrics data + # Allowed values: int + # Default value: 10 + - name: "POWERMAX_CAPACITY_POLL_FREQUENCY" + value: "10" + # POWERMAX_PERFORMANCE_POLL_FREQUENCY: set polling frequency to get volume performance data + # Allowed values: int + # Default value: 10 + - name: "POWERMAX_PERFORMANCE_POLL_FREQUENCY" + value: "10" + # PowerMax metrics log level + # Valid values: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, PANIC + # Default value: "INFO" + - name: "POWERMAX_LOG_LEVEL" + value: "INFO" + # PowerMax Metrics Output logs in the specified format + # Valid values: TEXT, JSON + # Default value: "TEXT" + - name: "POWERMAX_LOG_FORMAT" + value: "TEXT" + # otel collector address + # Allowed values: String + # Default value: "otel-collector:55680" + - name: "COLLECTOR_ADDRESS" + value: "otel-collector:55680" + # configMap name which has all array/endpoint related info + - name: "X_CSI_CONFIG_MAP_NAME" + value: "powermax-reverseproxy-config" + - name: resiliency + # enabled: Enable/Disable Resiliency feature + # Allowed values: + # true: enable Resiliency feature(deploy podmon sidecar) + # false: disable Resiliency feature(do not deploy podmon sidecar) + # Default value: false + enabled: $OPERATOR_RESILIENCY_ENABLED + configVersion: v1.9.0 + components: + - name: podmon-controller + image: dellemc/podmon:v1.9.0 + imagePullPolicy: IfNotPresent + args: + - "--labelvalue=$LABEL_VALUE" + - "--arrayConnectivityPollRate=$POLL_RATE" + - "--skipArrayConnectionValidation=$SKIP_ARRAY_CONNECTION_VALIDATION" + - "--driverPodLabelValue=$DRIVER_POD_LABEL_VALUE" + - "--ignoreVolumelessPods=$IGNORE_VOLUMELESS_PODS" + - "--arrayConnectivityConnectionLossThreshold=$ARRAY_THRESHOLD" + # Below 4 args should not be modified. + - "--csisock=unix:/var/run/csi/csi.sock" + - "--mode=controller" + - "--driver-config-params=/powermax-config-params/driver-config-params.yaml" + - "--driverPath=csi-powermax.dellemc.com" + - name: podmon-node + image: dellemc/podmon:v1.9.0 + imagePullPolicy: IfNotPresent + envs: + # podmonAPIPort: Defines the port to be used within the kubernetes cluster + # Allowed values: Any valid and free port (string) + # Default value: 8083 + - name: "X_CSI_PODMON_API_PORT" + value: "8083" + args: + - "--labelvalue=$LABEL_VALUE" + - "--arrayConnectivityPollRate=$POLL_RATE" + - "--leaderelection=$LEADER_ELECTION" + - "--driverPodLabelValue=$DRIVER_POD_LABEL_VALUE" + - "--ignoreVolumelessPods=$IGNORE_VOLUMELESS_PODS" + # Below 4 args should not be modified. + - "--csisock=unix:/var/lib/kubelet/plugins/powermax.emc.dell.com/csi_sock" + - "--mode=node" + - "--driver-config-params=/powermax-config-params/driver-config-params.yaml" + - "--driverPath=csi-powermax.dellemc.com" From 0946a61af8b7e5319ece11c664d7a4af40eabff8 Mon Sep 17 00:00:00 2001 From: Surya Gupta <109594002+suryagupta4@users.noreply.github.com> Date: Thu, 25 Apr 2024 16:25:54 +0530 Subject: [PATCH 08/49] add podmon args in csm-1.11 template (#1079) --- .../templates/helm/csm-1.11.0-values.template | 38 +++++++++++++++++++ 1 file changed, 38 insertions(+) diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template index aa90c48ace..1ee80129db 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template @@ -263,6 +263,24 @@ csi-vxflexos: enabled: $VG_SNAPSHOT_ENABLED podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-vxflexos" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/vxflexos-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/vxflexos.emc.dell.com/csi_sock" + - "--labelvalue=csi-vxflexos" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/vxflexos-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" authorization: enabled: $AUTHORIZATION_ENABLED proxyHost: $AUTHORIZATION_PROXY_HOST @@ -425,6 +443,26 @@ csi-unity: maxUnityVolumesPerNode: $MAX_VOLUMES_PER_NODE podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-unity" + - "--driverPath=csi-unity.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/unity-config/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock" + - "--labelvalue=csi-unity" + - "--driverPath=csi-unity.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/unity-config/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" ## K8S/Replication Module ATTRIBUTES ########################################## From b0cef3633f988b3da37b89896f51e3ce12f397da Mon Sep 17 00:00:00 2001 From: boyamurthy <92081029+boyamurthy@users.noreply.github.com> Date: Fri, 26 Apr 2024 11:20:41 +0530 Subject: [PATCH 09/49] Adding podmon entries for PowerStore (#1082) --- .../templates/helm/csm-1.10.0-values.template | 24 +++++++++++++++++++ .../templates/helm/csm-1.11.0-values.template | 24 +++++++++++++++++++ .../templates/helm/csm-1.8.0-values.template | 1 + .../templates/helm/csm-1.9.3-values.template | 24 +++++++++++++++++++ 4 files changed, 73 insertions(+) diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.0-values.template index 1b62e14b91..4f28427adc 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.0-values.template @@ -73,8 +73,32 @@ csi-powerstore: enabled: $STORAGE_CAPACITY_ENABLED podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-powerstore" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powerstore.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/csi-powerstore.dellemc.com/csi_sock" + - "--labelvalue=csi-powerstore" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powerstore.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" maxPowerstoreVolumesPerNode: $MAX_VOLUMES_PER_NODE + podmonAPIPort: 8083 ## K8S/CSI-PowerMax ATTRIBUTES ########################################## diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template index 1ee80129db..d942674bff 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template @@ -73,8 +73,32 @@ csi-powerstore: enabled: $STORAGE_CAPACITY_ENABLED podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-powerstore" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powerstore.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/csi-powerstore.dellemc.com/csi_sock" + - "--labelvalue=csi-powerstore" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powerstore.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" maxPowerstoreVolumesPerNode: $MAX_VOLUMES_PER_NODE + podmonAPIPort: 8083 ## K8S/CSI-PowerMax ATTRIBUTES ########################################## diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.8.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.8.0-values.template index 5b8f25d417..8aa9673e00 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.8.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.8.0-values.template @@ -88,6 +88,7 @@ csi-powerstore: - "--ignoreVolumelessPods=false" maxPowerstoreVolumesPerNode: $MAX_VOLUMES_PER_NODE + podmonAPIPort: 8083 ## K8S/CSI-PowerMax ATTRIBUTES ########################################## diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template index aea7a6f51f..b88527f6d5 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template @@ -73,8 +73,32 @@ csi-powerstore: enabled: $STORAGE_CAPACITY_ENABLED podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-powerstore" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powerstore.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/csi-powerstore.dellemc.com/csi_sock" + - "--labelvalue=csi-powerstore" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powerstore.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" maxPowerstoreVolumesPerNode: $MAX_VOLUMES_PER_NODE + podmonAPIPort: 8083 ## K8S/CSI-PowerMax ATTRIBUTES ########################################## From 98f66a7499860c5a66e57979028dace1e6c7f287 Mon Sep 17 00:00:00 2001 From: Chiman Jain <36687396+chimanjain@users.noreply.github.com> Date: Tue, 30 Apr 2024 18:56:48 +0530 Subject: [PATCH 10/49] update podmon arguments (#1086) --- .../templates/helm/csm-1.11.0-values.template | 24 +++++++++++++++++++ 1 file changed, 24 insertions(+) diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template index d942674bff..e85cf97e48 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template @@ -396,6 +396,30 @@ csi-isilon: # Enable this feature only after contact support for additional information podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-isilon" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-isilon.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/csi-isilon/csi_sock" + - "--labelvalue=csi-isilon" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-isilon.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + podmonAPIPort: 8083 ## K8S/CSI-Unity ATTRIBUTES ########################################## From 433ccdd94cb1505fe00899e6e7253b399a13a8cf Mon Sep 17 00:00:00 2001 From: KshitijaKakde <111420075+KshitijaKakde@users.noreply.github.com> Date: Fri, 3 May 2024 17:20:31 +0530 Subject: [PATCH 11/49] Installation wizard changes (#1088) --- config.toml | 2 +- .../src/csm-versions/default-values.properties | 2 +- .../docs/deployment/csminstallationwizard/src/index.html | 2 +- .../csminstallationwizard/src/static/js/constants.js | 2 +- .../csminstallationwizard/src/static/js/ui-functions.js | 6 +++--- ...sm-1.10.0-values.template => csm-1.10.1-values.template} | 0 content/docs/prerequisites/_index.md | 2 +- 7 files changed, 8 insertions(+), 8 deletions(-) rename content/docs/deployment/csminstallationwizard/src/templates/helm/{csm-1.10.0-values.template => csm-1.10.1-values.template} (100%) diff --git a/config.toml b/config.toml index fc318baf81..1488aec78a 100644 --- a/config.toml +++ b/config.toml @@ -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.11.0)" url = "https://dell.github.io/csm-docs/docs/" [[params.versions]] diff --git a/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties b/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties index a93be80a5f..61fd4afa52 100644 --- a/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties +++ b/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties @@ -1,4 +1,4 @@ -csmVersion=1.10.0 +csmVersion=1.10.1 imageRepository=dellemc controllerCount=1 nodeSelectorLabel=node-role.kubernetes.io/control-plane: diff --git a/content/docs/deployment/csminstallationwizard/src/index.html b/content/docs/deployment/csminstallationwizard/src/index.html index bbe5c6753e..6cebdb07d0 100644 --- a/content/docs/deployment/csminstallationwizard/src/index.html +++ b/content/docs/deployment/csminstallationwizard/src/index.html @@ -93,7 +93,7 @@ - + diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js index 18fa240c1b..b4975024fd 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js @@ -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" diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js index 84511f55c2..e6cc6af39b 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js @@ -479,11 +479,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(); diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.1-values.template similarity index 100% rename from content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.0-values.template rename to content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.10.1-values.template diff --git a/content/docs/prerequisites/_index.md b/content/docs/prerequisites/_index.md index 45f270a75b..a82f4c3dac 100644 --- a/content/docs/prerequisites/_index.md +++ b/content/docs/prerequisites/_index.md @@ -10,7 +10,7 @@ weight: 1 {{}} | Platform | Version | OS Dependencies | |---------------|:----------------:|:------------------------:| -| PowerMax | PowerMax 2500/8500 PowerMaxOS 10 (6079)
PowerMaxOS 10.0.1 (6079)
PowerMaxOS 10.1 (6079)
PowerMax 2000/8000 - 5978.711.xxx
5978.479.xxx
Unisphere 10.0,10.0.1,10.1 | iscsi-initiator-utils
multipathd or powerpath
nvme-cli
nfs-utils | +| PowerMax | PowerMax 2500/8500 PowerMaxOS 10 (6079)
PowerMaxOS 10.0.1 (6079)
PowerMaxOS 10.1 (6079)
PowerMax 2000/8000 - 5978.711.711, 5978.714.714
5978.479.479
Unisphere 10.0,10.0.1,10.1 | iscsi-initiator-utils
multipathd or powerpath
nvme-cli
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
multipathd
nfs-utils | | PowerScale | OneFS 9.3, 9.4, 9.5.0.x (x >= 5) | nfs-utils | From 3b4623aa332e3395a968e99080cd45e7603c5595 Mon Sep 17 00:00:00 2001 From: Rishabh Raj <120644626+rishabhatdell@users.noreply.github.com> Date: Mon, 6 May 2024 07:28:15 +0530 Subject: [PATCH 12/49] updated docs for csm 1.11 (#1083) --- config.toml | 6 +- .../configuration/powerflex/_index.md | 8 +- .../configuration/powermax/_index.md | 8 +- .../configuration/powerscale/_index.md | 8 +- content/docs/authorization/release/_index.md | 2 +- .../templates/helm/csm-1.11.0-values.template | 32 +- .../operator/csm-isilon-1.11.0.template | 470 ++++++++++++++++++ .../operator/csm-powermax-1.11.0.template | 22 +- .../operator/csm-powerstore-1.11.0.template | 195 ++++++++ content/docs/deployment/csmoperator/_index.md | 42 +- .../csmoperator/modules/replication.md | 4 +- .../csmoperator/modules/resiliency.md | 2 +- .../replication/install-repctl.md | 4 +- .../replication/install-script.md | 4 +- .../helm/modules/upgrade/observability.md | 2 +- .../helm/modules/upgrade/replication.md | 2 +- .../docs/deployment/offline/drivers/_index.md | 6 +- content/docs/observability/release/_index.md | 2 +- content/docs/resiliency/release/_index.md | 2 +- 19 files changed, 743 insertions(+), 78 deletions(-) create mode 100644 content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template create mode 100644 content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template diff --git a/config.toml b/config.toml index 1488aec78a..ad977d6d2a 100644 --- a/config.toml +++ b/config.toml @@ -176,15 +176,15 @@ enable = false url = "https://dell.github.io/csm-docs/docs/" [[params.versions]] - version = "v1.9.4" + version = "v1.10.0" url = "https://dell.github.io/csm-docs/v1" [[params.versions]] - version = "v1.8.0" + version = "v1.9.4" url = "https://dell.github.io/csm-docs/v2" [[params.versions]] - version = "v1.7.1" + version = "v1.8.0" url = "https://dell.github.io/csm-docs/v3" [[menu.main]] diff --git a/content/docs/authorization/configuration/powerflex/_index.md b/content/docs/authorization/configuration/powerflex/_index.md index 98d545dbd6..408944939e 100644 --- a/content/docs/authorization/configuration/powerflex/_index.md +++ b/content/docs/authorization/configuration/powerflex/_index.md @@ -119,8 +119,8 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization enabled: true # sidecarProxyImage: the container image used for the csm-authorization-sidecar. - # Default value: dellemc/csm-authorization-sidecar:v1.10.0 - sidecarProxyImage: dellemc/csm-authorization-sidecar:v1.10.0 + # Default value: dellemc/csm-authorization-sidecar:v1.11.0 + sidecarProxyImage: dellemc/csm-authorization-sidecar:v1.11.0 # proxyHost: hostname of the csm-authorization server # Default value: None @@ -156,10 +156,10 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization - name: authorization # enable: Enable/Disable csm-authorization enabled: true - configVersion: v1.10.0 + configVersion: v1.11.0 components: - name: karavi-authorization-proxy - image: dellemc/csm-authorization-sidecar:v1.10.0 + image: dellemc/csm-authorization-sidecar:v1.11.0 envs: # proxyHost: hostname of the csm-authorization server - name: "PROXY_HOST" diff --git a/content/docs/authorization/configuration/powermax/_index.md b/content/docs/authorization/configuration/powermax/_index.md index d37ce9ff9c..44d4cd8e1f 100644 --- a/content/docs/authorization/configuration/powermax/_index.md +++ b/content/docs/authorization/configuration/powermax/_index.md @@ -93,8 +93,8 @@ Create the karavi-authorization-config secret using this command: enabled: true # sidecarProxyImage: the container image used for the csm-authorization-sidecar. - # Default value: dellemc/csm-authorization-sidecar:v1.10.0 - sidecarProxyImage: dellemc/csm-authorization-sidecar:v1.10.0 + # Default value: dellemc/csm-authorization-sidecar:v1.11.0 + sidecarProxyImage: dellemc/csm-authorization-sidecar:v1.11.0 # proxyHost: hostname of the csm-authorization server # Default value: None @@ -130,10 +130,10 @@ Create the karavi-authorization-config secret using this command: - name: authorization # enable: Enable/Disable csm-authorization enabled: true - configVersion: v1.10.0 + configVersion: v1.11.0 components: - name: karavi-authorization-proxy - image: dellemc/csm-authorization-sidecar:v1.10.0 + image: dellemc/csm-authorization-sidecar:v1.11.0 envs: # proxyHost: hostname of the csm-authorization server - name: "PROXY_HOST" diff --git a/content/docs/authorization/configuration/powerscale/_index.md b/content/docs/authorization/configuration/powerscale/_index.md index 87941a9c85..b655108a63 100644 --- a/content/docs/authorization/configuration/powerscale/_index.md +++ b/content/docs/authorization/configuration/powerscale/_index.md @@ -127,8 +127,8 @@ kubectl -n isilon create secret generic karavi-authorization-config --from-file= enabled: true # sidecarProxyImage: the container image used for the csm-authorization-sidecar. - # Default value: dellemc/csm-authorization-sidecar:v1.10.0 - sidecarProxyImage: dellemc/csm-authorization-sidecar:v1.10.0 + # Default value: dellemc/csm-authorization-sidecar:v1.11.0 + sidecarProxyImage: dellemc/csm-authorization-sidecar:v1.11.0 # proxyHost: hostname of the csm-authorization server # Default value: None @@ -162,10 +162,10 @@ kubectl -n isilon create secret generic karavi-authorization-config --from-file= - name: authorization # enable: Enable/Disable csm-authorization enabled: true - configVersion: v1.10.0 + configVersion: v1.11.0 components: - name: karavi-authorization-proxy - image: dellemc/csm-authorization-sidecar:v1.10.0 + image: dellemc/csm-authorization-sidecar:v1.11.0 envs: # proxyHost: hostname of the csm-authorization server - name: "PROXY_HOST" diff --git a/content/docs/authorization/release/_index.md b/content/docs/authorization/release/_index.md index a642a295af..5d32effb18 100644 --- a/content/docs/authorization/release/_index.md +++ b/content/docs/authorization/release/_index.md @@ -6,7 +6,7 @@ Description: > Dell Container Storage Modules (CSM) release notes for authorization --- -## Release Notes - CSM Authorization 1.10.0 +## Release Notes - CSM Authorization 1.11.0 diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template index e85cf97e48..b76d70d6eb 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template @@ -4,10 +4,10 @@ ########################################## csi-powerstore: enabled: $POWERSTORE_ENABLED - version: v2.10.0 + version: v2.11.0 images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-powerstore:v2.10.0 + driver: dellemc/csi-powerstore:v2.11.0 # CSI sidecars attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0 @@ -17,9 +17,9 @@ csi-powerstore: healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.8.0 + replication: dellemc/dell-csi-replicator:v1.9.0 vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0 - podmon: dellemc/podmon:v1.9.0 + podmon: dellemc/podmon:v1.10.0 metadataretriever: dellemc/csi-metadata-retriever:v1.6.0 ## Controller ATTRIBUTES controller: @@ -114,10 +114,10 @@ csi-powermax: managementServers: - endpoint: $POWERMAX_MANAGEMENT_SERVERS_ENDPOINT_URL - endpoint: $TARGET_UNISPHERE - version: v2.10.0 + version: v2.11.0 images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-powermax:v2.10.0 + driver: dellemc/csi-powermax:v2.11.0 csireverseproxy: dellemc/csipowermax-reverseproxy:v2.9.0 # CSI sidecars attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 @@ -127,7 +127,7 @@ csi-powermax: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.8.0 + replication: dellemc/dell-csi-replicator:v1.9.0 authorization: dellemc/csm-authorization-sidecar:v1.10.0 migration: dellemc/dell-csi-migrator:v1.3.0 noderescan: dellemc/dell-csi-node-rescanner:v1.2.0 @@ -216,10 +216,10 @@ csi-powermax: ########################################## csi-vxflexos: enabled: $POWERFLEX_ENABLED - version: v2.10.0 + version: v2.11.0 images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-vxflexos:v2.10.0 + driver: dellemc/csi-vxflexos:v2.11.0 # "powerflexSdc" defines the SDC image for init container. powerflexSdc: dellemc/sdc:4.5 # CSI sidecars @@ -230,9 +230,9 @@ csi-vxflexos: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.8.0 + replication: dellemc/dell-csi-replicator:v1.9.0 vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0 - podmon: dellemc/podmon:v1.9.0 + podmon: dellemc/podmon:v1.10.0 authorization: dellemc/csm-authorization-sidecar:v1.10.0 certSecretCount: $CERT_SECRET_COUNT controller: @@ -315,10 +315,10 @@ csi-vxflexos: ########################################## csi-isilon: enabled: $POWERSCALE_ENABLED - version: "v2.10.0" + version: "v2.11.0" images: # "driver" defines the container image, used for the driver container. - driver: dellemc/csi-isilon:v2.10.0 + driver: dellemc/csi-isilon:v2.11.0 # CSI sidecars attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0 provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0 @@ -327,8 +327,8 @@ csi-isilon: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 # CSM sidecars - replication: dellemc/dell-csi-replicator:v1.8.0 - podmon: dellemc/podmon:v1.9.0 + replication: dellemc/dell-csi-replicator:v1.9.0 + podmon: dellemc/podmon:v1.10.0 authorization: dellemc/csm-authorization-sidecar:v1.10.0 metadataretriever: dellemc/csi-metadata-retriever:v1.4.0 encryption: dellemc/csm-encryption:v0.3.0 @@ -437,7 +437,7 @@ csi-unity: registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0 healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0 # CSM sidecars - podmon: dellemc/podmon:v1.9.0 + podmon: dellemc/podmon:v1.10.0 certSecretCount: $CERT_SECRET_COUNT allowedNetworks: [] fsGroupPolicy: $FSGROUP_POLICY diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template new file mode 100644 index 0000000000..1b2266edfb --- /dev/null +++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template @@ -0,0 +1,470 @@ +apiVersion: storage.dell.com/v1 +kind: ContainerStorageModule +metadata: + name: isilon + namespace: $NAMESPACE +spec: + driver: + csiDriverType: "isilon" + csiDriverSpec: + # fsGroupPolicy: Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. + # Allowed values: ReadWriteOnceWithFSType, File , None + # Default value: ReadWriteOnceWithFSType + fSGroupPolicy: "$FSGROUP_POLICY" + # storageCapacity: Helps the scheduler to schedule the pod on a node satisfying the topology constraints, only if the requested capacity is available on the storage array + # Allowed values: + # true: enable storage capacity tracking + # false: disable storage capacity tracking + storageCapacity: $STORAGE_CAPACITY_ENABLED + # Config version for CSI PowerScale v2.11.0 driver + configVersion: v2.11.0 + authSecret: isilon-creds + replicas: $CONTROLLER_COUNT + dnsPolicy: ClusterFirstWithHostNet + # Uninstall CSI Driver and/or modules when CR is deleted + forceRemoveDriver: true + common: + # Image for CSI PowerScale driver v2.11.0 + image: "dellemc/csi-isilon:v2.11.0" + imagePullPolicy: IfNotPresent + envs: + # X_CSI_VERBOSE: Indicates what content of the OneFS REST API message should be logged in debug level logs + # Allowed Values: + # 0: log full content of the HTTP request and response + # 1: log without the HTTP response body + # 2: log only 1st line of the HTTP request and response + # Default value: 0 + - name: X_CSI_VERBOSE + value: "1" + + # X_CSI_ISI_PORT: Specify the HTTPs port number of the PowerScale OneFS API server + # This value acts as a default value for endpointPort, if not specified for a cluster config in secret + # Allowed value: valid port number + # Default value: 8080 + - name: X_CSI_ISI_PORT + value: "8080" + + # X_CSI_ISI_PATH: The base path for the volumes to be created on PowerScale cluster. + # This value acts as a default value for isiPath, if not specified for a cluster config in secret + # Ensure that this path exists on PowerScale cluster. + # Allowed values: unix absolute path + # Default value: /ifs + # Examples: /ifs/data/csi, /ifs/engineering + - name: X_CSI_ISI_PATH + value: "/ifs/data/csi" + + # X_CSI_ISI_NO_PROBE_ON_START: Indicates whether the controller/node should probe all the PowerScale clusters during driver initialization + # Allowed values: + # true : do not probe all PowerScale clusters during driver initialization + # false: probe all PowerScale clusters during driver initialization + # Default value: false + - name: X_CSI_ISI_NO_PROBE_ON_START + value: "false" + + # X_CSI_ISI_AUTOPROBE: automatically probe the PowerScale cluster if not done already during CSI calls. + # Allowed values: + # true : enable auto probe. + # false: disable auto probe. + # Default value: false + - name: X_CSI_ISI_AUTOPROBE + value: "true" + + # X_CSI_ISI_SKIP_CERTIFICATE_VALIDATION: Specify whether the PowerScale OneFS API server's certificate chain and host name should be verified. + # Formerly this attribute was named as "X_CSI_ISI_INSECURE" + # This value acts as a default value for skipCertificateValidation, if not specified for a cluster config in secret + # Allowed values: + # true: skip OneFS API server's certificate verification + # false: verify OneFS API server's certificates + # Default value: true + - name: X_CSI_ISI_SKIP_CERTIFICATE_VALIDATION + value: "true" + + # X_CSI_CUSTOM_TOPOLOGY_ENABLED: Specify if custom topology label .dellemc.com/: + # has to be used for making connection to backend PowerScale Array. + # If X_CSI_CUSTOM_TOPOLOGY_ENABLED is set to true, then do not specify allowedTopologies in storage class. + # Allowed values: + # true : enable custom topology + # false: disable custom topology + # Default value: false + - name: X_CSI_CUSTOM_TOPOLOGY_ENABLED + value: "false" + + # Specify kubelet config dir path. + # Ensure that the config.yaml file is present at this path. + # Default value: None + - name: KUBELET_CONFIG_DIR + value: "/var/lib/kubelet" + + # certSecretCount: Represents number of certificate secrets, which user is going to create for + # ssl authentication. (isilon-cert-0..isilon-cert-n) + # Allowed values: n, where n > 0 + # Default value: None + - name: "CERT_SECRET_COUNT" + value: "1" + + # CSI driver log level + # Allowed values: "error", "warn"/"warning", "info", "debug" + # Default value: "debug" + - name: "CSI_LOG_LEVEL" + value: "debug" + + controller: + envs: + # X_CSI_ISI_QUOTA_ENABLED: Indicates whether the provisioner should attempt to set (later unset) quota + # on a newly provisioned volume. + # This requires SmartQuotas to be enabled on PowerScale cluster. + # Allowed values: + # true: set quota for volume + # false: do not set quota for volume + - name: X_CSI_ISI_QUOTA_ENABLED + value: "true" + + # X_CSI_ISI_ACCESS_ZONE: The name of the access zone a volume can be created in. + # If storageclass is missing with AccessZone parameter, then value of X_CSI_ISI_ACCESS_ZONE is used for the same. + # Default value: System + # Examples: System, zone1 + - name: X_CSI_ISI_ACCESS_ZONE + value: "System" + + # X_CSI_ISI_VOLUME_PATH_PERMISSIONS: The permissions for isi volume directory path + # This value acts as a default value for isiVolumePathPermissions, if not specified for a cluster config in secret + # Allowed values: valid octal mode number + # Default value: "0777" + # Examples: "0777", "777", "0755" + - name: X_CSI_ISI_VOLUME_PATH_PERMISSIONS + value: "0777" + + # X_CSI_HEALTH_MONITOR_ENABLED: Enable/Disable health monitor of CSI volumes from Controller plugin- volume status, volume condition. + # Install the 'external-health-monitor' sidecar accordingly. + # Allowed values: + # true: enable checking of health condition of CSI volumes + # false: disable checking of health condition of CSI volumes + # Default value: false + - name: X_CSI_HEALTH_MONITOR_ENABLED + value: "$HEALTH_MONITOR_ENABLED" + + # X_CSI_ISI_IGNORE_UNRESOLVABLE_HOSTS: Ignore unresolvable hosts on the OneFS. + # When set to true, OneFS allows new host to add to existing export list though any of the existing hosts from the + # same exports are unresolvable/doesn't exist anymore. + # Allowed values: + # true: ignore existing unresolvable hosts and append new host to the existing export + # false: exhibits OneFS default behavior i.e. if any of existing hosts are unresolvable while adding new one it fails + # Default value: false + - name: X_CSI_ISI_IGNORE_UNRESOLVABLE_HOSTS + value: "false" + + # X_CSI_MAX_PATH_LIMIT: this parameter is used for setting the maximum Path length for the given volume. + # Default value: 192 + # Examples: 192, 256 + - name: X_CSI_MAX_PATH_LIMIT + value: "192" + + # nodeSelector: Define node selection constraints for pods of controller deployment. + # For the pod to be eligible to run on a node, the node must have each + # of the indicated key-value pairs as labels. + # Leave as blank to consider all nodes + # Allowed values: map of key-value pairs + # Default value: None + nodeSelector:$CONTROLLER_POD_NODE_SELECTOR + + # tolerations: Define tolerations for the controller deployment, if required. + # Default value: None + tolerations:$CONTROLLER_TOLERATIONS + + node: + envs: + # X_CSI_MAX_VOLUMES_PER_NODE: Specify default value for maximum number of volumes that controller can publish to the node. + # If value is zero CO SHALL decide how many volumes of this type can be published by the controller to the node. + # This limit is applicable to all the nodes in the cluster for which node label 'max-isilon-volumes-per-node' is not set. + # Allowed values: n, where n >= 0 + # Default value: 0 + - name: X_CSI_MAX_VOLUMES_PER_NODE + value: "$MAX_VOLUMES_PER_NODE" + + # X_CSI_ALLOWED_NETWORKS: Custom networks for PowerScale export + # Specify list of networks which can be used for NFS I/O traffic; CIDR format should be used. + # Allowed values: list of one or more networks + # Default value: None + # Provide them in the following format: "[net1, net2]" + # CIDR format should be used + # eg: "[192.168.1.0/24, 192.168.100.0/22]" + - name: X_CSI_ALLOWED_NETWORKS + value: "" + + # X_CSI_HEALTH_MONITOR_ENABLED: Enable/Disable health monitor of CSI volumes from Controller plugin- volume status, volume condition. + # Install the 'external-health-monitor' sidecar accordingly. + # Allowed values: + # true: enable checking of health condition of CSI volumes + # false: disable checking of health condition of CSI volumes + # Default value: false + - name: X_CSI_HEALTH_MONITOR_ENABLED + value: "$HEALTH_MONITOR_ENABLED" + + # X_CSI_MAX_PATH_LIMIT: this parameter is used for setting the maximum Path length for the given volume. + # Default value: 192 + # Examples: 192, 256 + - name: X_CSI_MAX_PATH_LIMIT + value: "192" + + # nodeSelector: Define node selection constraints for pods of node daemonset + # For the pod to be eligible to run on a node, the node must have each + # of the indicated key-value pairs as labels. + # Leave as blank to consider all nodes + # Allowed values: map of key-value pairs + # Default value: None + nodeSelector:$NODE_POD_NODE_SELECTOR + + # tolerations: Define tolerations for the node daemonset, if required. + # Default value: None + tolerations:$NODE_TOLERATIONS + # - key: "node.kubernetes.io/memory-pressure" + # operator: "Exists" + # effect: "NoExecute" + # - key: "node.kubernetes.io/disk-pressure" + # operator: "Exists" + # effect: "NoExecute" + # - key: "node.kubernetes.io/network-unavailable" + # operator: "Exists" + # effect: "NoExecute" + + sideCars: + - name: provisioner + args: ["--volume-name-prefix=$VOLUME_NAME_PREFIX"] + # health monitor is disabled by default, refer to driver documentation before enabling it + - name: external-health-monitor + enabled: $HEALTH_MONITOR_ENABLED + args: ["--monitor-interval=60s"] + # Uncomment the following to configure how often external-provisioner polls the driver to detect changed capacity + # Configure when the storageCapacity is set as "true" + # Allowed values: 1m,2m,3m,...,10m,...,60m etc. Default value: 5m + #- name: provisioner + # args: ["--capacity-poll-interval=5m"] + + modules: + # Authorization: enable csm-authorization for RBAC + - name: authorization + # enable: Enable/Disable csm-authorization + enabled: $AUTHORIZATION_ENABLED + configVersion: v1.10.0 + components: + - name: karavi-authorization-proxy + image: dellemc/csm-authorization-sidecar:v1.10.0 + envs: + # proxyHost: hostname of the csm-authorization server + - name: "PROXY_HOST" + value: "$AUTHORIZATION_PROXY_HOST" + + # skipCertificateValidation: Enable/Disable certificate validation of the csm-authorization server + - name: "SKIP_CERTIFICATE_VALIDATION" + value: "$AUTHORIZATION_SKIP_CERTIFICATE_VALIDATION" + + # replication: allows to configure replication + # Replication CRDs must be installed before installing driver + - name: replication + # enabled: Enable/Disable replication feature + # Allowed values: + # true: enable replication feature(install dell-csi-replicator sidecar) + # false: disable replication feature(do not install dell-csi-replicator sidecar) + # Default value: false + enabled: $REPLICATION_ENABLED + configVersion: v1.9.0 + components: + - name: dell-csi-replicator + # image: Image to use for dell-csi-replicator. This shouldn't be changed + # Allowed values: string + # Default value: None + image: dellemc/dell-csi-replicator:v1.9.0 + envs: + # replicationPrefix: prefix to prepend to storage classes parameters + # Allowed values: string + # Default value: replication.storage.dell.com + - name: "X_CSI_REPLICATION_PREFIX" + value: "replication.storage.dell.com" + # replicationContextPrefix: prefix to use for naming of resources created by replication feature + # Allowed values: string + # Default value: powerscale + - name: "X_CSI_REPLICATION_CONTEXT_PREFIX" + value: "powerscale" + + - name: dell-replication-controller-manager + # image: Defines controller image. This shouldn't be changed + # Allowed values: string + image: dellemc/dell-replication-controller:v1.7.0 + envs: + # TARGET_CLUSTERS_IDS: comma separated list of cluster IDs of the targets clusters. DO NOT include the source(wherever CSM Operator is deployed) cluster ID + # Set the value to "self" in case of stretched/single cluster configuration + # Allowed values: string + - name: "TARGET_CLUSTERS_IDS" + value: "$TARGET_CLUSTER_ID" + # Replication log level + # Allowed values: "error", "warn"/"warning", "info", "debug" + # Default value: "debug" + - name: "REPLICATION_CTRL_LOG_LEVEL" + value: "debug" + + # replicas: Defines number of controller replicas + # Allowed values: int + # Default value: 1 + - name: "REPLICATION_CTRL_REPLICAS" + value: "1" + # retryIntervalMin: Initial retry interval of failed reconcile request. + # It doubles with each failure, upto retry-interval-max + # Allowed values: time + - name: "RETRY_INTERVAL_MIN" + value: "1s" + # RETRY_INTERVAL_MAX: Maximum retry interval of failed reconcile request + # Allowed values: time + - name: "RETRY_INTERVAL_MAX" + value: "5m" + + # observability: allows to configure observability + - name: observability + # enabled: Enable/Disable observability + enabled: $OBSERVABILITY_OPERATOR_ENABLED + configVersion: v1.7.0 + components: + - name: topology + # enabled: Enable/Disable topology + enabled: $OBSERVABILITY_OPERATOR_TOPOLOGY + # image: Defines karavi-topology image. This shouldn't be changed + # Allowed values: string + image: dellemc/csm-topology:v1.7.0 + envs: + # topology log level + # Valid values: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, PANIC + # Default value: "INFO" + - name: "TOPOLOGY_LOG_LEVEL" + value: "INFO" + + - name: otel-collector + # enabled: Enable/Disable OpenTelemetry Collector + enabled: $OBSERVABILITY_OPERATOR_OTEL + # image: Defines otel-collector image. This shouldn't be changed + # Allowed values: string + image: otel/opentelemetry-collector:0.42.0 + envs: + # image of nginx proxy image + # Allowed values: string + # Default value: "nginxinc/nginx-unprivileged:1.20" + - name: "NGINX_PROXY_IMAGE" + value: "nginxinc/nginx-unprivileged:1.20" + + - name: cert-manager + # enabled: Enable/Disable cert-manager + # Allowed values: + # true: enable deployment of cert-manager + # false: disable deployment of cert-manager only if it's already deployed + # Default value: false + enabled: $OBSERVABILITY_OPERATOR_ENABLED + + - name: metrics-powerscale + # enabled: Enable/Disable PowerScale metrics + enabled: $OBSERVABILITY_OPERATOR_METRICS + # image: Defines PowerScale metrics image. This shouldn't be changed + # Allowed values: string + image: dellemc/csm-metrics-powerscale:v1.4.0 + envs: + # POWERSCALE_MAX_CONCURRENT_QUERIES: set the default max concurrent queries to PowerScale + # Allowed values: int + # Default value: 10 + - name: "POWERSCALE_MAX_CONCURRENT_QUERIES" + value: "10" + # POWERSCALE_CAPACITY_METRICS_ENABLED: enable/disable collection of capacity metrics + # Allowed values: ture, false + # Default value: true + - name: "POWERSCALE_CAPACITY_METRICS_ENABLED" + value: "true" + # POWERSCALE_PERFORMANCE_METRICS_ENABLED: enable/disable collection of performance metrics + # Allowed values: ture, false + # Default value: true + - name: "POWERSCALE_PERFORMANCE_METRICS_ENABLED" + value: "true" + # POWERSCALE_CLUSTER_CAPACITY_POLL_FREQUENCY: set polling frequency to get cluster capacity metrics data + # Allowed values: int + # Default value: 30 + - name: "POWERSCALE_CLUSTER_CAPACITY_POLL_FREQUENCY" + value: "30" + # POWERSCALE_CLUSTER_PERFORMANCE_POLL_FREQUENCY: set polling frequency to get cluster performance metrics data + # Allowed values: int + # Default value: 20 + - name: "POWERSCALE_CLUSTER_PERFORMANCE_POLL_FREQUENCY" + value: "20" + # POWERSCALE_QUOTA_CAPACITY_POLL_FREQUENCY: set polling frequency to get Quota capacity metrics data + # Allowed values: int + # Default value: 20 + - name: "POWERSCALE_QUOTA_CAPACITY_POLL_FREQUENCY" + value: "30" + # ISICLIENT_INSECURE: set true/false to skip/verify OneFS API server's certificates + # Allowed values: ture, false + # Default value: true + - name: "ISICLIENT_INSECURE" + value: "true" + # ISICLIENT_AUTH_TYPE: set 0/1 to enables session-based/basic Authentication + # Allowed values: ture, false + # Default value: true + - name: "ISICLIENT_AUTH_TYPE" + value: "1" + # ISICLIENT_VERBOSE: set 0/1/2 decide High/Medium/Low content of the OneFS REST API message should be logged in debug level logs + # Allowed values: 0,1,2 + # Default value: 0 + - name: "ISICLIENT_VERBOSE" + value: "0" + # PowerScale metrics log level + # Valid values: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, PANIC + # Default value: "INFO" + - name: "POWERSCALE_LOG_LEVEL" + value: "INFO" + # PowerScale Metrics Output logs in the specified format + # Valid values: TEXT, JSON + # Default value: "TEXT" + - name: "POWERSCALE_LOG_FORMAT" + value: "TEXT" + # Otel collector address + # Allowed values: String + # Default value: "otel-collector:55680" + - name: "COLLECTOR_ADDRESS" + value: "otel-collector:55680" + - name: resiliency + # enabled: Enable/Disable Resiliency feature + # Allowed values: + # true: enable Resiliency feature(deploy podmon sidecar) + # false: disable Resiliency feature(do not deploy podmon sidecar) + # Default value: false + enabled: $OPERATOR_RESILIENCY_ENABLED + configVersion: v1.10.0 + components: + - name: podmon-controller + image: dellemc/podmon:v1.10.0 + imagePullPolicy: IfNotPresent + args: + - "--labelvalue=$LABEL_VALUE" + - "--arrayConnectivityPollRate=$POLL_RATE" + - "--skipArrayConnectionValidation=$SKIP_ARRAY_CONNECTION_VALIDATION" + - "--driverPodLabelValue=$DRIVER_POD_LABEL_VALUE" + - "--ignoreVolumelessPods=$IGNORE_VOLUMELESS_PODS" + - "--arrayConnectivityConnectionLossThreshold=$ARRAY_THRESHOLD" + # Below 4 args should not be modified. + - "--csisock=unix:/var/run/csi/csi.sock" + - "--mode=controller" + - "--driverPath=csi-isilon.dellemc.com" + - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml" + - name: podmon-node + image: dellemc/podmon:v1.10.0 + imagePullPolicy: IfNotPresent + envs: + # podmonAPIPort: Defines the port to be used within the kubernetes cluster + # Allowed values: Any valid and free port (string) + # Default value: 8083 + - name: "X_CSI_PODMON_API_PORT" + value: "8083" + args: + - "--labelvalue=$LABEL_VALUE" + - "--arrayConnectivityPollRate=$POLL_RATE" + - "--leaderelection=$LEADER_ELECTION" + - "--driverPodLabelValue=$DRIVER_POD_LABEL_VALUE" + - "--ignoreVolumelessPods=$IGNORE_VOLUMELESS_PODS" + # Below 4 args should not be modified. + - "--csisock=unix:/var/lib/kubelet/plugins/csi-isilon/csi_sock" + - "--mode=node" + - "--driverPath=csi-isilon.dellemc.com" + - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml" diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template index 263561fb99..55264ee3af 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template @@ -31,8 +31,8 @@ spec: # true: enable storage capacity tracking # false: disable storage capacity tracking storageCapacity: $STORAGE_CAPACITY_ENABLED - # Config version for CSI PowerMax v2.10.0 driver - configVersion: v2.10.0 + # Config version for CSI PowerMax v2.11.0 driver + configVersion: v2.11.0 # replica: Define the number of PowerMax controller nodes # to deploy to the Kubernetes release # Allowed values: n, where n > 0 @@ -44,8 +44,8 @@ spec: forceUpdate: false forceRemoveDriver: true common: - # Image for CSI PowerMax driver v2.10.0 - image: dellemc/csi-powermax:v2.10.0 + # Image for CSI PowerMax driver v2.11.0 + image: dellemc/csi-powermax:v2.11.0 # imagePullPolicy: Policy to determine if the image should be pulled prior to starting the container. # Allowed values: # Always: Always pull the image. @@ -256,10 +256,10 @@ spec: - name: authorization # enabled: Enable/Disable csm-authorization enabled: $AUTHORIZATION_ENABLED - configVersion: v1.9.0 + configVersion: v1.11.0 components: - name: karavi-authorization-proxy - image: dellemc/csm-authorization-sidecar:v1.10.0 + image: dellemc/csm-authorization-sidecar:v1.11.0 envs: # proxyHost: hostname of the csm-authorization server - name: "PROXY_HOST" @@ -277,13 +277,13 @@ spec: # false: disable replication feature(do not install dell-csi-replicator sidecar) # Default value: false enabled: $REPLICATION_ENABLED - configVersion: v1.8.0 + configVersion: v1.9.0 components: - name: dell-csi-replicator # image: Image to use for dell-csi-replicator. This shouldn't be changed # Allowed values: string # Default value: None - image: dellemc/dell-csi-replicator:v1.8.0 + image: dellemc/dell-csi-replicator:v1.9.0 envs: # replicationPrefix: prefix to prepend to storage classes parameters # Allowed values: string @@ -414,10 +414,10 @@ spec: # false: disable Resiliency feature(do not deploy podmon sidecar) # Default value: false enabled: $OPERATOR_RESILIENCY_ENABLED - configVersion: v1.9.0 + configVersion: v1.10.0 components: - name: podmon-controller - image: dellemc/podmon:v1.9.0 + image: dellemc/podmon:v1.10.0 imagePullPolicy: IfNotPresent args: - "--labelvalue=$LABEL_VALUE" @@ -432,7 +432,7 @@ spec: - "--driver-config-params=/powermax-config-params/driver-config-params.yaml" - "--driverPath=csi-powermax.dellemc.com" - name: podmon-node - image: dellemc/podmon:v1.9.0 + image: dellemc/podmon:v1.10.0 imagePullPolicy: IfNotPresent envs: # podmonAPIPort: Defines the port to be used within the kubernetes cluster diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template new file mode 100644 index 0000000000..0a357fef38 --- /dev/null +++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template @@ -0,0 +1,195 @@ +# +# +# Copyright © 2023 Dell Inc. or its subsidiaries. All Rights Reserved. +# +# Licensed under the Apache License, Version 2.0 (the "License"); +# you may not use this file except in compliance with the License. +# You may obtain a copy of the License at +# http://www.apache.org/licenses/LICENSE-2.0 +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +# +# +apiVersion: storage.dell.com/v1 +kind: ContainerStorageModule +metadata: + name: powerstore + namespace: $NAMESPACE +spec: + driver: + csiDriverType: "powerstore" + csiDriverSpec: + # fsGroupPolicy: Defines if the underlying volume supports changing ownership and permission of the volume before being mounted. + # Allowed values: ReadWriteOnceWithFSType, File , None + # Default value: ReadWriteOnceWithFSType + fSGroupPolicy: "$FSGROUP_POLICY" + # storageCapacity: Helps the scheduler to schedule the pod on a node satisfying the topology constraints, only if the requested capacity is available on the storage array + # Allowed values: + # true: enable storage capacity tracking + # false: disable storage capacity tracking + storageCapacity: $STORAGE_CAPACITY_ENABLED + # Config version for CSI PowerStore v2.11.0 driver + configVersion: v2.11.0 + # authSecret: This is the secret used to validate the default PowerStore secret used for installation + # Allowed values: -config + # For example: If the metadataName is set to powerstore, authSecret value should be set to powerstore-config + authSecret: powerstore-config + # Controller count + replicas: $CONTROLLER_COUNT + dnsPolicy: ClusterFirstWithHostNet + forceUpdate: false + forceRemoveDriver: true + common: + # Image for CSI PowerStore driver v2.11.0 + image: "dellemc/csi-powerstore:v2.11.0" + imagePullPolicy: IfNotPresent + envs: + - name: X_CSI_POWERSTORE_NODE_NAME_PREFIX + value: "csi-node" + - name: X_CSI_FC_PORTS_FILTER_FILE_PATH + value: "/etc/fc-ports-filter" + - name: KUBELET_CONFIG_DIR + value: /var/lib/kubelet + - name: CSI_LOG_LEVEL + value: debug + + sideCars: + - name: provisioner + args: ["--volume-name-prefix=$VOLUME_NAME_PREFIX"] + # health monitor is disabled by default, refer to driver documentation before enabling it + - name: external-health-monitor + enabled: $HEALTH_MONITOR_ENABLED + args: ["--monitor-interval=60s"] + + # Uncomment the following to configure how often external-provisioner polls the driver to detect changed capacity + # Configure only when the storageCapacity is set as "true" + # Allowed values: 1m,2m,3m,...,10m,...,60m etc. Default value: 5m + #- name: provisioner + # args: ["--capacity-poll-interval=5m"] + + controller: + envs: + # X_CSI_NFS_ACLS: enables setting permissions on NFS mount directory + # This value will be the default value if a storage class and array config in secret + # do not contain the NFS ACL (nfsAcls) parameter specified + # Permissions can be specified in two formats: + # 1) Unix mode (NFSv3) + # 2) NFSv4 ACLs (NFSv4) + # NFSv4 ACLs are supported on NFSv4 share only. + # Allowed values: + # 1) Unix mode: valid octal mode number + # Examples: "0777", "777", "0755" + # 2) NFSv4 acls: valid NFSv4 acls, seperated by comma + # Examples: "A::OWNER@:RWX,A::GROUP@:RWX", "A::OWNER@:rxtncy" + # Optional: true + # Default value: "0777" + # nfsAcls: "0777" + - name: X_CSI_NFS_ACLS + value: "0777" + # X_CSI_HEALTH_MONITOR_ENABLED: Enable/Disable health monitor of CSI volumes from Controller plugin - volume condition. + # Install the 'external-health-monitor' sidecar accordingly. + # Allowed values: + # true: enable checking of health condition of CSI volumes + # false: disable checking of health condition of CSI volumes + # Default value: false + - name: X_CSI_HEALTH_MONITOR_ENABLED + value: "$HEALTH_MONITOR_ENABLED" + # X_CSI_POWERSTORE_EXTERNAL_ACCESS: Allows to specify additional entries for hostAccess of NFS volumes. Both single IP address and subnet are valid entries. + # Allowed Values: x.x.x.x/xx or x.x.x.x + # Default Value: + - name: X_CSI_POWERSTORE_EXTERNAL_ACCESS + value: + + # nodeSelector: Define node selection constraints for controller pods. + # For the pod to be eligible to run on a node, the node must have each + # of the indicated key-value pairs as labels. + # Leave as blank to consider all nodes + # Allowed values: map of key-value pairs + # Default value: None + nodeSelector: $CONTROLLER_POD_NODE_SELECTOR + + # tolerations: Define tolerations for the controllers, if required. + # Leave as blank to install controller on worker nodes + # Default value: None + tolerations:$CONTROLLER_TOLERATIONS + + node: + envs: + # Set to "true" to enable ISCSI CHAP Authentication + # CHAP password will be autogenerated by driver + - name: "X_CSI_POWERSTORE_ENABLE_CHAP" + value: "false" + # X_CSI_HEALTH_MONITOR_ENABLED: Enable/Disable health monitor of CSI volumes from node plugin - volume usage + # Allowed values: + # true: enable checking of health condition of CSI volumes + # false: disable checking of health condition of CSI volumes + # Default value: false + - name: X_CSI_HEALTH_MONITOR_ENABLED + value: "$HEALTH_MONITOR_ENABLED" + # X_CSI_POWERSTORE_MAX_VOLUMES_PER_NODE: Defines the maximum PowerStore volumes that can be created per node + # Allowed values: Any value greater than or equal to 0 + # Default value: "0" + - name: X_CSI_POWERSTORE_MAX_VOLUMES_PER_NODE + value: "$MAX_VOLUMES_PER_NODE" + + # nodeSelector: Define node selection constraints for node pods. + # For the pod to be eligible to run on a node, the node must have each + # of the indicated key-value pairs as labels. + # Leave as blank to consider all nodes + # Allowed values: map of key-value pairs + # Default value: None + nodeSelector:$NODE_POD_NODE_SELECTOR + + # tolerations: Define tolerations for the controllers, if required. + # Leave as blank to install controller on worker nodes + # Default value: None + tolerations:$NODE_TOLERATIONS + + modules: + - name: resiliency + # enabled: Enable/Disable Resiliency feature + # Allowed values: + # true: enable Resiliency feature(deploy podmon sidecar) + # false: disable Resiliency feature(do not deploy podmon sidecar) + # Default value: false + enabled: $OPERATOR_RESILIENCY_ENABLED + configVersion: v1.10.0 + components: + - name: podmon-controller + image: dellemc/podmon:v1.10.0 + imagePullPolicy: IfNotPresent + args: + - "--labelvalue=$LABEL_VALUE" + - "--arrayConnectivityPollRate=$POLL_RATE" + - "--skipArrayConnectionValidation=$SKIP_ARRAY_CONNECTION_VALIDATION" + - "--driverPodLabelValue=$DRIVER_POD_LABEL_VALUE" + - "--ignoreVolumelessPods=$IGNORE_VOLUMELESS_PODS" + - "--arrayConnectivityConnectionLossThreshold=$ARRAY_THRESHOLD" + # Below 4 args should not be modified. + - "--csisock=unix:/var/run/csi/csi.sock" + - "--mode=controller" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPath=csi-powerstore.dellemc.com" + - name: podmon-node + image: dellemc/podmon:v1.10.0 + imagePullPolicy: IfNotPresent + envs: + # podmonAPIPort: Defines the port to be used within the kubernetes cluster + # Allowed values: Any valid and free port (string) + # Default value: 8083 + - name: "X_CSI_PODMON_API_PORT" + value: "8083" + args: + - "--labelvalue=$LABEL_VALUE" + - "--arrayConnectivityPollRate=$POLL_RATE" + - "--leaderelection=$LEADER_ELECTION" + - "--driverPodLabelValue=$DRIVER_POD_LABEL_VALUE" + - "--ignoreVolumelessPods=$IGNORE_VOLUMELESS_PODS" + # Below 4 args should not be modified. + - "--csisock=unix:/var/lib/kubelet/plugins/csi-powerstore.dellemc.com/csi_sock" + - "--mode=node" + - "--driver-config-params=/powerstore-config-params/driver-config-params.yaml" + - "--driverPath=csi-powerstore.dellemc.com" diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md index 70cfa0e2d0..dc662f6d1e 100644 --- a/content/docs/deployment/csmoperator/_index.md +++ b/content/docs/deployment/csmoperator/_index.md @@ -13,21 +13,21 @@ The table below lists the driver and modules versions installable with the CSM O | CSI Driver | Version | CSM Authorization | CSM Replication | CSM Observability | CSM Resiliency | | ------------------ |---------|-------------------|-----------------|-------------------|----------------| -| CSI PowerScale | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ✔ 1.9.0 | -| CSI PowerScale | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | -| CSI PowerScale | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ✔ 1.7.0 | -| CSI PowerFlex | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ✔ 1.9.0 | -| CSI PowerFlex | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | -| CSI PowerFlex | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ✔ 1.7.0 | -| CSI PowerStore | 2.10.0 | ❌ | ❌ | ❌ | ✔ 1.9.0 | -| CSI PowerStore | 2.9.0 | ❌ | ❌ | ❌ | ✔ 1.8.0 | -| CSI PowerStore | 2.8.0 | ❌ | ❌ | ❌ | ✔ 1.7.0 | -| CSI PowerMax | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ❌ | -| CSI PowerMax | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ❌ | -| CSI PowerMax | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ❌ | -| CSI Unity XT | 2.10.0 | ❌ | ❌ | ❌ | ❌ | -| CSI Unity XT | 2.9.0 | ❌ | ❌ | ❌ | ❌ | -| CSI Unity XT | 2.8.0 | ❌ | ❌ | ❌ | ❌ | +| CSI PowerScale | 2.11.0 | ✔ 1.11.0 | ✔ 1.9.0 | ✔ 1.9.0 | ✔ 1.10.0 | +| CSI PowerScale | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ✔ 1.9.0 | +| CSI PowerScale | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | +| CSI PowerFlex | 2.11.0 | ✔ 1.11.0 | ✔ 1.9.0 | ✔ 1.9.0 | ✔ 1.10.0 | +| CSI PowerFlex | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ✔ 1.9.0 | +| CSI PowerFlex | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | +| CSI PowerStore | 2.11.0 | ❌ | ❌ | ❌ | ✔ 1.10.0 | +| CSI PowerStore | 2.10.0 | ❌ | ❌ | ❌ | ✔ 1.9.0 | +| CSI PowerStore | 2.9.0 | ❌ | ❌ | ❌ | ✔ 1.8.0 | +| CSI PowerMax | 2.11.0 | ✔ 1.11.0 | ✔ 1.9.0 | ✔ 1.9.0 | ❌ | +| CSI PowerMax | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ❌ | +| CSI PowerMax | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ❌ | +| CSI Unity XT | 2.11.0 | ❌ | ❌ | ❌ | ❌ | +| CSI Unity XT | 2.10.0 | ❌ | ❌ | ❌ | ❌ | +| CSI Unity XT | 2.9.0 | ❌ | ❌ | ❌ | ❌ | >NOTE: >- Refer to sample files [here](https://github.com/dell/csm-operator/tree/main/samples). @@ -157,14 +157,14 @@ Here is the output of a request to build an offline bundle for the Dell CSM Oper dellemc/csi-powerstore:v2.10.0 dellemc/csi-unity:v2.10.0 dellemc/csi-vxflexos:v2.10.0 - dellemc/csm-authorization-sidecar:v1.10.0 - dellemc/csm-metrics-powerflex:v1.8.0 - dellemc/csm-metrics-powerscale:v1.5.0 + dellemc/csm-authorization-sidecar:v1.11.0 + dellemc/csm-metrics-powerflex:v1.9.0 + dellemc/csm-metrics-powerscale:v1.6.0 dellemc/csm-topology:v1.7.0 - dellemc/dell-csi-replicator:v1.8.0 - dellemc/dell-replication-controller:v1.8.0 + dellemc/dell-csi-replicator:v1.9.0 + dellemc/dell-replication-controller:v1.9.0 dellemc/sdc:4.5 - docker.io/dellemc/dell-csm-operator:v1.5.0 + docker.io/dellemc/dell-csm-operator:v1.6.0 gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0 nginxinc/nginx-unprivileged:1.20 otel/opentelemetry-collector:0.42.0 diff --git a/content/docs/deployment/csmoperator/modules/replication.md b/content/docs/deployment/csmoperator/modules/replication.md index c2775c3a68..6a5df95419 100644 --- a/content/docs/deployment/csmoperator/modules/replication.md +++ b/content/docs/deployment/csmoperator/modules/replication.md @@ -31,14 +31,14 @@ This change will need to be made to the /etc/hosts file on: The [csm-replication](https://github.com/dell/csm-replication.git) GitHub repository is cloned to your source cluster as part of the installation. On your source cluster run the following to clone and build the repctl tool: ```bash -git clone -b v1.8.0 https://github.com/dell/csm-replication.git +git clone -b v1.9.0 https://github.com/dell/csm-replication.git cd csm-replication/repctl make build ``` Alternately, you can download a pre-built repctl binary from our [Releases](https://github.com/dell/csm-replication/releases) page. ```shell -wget https://github.com/dell/csm-replication/releases/download/v1.8.0/repctl-linux-amd64 +wget https://github.com/dell/csm-replication/releases/download/v1.9.0/repctl-linux-amd64 mv repctl-linux-amd64 repctl chmod +x repctl ``` diff --git a/content/docs/deployment/csmoperator/modules/resiliency.md b/content/docs/deployment/csmoperator/modules/resiliency.md index a4fb29fd7b..421cdcef42 100644 --- a/content/docs/deployment/csmoperator/modules/resiliency.md +++ b/content/docs/deployment/csmoperator/modules/resiliency.md @@ -40,7 +40,7 @@ To enable this module, user should choose the sample file for the respective dri # false: disable Resiliency feature(do not deploy podmon sidecar) # Default value: false enabled: true - configVersion: v1.9.0 + configVersion: v1.10.0 components: - name: podmon-controller args: diff --git a/content/docs/deployment/helm/modules/installation/replication/install-repctl.md b/content/docs/deployment/helm/modules/installation/replication/install-repctl.md index 963785930b..7910f93334 100644 --- a/content/docs/deployment/helm/modules/installation/replication/install-repctl.md +++ b/content/docs/deployment/helm/modules/installation/replication/install-repctl.md @@ -13,14 +13,14 @@ Before you begin, make sure you have the repctl tool available. You can download a pre-built repctl binary from our [Releases](https://github.com/dell/csm-replication/releases) page. ```shell -wget https://github.com/dell/csm-replication/releases/download/v1.8.0/repctl-linux-amd64 +wget https://github.com/dell/csm-replication/releases/download/v1.9.0/repctl-linux-amd64 mv repctl-linux-amd64 repctl chmod +x repctl ``` Alternately, if you want to build the binary yourself, you can follow these steps: ```shell -git clone -b v1.8.0 https://github.com/dell/csm-replication.git +git clone -b v1.9.0 https://github.com/dell/csm-replication.git cd csm-replication/repctl make build ``` diff --git a/content/docs/deployment/helm/modules/installation/replication/install-script.md b/content/docs/deployment/helm/modules/installation/replication/install-script.md index 52506ba306..4a2429a101 100644 --- a/content/docs/deployment/helm/modules/installation/replication/install-script.md +++ b/content/docs/deployment/helm/modules/installation/replication/install-script.md @@ -9,11 +9,11 @@ description: Installation of CSM for Replication using script (Helm chart) > **_NOTE:_** These steps should be repeated on all Kubernetes clusters where you want to configure replication. ```shell -git clone -b v1.8.0 https://github.com/dell/csm-replication.git +git clone -b v1.9.0 https://github.com/dell/csm-replication.git cd csm-replication kubectl create ns dell-replication-controller # Download and modify the default values.yaml file if you wish to customize your deployment in any way -wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.8.0/charts/csm-replication/values.yaml +wget -O myvalues.yaml https://raw.githubusercontent.com/dell/helm-charts/csm-replication-1.9.0/charts/csm-replication/values.yaml bash scripts/install.sh --values ./myvalues.yaml ``` >Note: Current installation method allows you to specify custom `:` entries to be appended to controller's `/etc/hosts` file. It can be useful if controller is being deployed in private environment where DNS is not set up properly, but kubernetes clusters use FQDN as API server's address. diff --git a/content/docs/deployment/helm/modules/upgrade/observability.md b/content/docs/deployment/helm/modules/upgrade/observability.md index 5189a21520..6a8b960e1a 100644 --- a/content/docs/deployment/helm/modules/upgrade/observability.md +++ b/content/docs/deployment/helm/modules/upgrade/observability.md @@ -28,7 +28,7 @@ helm search repo dell ``` ``` NAME CHART VERSION APP VERSION DESCRIPTION -dell/karavi-observability 1.8.0 1.8.0 CSM for Observability is part of the [Container... +dell/karavi-observability 1.9.0 1.9.0 CSM for Observability is part of the [Container... ``` >Note: If using cert-manager CustomResourceDefinitions older than v1.5.3, delete the old CRDs and install v1.5.3 of the CRDs prior to upgrade. See [Prerequisites](../../installation/observability/deployment#prerequisites) for location of CRDs. diff --git a/content/docs/deployment/helm/modules/upgrade/replication.md b/content/docs/deployment/helm/modules/upgrade/replication.md index 75c7a8f365..38f78188b5 100644 --- a/content/docs/deployment/helm/modules/upgrade/replication.md +++ b/content/docs/deployment/helm/modules/upgrade/replication.md @@ -45,7 +45,7 @@ On PowerScale systems, an additional step is needed when upgrading to CSM Replic Make sure the appropriate release branch is available on the machine performing the upgrade by running: ```bash -git clone -b v1.8.0 https://github.com/dell/csm-replication.git +git clone -b v1.9.0 https://github.com/dell/csm-replication.git ``` ### Upgrading with Helm diff --git a/content/docs/deployment/offline/drivers/_index.md b/content/docs/deployment/offline/drivers/_index.md index cd772237d8..7b151f74df 100644 --- a/content/docs/deployment/offline/drivers/_index.md +++ b/content/docs/deployment/offline/drivers/_index.md @@ -90,12 +90,12 @@ bash scripts/csm-offline-bundle.sh -c dellemc/csi-powerstore:v2.10.0 dellemc/csi-unity:v2.10.0 dellemc/csi-vxflexos:v2.10.0 - dellemc/csm-authorization-sidecar:v1.10.0 + dellemc/csm-authorization-sidecar:v1.11.0 dellemc/csm-metrics-powerflex:v1.5.0 dellemc/csm-metrics-powerscale:v1.2.0 dellemc/csm-topology:v1.5.0 - dellemc/dell-csi-replicator:v1.8.0 - dellemc/dell-replication-controller:v1.8.0 + dellemc/dell-csi-replicator:v1.9.0 + dellemc/dell-replication-controller:v1.9.0 dellemc/sdc:4.5 docker.io/dellemc/dell-csm-operator:v1.4.3 gcr.io/kubebuilder/kube-rbac-proxy:v0.8.0 diff --git a/content/docs/observability/release/_index.md b/content/docs/observability/release/_index.md index 01060bb88a..76401caa75 100644 --- a/content/docs/observability/release/_index.md +++ b/content/docs/observability/release/_index.md @@ -6,7 +6,7 @@ Description: > Dell Container Storage Modules (CSM) release notes for observability --- -## Release Notes - CSM Observability 1.8.0 +## Release Notes - CSM Observability 1.9.0 diff --git a/content/docs/resiliency/release/_index.md b/content/docs/resiliency/release/_index.md index 0beacafe4b..91e9bffeb5 100644 --- a/content/docs/resiliency/release/_index.md +++ b/content/docs/resiliency/release/_index.md @@ -6,7 +6,7 @@ Description: > Dell Container Storage Modules (CSM) release notes for resiliency --- -## Release Notes - CSM Resiliency 1.9.0 +## Release Notes - CSM Resiliency 1.10.0 From a756e333b6042132e9c827b355d1b1e665638765 Mon Sep 17 00:00:00 2001 From: Wilson Radadia <159131702+WilsonRadadia20@users.noreply.github.com> Date: Thu, 9 May 2024 11:15:27 +0530 Subject: [PATCH 13/49] Renamed templates of csm isilon, powermax and powerstore (#1091) --- .../{csm-isilon-1.10.0.template => csm-isilon-1.10.1.template} | 0 ...{csm-powermax-1.10.0.template => csm-powermax-1.10.1.template} | 0 ...-powerstore-1.10.0.template => csm-powerstore-1.10.1.template} | 0 3 files changed, 0 insertions(+), 0 deletions(-) rename content/docs/deployment/csminstallationwizard/src/templates/operator/{csm-isilon-1.10.0.template => csm-isilon-1.10.1.template} (100%) rename content/docs/deployment/csminstallationwizard/src/templates/operator/{csm-powermax-1.10.0.template => csm-powermax-1.10.1.template} (100%) rename content/docs/deployment/csminstallationwizard/src/templates/operator/{csm-powerstore-1.10.0.template => csm-powerstore-1.10.1.template} (100%) diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.10.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.10.1.template similarity index 100% rename from content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.10.0.template rename to content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.10.1.template diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.1.template similarity index 100% rename from content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.0.template rename to content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.10.1.template diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.10.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.10.1.template similarity index 100% rename from content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.10.0.template rename to content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.10.1.template From d4d7b4d3ebaeffbd76fd8bd0ea7e9162faa44bd2 Mon Sep 17 00:00:00 2001 From: gallacher <35462391+gallacher@users.noreply.github.com> Date: Wed, 22 May 2024 17:15:54 -0300 Subject: [PATCH 14/49] Added broken links check action (#1102) * Create broken-links.yaml * Update actions.yaml --- .github/workflows/actions.yaml | 2 +- .github/workflows/broken-links.yaml | 46 +++++++++++++++++++++++++++++ 2 files changed, 47 insertions(+), 1 deletion(-) create mode 100644 .github/workflows/broken-links.yaml diff --git a/.github/workflows/actions.yaml b/.github/workflows/actions.yaml index 37d67add4b..9c4e459b74 100644 --- a/.github/workflows/actions.yaml +++ b/.github/workflows/actions.yaml @@ -3,7 +3,7 @@ on: push: branches: [ main ] pull_request: - branches: [ main ] + branches: [ main, release-* ] jobs: malware_security_scan: name: Malware Scanner diff --git a/.github/workflows/broken-links.yaml b/.github/workflows/broken-links.yaml new file mode 100644 index 0000000000..367573fda9 --- /dev/null +++ b/.github/workflows/broken-links.yaml @@ -0,0 +1,46 @@ +name: Check Broken Links + +on: + push: + branches: [ main ] + pull_request: + branches: [ main, release-* ] +jobs: + check-broken-links: + runs-on: ubuntu-latest + steps: + - name: Checkout + uses: actions/checkout@v4 + - name: Setup Hugo + uses: peaceiris/actions-hugo@v2 + with: + hugo-version: '0.120.3' + extended: true + - name: Setup Node + uses: actions/setup-node@v3 + with: + node-version: '16' + - name: Cache dependencies + uses: actions/cache@v3 + with: + path: ~/.npm + key: ${{ runner.os }}-node-${{ hashFiles('**/package-lock.json') }} + restore-keys: | + ${{ runner.os }}-node- + - run: npm ci + - name: Build + run: | + npm install -D --save autoprefixer + npm install -D --save postcss-cli + npm install -D --save postcss + hugo server --bind 127.0.0.1 & + - name: Wait for Hugo server + run: curl --head -X GET --retry 5 --retry-connrefused --retry-delay 10 http://127.0.0.1:1313/csm-docs/ + - name: Scanning docs for broken links + continue-on-error: true + run: | + wget --verbose --spider -o spider.log -e robots=off -rp http://127.0.0.1:1313/csm-docs/ + - name: Getting output + run: | + sed -n '/broken links/,$p' spider.log + grep -Fxq "Found 0 broken links." spider.log From e0ac7a0001ec9c96bd0ce0ecf63980be521ea006 Mon Sep 17 00:00:00 2001 From: gallacher <35462391+gallacher@users.noreply.github.com> Date: Mon, 27 May 2024 13:57:09 -0300 Subject: [PATCH 15/49] Update broken-links.yaml (#1110) --- .github/workflows/broken-links.yaml | 13 ++++++++++--- 1 file changed, 10 insertions(+), 3 deletions(-) diff --git a/.github/workflows/broken-links.yaml b/.github/workflows/broken-links.yaml index 367573fda9..2aa5528dce 100644 --- a/.github/workflows/broken-links.yaml +++ b/.github/workflows/broken-links.yaml @@ -41,6 +41,13 @@ jobs: run: | wget --verbose --spider -o spider.log -e robots=off -rp http://127.0.0.1:1313/csm-docs/ - name: Getting output - run: | - sed -n '/broken links/,$p' spider.log - grep -Fxq "Found 0 broken links." spider.log + continue-on-error: true + run: | + sed -i '/http:\/\/127.0.0.1:1313\/favicons\/favicon.ico/d' spider.log + sed -i '/http:\/\/127.0.0.1:1313\/css\/prism.css/d' spider.log + sed -n '/broken links/,$p' spider.log | grep 'http' > broken_links + - name: Check for broken links + run: | + wc -l broken_links + cat broken_links + wc -l broken_links | grep -Fxq "0 broken_links" From 509ac1cf8c6687c40fc685106015e653c42baf19 Mon Sep 17 00:00:00 2001 From: HarishH-DELL <109663924+HarishH-DELL@users.noreply.github.com> Date: Tue, 28 May 2024 17:42:36 +0530 Subject: [PATCH 16/49] Encryption Release notes (#1116) * Encryption Release notes * Correction for version --- content/docs/secure/encryption/_index.md | 5 +++++ content/docs/secure/encryption/release/_index.md | 10 +--------- content/v1/secure/encryption/_index.md | 3 +++ content/v1/secure/encryption/release/_index.md | 10 +--------- 4 files changed, 10 insertions(+), 18 deletions(-) diff --git a/content/docs/secure/encryption/_index.md b/content/docs/secure/encryption/_index.md index e3b007bfa2..63d9a98e86 100644 --- a/content/docs/secure/encryption/_index.md +++ b/content/docs/secure/encryption/_index.md @@ -5,8 +5,13 @@ weight: 1 Description: > CSI Volumes Encryption --- + +**NOTE:** Encryption is not supported for CSM 1.10.x release. Please refer to the [release notes](./release/) for more details. + Encryption provides the capability to encrypt user data residing on volumes created by Dell CSI Drivers. + + > **NOTE:** This tech-preview release is not intended for use in production environment. > **NOTE:** Encryption requires a time-based license to create new encrypted volumes. Request a [trial license](../../license) prior to deployment. diff --git a/content/docs/secure/encryption/release/_index.md b/content/docs/secure/encryption/release/_index.md index b2376e4be6..46a0169cbd 100644 --- a/content/docs/secure/encryption/release/_index.md +++ b/content/docs/secure/encryption/release/_index.md @@ -6,14 +6,6 @@ Description: > Release Notes --- -### New Features/Changes - -- Supports the latest version of CSM. - -### Fixed Issues - -There are no fixed issues in this release. - ### Known Issues -There are no known issues in this release. +The encryption module installation fails because sidecars like csi-metadata-retriever-* conflict when trying to access the same domain socket. (/var/run/csi/csi_retriever.sock). Please find the [github issue](https://github.com/dell/csm/issues/1309). \ No newline at end of file diff --git a/content/v1/secure/encryption/_index.md b/content/v1/secure/encryption/_index.md index 440c171c56..08b70aec88 100644 --- a/content/v1/secure/encryption/_index.md +++ b/content/v1/secure/encryption/_index.md @@ -5,6 +5,9 @@ weight: 1 Description: > CSI Volumes Encryption --- + +**NOTE:** Encryption is not supported for CSM 1.9.x release. Please refer to the [release notes](./release/) for more details. + Encryption provides the capability to encrypt user data residing on volumes created by Dell CSI Drivers. > **NOTE:** This tech-preview release is not intended for use in production environment. diff --git a/content/v1/secure/encryption/release/_index.md b/content/v1/secure/encryption/release/_index.md index b2376e4be6..46a0169cbd 100644 --- a/content/v1/secure/encryption/release/_index.md +++ b/content/v1/secure/encryption/release/_index.md @@ -6,14 +6,6 @@ Description: > Release Notes --- -### New Features/Changes - -- Supports the latest version of CSM. - -### Fixed Issues - -There are no fixed issues in this release. - ### Known Issues -There are no known issues in this release. +The encryption module installation fails because sidecars like csi-metadata-retriever-* conflict when trying to access the same domain socket. (/var/run/csi/csi_retriever.sock). Please find the [github issue](https://github.com/dell/csm/issues/1309). \ No newline at end of file From dfd73c6d2dd983e291fbd6b2d4c43935a3c3a1d0 Mon Sep 17 00:00:00 2001 From: Wilson Radadia <159131702+WilsonRadadia20@users.noreply.github.com> Date: Tue, 28 May 2024 18:59:55 +0530 Subject: [PATCH 17/49] Bug 1289 dead links (#1115) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Snapshot ingestion procedure for CSI Unity Driver (#1042) * Snapshot ingestion procedure for CSI Unity Driver * Addressed review comments * Review commnets addressed * Review commnets addressed * Add dell/csm#1205 to known issues (#1045) * Add #1205 to known issues * Fix yaml snippet displaying issue * Updating powermax support matrix (#1046) * Adding PowerFlex known issue for https://github.com/dell/csm/issues/1210 (#1049) * Update PowerFlex known issues * Release 1.10.1 (#1055) * Add notes about non-default namespace for Authorization and Operator (#1047) Co-authored-by: Aaron Tye * Adding known issue for authorization for previous releases (#1052) * Update Docs for PowerFlex issue 1210 (#1053) * installation wizard changes (#1056) --------- Co-authored-by: Akshay Saini <109056238+AkshaySainiDell@users.noreply.github.com> Co-authored-by: Aaron Tye Co-authored-by: Surya Gupta <109594002+suryagupta4@users.noreply.github.com> * Add RPM deployment for Authorization (#1060) * readd rpm deployment * fix page descriptions * fix broken links * Added fsGroupPolicy troubleshooting notes and missing known issues (#1063) * Added fsGroupPolicy troubleshooting note * Fixed issue with troubleshooting note * Added fsGroupPolicy troubleshooting note * Added fsGroupPolicy troubleshooting note * Added fsGroupPolicy known issue * Update known issue powermax (#1066) * New CSM Operator interactive tutorial (#1067) * Reorder deployment methods by priority (#1068) * Operator unavailablity message for fresh install and upgrade in OCP UI (#1070) * Move support matrix, clarify certified vs community (#1069) * Move support matrix, clarify certified vs community * clarify certified vs community * Revert "Operator unavailablity message for fresh install and upgrade in OCP U…" (#1071) * Updating support for Powerstore 3.6 (#1072) * add podmon arguments (#1078) * Add VGS to the support matrix ; align tables (#1077) * Updating podmon entries in helm template (#1081) * PowerScale: Add podmon arguments in Installation Wizard templates (#1085) * update podmon arguments * Add codeowners * update Unity NAT section (#1092) * Renamed templates of csm isilon, powermax and powerstore (#1089) * Restructure the left menu & reference ; remove FAQ (#1075) * 404 Not Found for Cert-CSI * Solved: 404 Not Found License Page * Solved: 404 Not Found License Page * Solved: 404 Not Found Cert-CSI * Solved: 404 Not Found License Page * Solved: Not Found in request a license for Application Mobility * Changes Reverted Solved: 404 Not Found, troubleshooting Solved: 404 Not Found, troubleshooting Solved: 404 Not Found, troubleshooting Solved: 404 Not Found, troubleshooting Solved: 404 Not Found, troubleshooting Solved: 404 Not Found, troubleshooting Solved: 404 Not Found, proxy sever Solved: 404 Not Found, proxy sever Solved: 404 Not Found, troubleshooting Solved: 404 Not Found, troubleshooting * Solved: Not Found, supported Solved: Not Found, supported Solved: Not Found, supported * Solved: 404 Not Found, troubleshooting * Solved: 404 Not Found, proxy sever * Solved: 404 Not Found, Powerflex * Solved: 404 Not Found, PowerMax * Solved: 404 Not Found, PowerScale Solved: 404 Not Found, PowerScale * Update Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod (#1096) * Solved: Not Found, CSI drivers, Authorization, Observability, Replication, Resiliency, Encryption, Application Mobility, Operator troubleshoot Solved: Not Found, CSI drivers, Authorization, Observability, Replication, Resiliency, Encryption, Application Mobility, Operator troubleshoot Solved: Not Found, CSI drivers, Authorization, Observability, Replication, Resiliency, Encryption, Application Mobility, Operator troubleshoot * Solved: 404 Not Found, SmartQuotas powerscale Solved: 404 Not Found, SmartQuotas powerscale * Solved: 404 Not Found, CSI Driver release notes * Solved: 404 Not Found, CSM for Authorization, Observability, Replication, Resiliency, Encryption, Aplication Mobility, Operator, Installation Wizard Solved: 404 Not Found, CSM for Authorization, Observability, Replication, Resiliency, Encryption, Aplication Mobility, Operator, Installation Wizard * Solved: 404 Not Found, cli for dellctl * Check for broken links (#1100) * Create broken-links.yaml * Solved: 404 Not Found, license page in encryption * Solved: 404 Not Found, license page in troubleshooting Solved: 404 Not Found, license page in troubleshooting * Solved: 404 Not Found, prerequisite in authorization * Updated Resiliency "Not Yet Tested or Supported" for Powerflex * Solved: 404 Not Found, Install driver in authorization for PowerFlex * Resiliency not supported for NFS in PowerFlex (#1106) * Solved: 404 Not Found, Install driver in authorization for PowerFlex Solved: 404 Not Found, Install driver in authorization for PowerFlex Solved: 404 Not Found, Install driver in authorization for PowerFlex Solved: 404 Not Found, Install driver in authorization for PowerFlex * Solved: 404 Not Found, PowerFlex, PowerScale, PowerMax, Proxy-server, Troubleshooting and support Solved: 404 Not Found, PowerFlex, PowerScale, PowerMax, Proxy-server, Troubleshooting and support * Solved: 404 Not Found dellctl and installation of PowerFlex using Helm in Authorization * Solved: 404 Not Found License Page in Encryption * Solved: 404 Not Found Troubleshooting in Support for Observability, Resiliency, Encryption and Application Mobility * Solved: 404 Not Found CLI in Application Mobility * Solved: 404 Not Found, SmartQuotas in PowerScale * Solved: 404 Not Found reference CLI for PowerScale and PowerMax * Solved: 404 Not Found, Authorization in Upgrade Module * Update broken-links.yaml (#1108) * Removed the conflicts for merging in release-1.11.0 * Updated changes in release file of Operator and Authorization * Updated CODEOWNERS --------- Co-authored-by: HarishH-DELL <109663924+HarishH-DELL@users.noreply.github.com> Co-authored-by: Akshay Saini <109056238+AkshaySainiDell@users.noreply.github.com> Co-authored-by: boyamurthy <92081029+boyamurthy@users.noreply.github.com> Co-authored-by: gallacher <35462391+gallacher@users.noreply.github.com> Co-authored-by: Adarsh Kumar Yadav <109620911+adarsh-dell@users.noreply.github.com> Co-authored-by: Aaron Tye Co-authored-by: Surya Gupta <109594002+suryagupta4@users.noreply.github.com> Co-authored-by: shaynafinocchiaro Co-authored-by: coulof <49235405+coulof@users.noreply.github.com> Co-authored-by: panigs7 <92028646+panigs7@users.noreply.github.com> Co-authored-by: Chiman Jain <36687396+chimanjain@users.noreply.github.com> Co-authored-by: Matt Schmaelzle <51763677+mjsdell@users.noreply.github.com> Co-authored-by: Yamunadevi N Shanmugam <82038610+shanmydell@users.noreply.github.com> --- .github/CODEOWNERS | 4 +- content/docs/_index.md | 4 +- content/docs/applicationmobility/use_cases.md | 2 +- .../configuration/powerflex/_index.md | 2 +- .../configuration/powermax/_index.md | 2 +- .../configuration/powerscale/_index.md | 2 +- content/docs/authorization/release/_index.md | 7 +- content/docs/csidriver/features/powermax.md | 7 +- content/docs/csidriver/features/powerscale.md | 8 +- content/docs/csidriver/features/powerstore.md | 17 +- content/docs/csidriver/features/unity.md | 44 ++-- content/docs/csidriver/release/powerflex.md | 6 +- content/docs/csidriver/release/powermax.md | 3 +- content/docs/csidriver/release/powerscale.md | 2 +- content/docs/csidriver/release/powerstore.md | 2 +- content/docs/csidriver/release/unity.md | 3 +- .../csidriver/troubleshooting/powerscale.md | 1 + .../csidriver/troubleshooting/powerstore.md | 1 + .../docs/csidriver/troubleshooting/unity.md | 1 + .../templates/helm/csm-1.9.3-values.template | 62 ++++++ content/docs/deployment/csmoperator/_index.md | 15 +- .../helm/drivers/upgrade/powerflex.md | 2 +- .../docs/deployment/helm/modules/_index.md | 6 +- .../helm/modules/installation/_index.md | 2 +- .../applicationmobility/_index.md | 2 +- .../installation/authorization/_index.md | 14 +- .../modules/installation/encryption/_index.md | 2 +- .../helm/modules/uninstall/_index.md | 2 +- .../helm/modules/uninstall/authorization.md | 14 +- .../helm/modules/upgrade/authorization.md | 65 ++---- content/docs/deployment/rpm/_index.md | 8 + content/docs/deployment/rpm/modules/_index.md | 6 + .../rpm/modules/installation/_index.md | 6 + .../authorization/authorization.md | 194 ++++++++++++++++++ .../rpm/modules/uninstall/_index.md | 7 + .../rpm/modules/uninstall/authorization.md | 31 +++ .../deployment/rpm/modules/upgrade/_index.md | 7 + .../rpm/modules/upgrade/authorization.md | 66 ++++++ content/docs/interactive-tutorials/_index.md | 25 +-- .../csm-operator/_index.md | 29 +++ .../csm-quickstart/_index.md | 29 +++ content/docs/prerequisites/_index.md | 61 ++++-- content/docs/references/FAQ/_index.md | 112 ---------- content/docs/references/_index.md | 7 - content/docs/references/policies/_index.md | 7 - content/docs/release/_index.md | 27 --- content/docs/resiliency/_index.md | 2 + content/docs/secure/encryption/_index.md | 2 +- .../docs/secure/encryption/troubleshooting.md | 2 +- content/docs/securitypolicy/_index.md | 15 -- content/docs/support/_index.md | 16 +- content/docs/{ => support}/cert-csi/_index.md | 6 +- .../{ => support}/cert-csi/img/HTMLReport.png | Bin .../cert-csi/img/interruptTest.png | Bin .../{ => support}/cert-csi/img/listRuns.png | Bin .../{ => support}/cert-csi/img/longevity.png | Bin .../cert-csi/img/multiDBTabularReport.png | Bin .../cert-csi/img/resourceUsage.png | Bin .../{ => support}/cert-csi/img/scaling.PNG | Bin .../cert-csi/img/tabularReport.png | Bin .../{ => support}/cert-csi/img/textReport.png | Bin .../cert-csi/img/unifiedTest.png | Bin .../docs/{ => support}/cert-csi/qualified.md | 0 .../{references => support}/cli/_index.md | 2 +- .../contributionguidelines/_index.md | 2 +- .../deprecationpolicy/_index.md | 2 +- .../{references => support}/learn/_index.md | 4 +- content/docs/{ => support}/license/_index.md | 4 +- content/docs/support/release/_index.md | 27 +++ .../docs/support/troubleshooting/_index.md | 25 +++ content/docs/troubleshooting/_index.md | 25 --- content/v1/authorization/release/_index.md | 5 +- content/v1/csidriver/release/powermax.md | 1 + .../deployment/csmoperator/release/_index.md | 1 + content/v1/resiliency/_index.md | 2 + content/v2/authorization/release/_index.md | 5 +- content/v2/csidriver/release/powermax.md | 1 + .../deployment/csmoperator/release/_index.md | 4 +- content/v2/resiliency/_index.md | 2 + content/v3/authorization/release/_index.md | 4 + content/v3/csidriver/release/powermax.md | 1 + .../deployment/csmoperator/release/_index.md | 4 +- 82 files changed, 715 insertions(+), 375 deletions(-) create mode 100644 content/docs/deployment/rpm/_index.md create mode 100644 content/docs/deployment/rpm/modules/_index.md create mode 100644 content/docs/deployment/rpm/modules/installation/_index.md create mode 100644 content/docs/deployment/rpm/modules/installation/authorization/authorization.md create mode 100644 content/docs/deployment/rpm/modules/uninstall/_index.md create mode 100644 content/docs/deployment/rpm/modules/uninstall/authorization.md create mode 100644 content/docs/deployment/rpm/modules/upgrade/_index.md create mode 100644 content/docs/deployment/rpm/modules/upgrade/authorization.md create mode 100644 content/docs/interactive-tutorials/csm-operator/_index.md create mode 100644 content/docs/interactive-tutorials/csm-quickstart/_index.md delete mode 100644 content/docs/references/FAQ/_index.md delete mode 100644 content/docs/references/_index.md delete mode 100644 content/docs/references/policies/_index.md delete mode 100644 content/docs/release/_index.md delete mode 100644 content/docs/securitypolicy/_index.md rename content/docs/{ => support}/cert-csi/_index.md (98%) rename content/docs/{ => support}/cert-csi/img/HTMLReport.png (100%) rename content/docs/{ => support}/cert-csi/img/interruptTest.png (100%) rename content/docs/{ => support}/cert-csi/img/listRuns.png (100%) rename content/docs/{ => support}/cert-csi/img/longevity.png (100%) rename content/docs/{ => support}/cert-csi/img/multiDBTabularReport.png (100%) rename content/docs/{ => support}/cert-csi/img/resourceUsage.png (100%) rename content/docs/{ => support}/cert-csi/img/scaling.PNG (100%) rename content/docs/{ => support}/cert-csi/img/tabularReport.png (100%) rename content/docs/{ => support}/cert-csi/img/textReport.png (100%) rename content/docs/{ => support}/cert-csi/img/unifiedTest.png (100%) rename content/docs/{ => support}/cert-csi/qualified.md (100%) rename content/docs/{references => support}/cli/_index.md (99%) rename content/docs/{references => support}/contributionguidelines/_index.md (99%) rename content/docs/{references/policies => support}/deprecationpolicy/_index.md (99%) rename content/docs/{references => support}/learn/_index.md (95%) rename content/docs/{ => support}/license/_index.md (94%) create mode 100644 content/docs/support/release/_index.md create mode 100644 content/docs/support/troubleshooting/_index.md delete mode 100644 content/docs/troubleshooting/_index.md diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS index 28a0b0c136..727eebcf08 100644 --- a/.github/CODEOWNERS +++ b/.github/CODEOWNERS @@ -10,7 +10,6 @@ # Bharath Sreekanth (bharathsreekanth) # Deepak Ghivari (Deepak-Ghivari) # Sean Gallacher (gallacher) -# Marek Suski (mareksuski-dell) # Małgorzata Dutka (mdutka-dell) # Matt Schmaelzle (mjsdell) # Mukesh Gandharva (mgandharva) @@ -21,5 +20,6 @@ # Yamunadevi Shanmugam (shanmydell) # Sharon Toll (sharont58) # Shayna Finocchiaro (shaynafinocchiaro) +# Shefali Malhotra (shefali-malhotra) -* @atye @bharathsreekanth @Deepak-Ghivari @gallacher @mareksuski-dell @mdutka-dell @mgandharva @mjsdell @prablr79 @rajendraindukuri @rajkumar-palani @rsedlock1958 @shanmydell @sharont58 @shaynafinocchiaro +* @atye @bharathsreekanth @Deepak-Ghivari @gallacher @mdutka-dell @mgandharva @mjsdell @prablr79 @rajendraindukuri @rajkumar-palani @rsedlock1958 @shanmydell @sharont58 @shaynafinocchiaro @shefali-malhotra diff --git a/content/docs/_index.md b/content/docs/_index.md index 3510637cbb..127367ddfd 100644 --- a/content/docs/_index.md +++ b/content/docs/_index.md @@ -58,10 +58,10 @@ CSM is made up of multiple components including modules (enterprise capabilities {{< /card >}} {{< /cardpane >}} {{< cardpane >}} - {{< card header="[License](license/)" + {{< card header="[License](support/license/)" footer="Required for [Application Mobility](applicationmobility/) & [Encryption](secure/encryption/)">}} The tech-preview releases of Application Mobility and Encryption require a license. Request a license using the [Container Storage Modules License Request](https://app.smartsheet.com/b/form/5e46fad643874d56b1f9cf4c9f3071fb) by providing the requested details. - [...Learn more](license/) + [...Learn more](support/license/) {{< /card >}} {{< /cardpane >}} \ No newline at end of file diff --git a/content/docs/applicationmobility/use_cases.md b/content/docs/applicationmobility/use_cases.md index 91671b9e73..7ffdae38ca 100644 --- a/content/docs/applicationmobility/use_cases.md +++ b/content/docs/applicationmobility/use_cases.md @@ -6,7 +6,7 @@ Description: > Use Cases --- -After Application Mobility is installed, the [dellctl CLI](../../references/cli/) can be used to register clusters and manage backups and restores of applications. These examples also provide references for using the Application Mobility Custom Resource Definitions (CRDs) to define Custom Resources (CRs) as an alternative to using the `dellctl` CLI. +After Application Mobility is installed, the [dellctl CLI](../../support/cli) can be used to register clusters and manage backups and restores of applications. These examples also provide references for using the Application Mobility Custom Resource Definitions (CRDs) to define Custom Resources (CRs) as an alternative to using the `dellctl` CLI. ## Backup and Restore an Application This example details the steps when an application in namespace `demo1` is being backed up and then later restored to either the same cluster or another cluster. In this sample, both Application Mobility and Velero are installed in the `application-mobility` namespace. diff --git a/content/docs/authorization/configuration/powerflex/_index.md b/content/docs/authorization/configuration/powerflex/_index.md index 408944939e..8a94fbe346 100644 --- a/content/docs/authorization/configuration/powerflex/_index.md +++ b/content/docs/authorization/configuration/powerflex/_index.md @@ -172,4 +172,4 @@ Given a setup where Kubernetes, a storage system, and the CSM for Authorization 6. Install the Dell CSI PowerFlex driver following the appropriate documenation for your installation method. -7. (Optional) Install [dellctl](../../../references/cli) to perform Kubernetes administrator commands for additional capabilities (e.g., list volumes). Please refer to the [dellctl documentation page](../../../references/cli) for the installation steps and command list. \ No newline at end of file +7. (Optional) Install [dellctl](../../../support/cli/#installation-instructions) to perform Kubernetes administrator commands for additional capabilities (e.g., list volumes). Please refer to the [dellctl documentation page](../../../support/cli) for the installation steps and command list. \ No newline at end of file diff --git a/content/docs/authorization/configuration/powermax/_index.md b/content/docs/authorization/configuration/powermax/_index.md index 44d4cd8e1f..ee70004f3c 100644 --- a/content/docs/authorization/configuration/powermax/_index.md +++ b/content/docs/authorization/configuration/powermax/_index.md @@ -146,4 +146,4 @@ Create the karavi-authorization-config secret using this command: 5. Install the Dell CSI PowerMax driver following the appropriate documenation for your installation method. -6. (Optional) Install [dellctl](../../../references/cli) to perform Kubernetes administrator commands for additional capabilities (e.g., list volumes). Please refer to the [dellctl documentation page](../../../references/cli) for the installation steps and command list. \ No newline at end of file +6. (Optional) Install [dellctl](../../../support/cli/#installation-instructions) to perform Kubernetes administrator commands for additional capabilities (e.g., list volumes). Please refer to the [dellctl documentation page](../../../support/cli) for the installation steps and command list. \ No newline at end of file diff --git a/content/docs/authorization/configuration/powerscale/_index.md b/content/docs/authorization/configuration/powerscale/_index.md index b655108a63..b6bcb41c60 100644 --- a/content/docs/authorization/configuration/powerscale/_index.md +++ b/content/docs/authorization/configuration/powerscale/_index.md @@ -178,4 +178,4 @@ kubectl -n isilon create secret generic karavi-authorization-config --from-file= 6. Install the Dell CSI PowerScale driver following the appropriate documenation for your installation method. -7. (Optional) Install [dellctl](../../../references/cli) to perform Kubernetes administrator commands for additional capabilities (e.g., list volumes). Please refer to the [dellctl documentation page](../../../references/cli) for the installation steps and command list. \ No newline at end of file +7. (Optional) Install [dellctl](../../../support/cli/#installation-instructions) to perform Kubernetes administrator commands for additional capabilities (e.g., list volumes). Please refer to the [dellctl documentation page](../../../support/cli) for the installation steps and command list. \ No newline at end of file diff --git a/content/docs/authorization/release/_index.md b/content/docs/authorization/release/_index.md index 5d32effb18..67e40ff17f 100644 --- a/content/docs/authorization/release/_index.md +++ b/content/docs/authorization/release/_index.md @@ -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,5 @@ Description: > ### Known Issues - -There are no known issues in this release. +| Issue | Workaround | +|-------|------------| diff --git a/content/docs/csidriver/features/powermax.md b/content/docs/csidriver/features/powermax.md index 577d6222dc..be4d00bab7 100644 --- a/content/docs/csidriver/features/powermax.md +++ b/content/docs/csidriver/features/powermax.md @@ -547,13 +547,10 @@ kubectl edit configmap -n powermax powermax-config-params CSI Driver for Dell PowerMax 2.2.0 and above supports volume health monitoring. To enable Volume Health Monitoring from the node side, the alpha feature gate CSIVolumeHealth needs to be enabled. To use this feature, set controller.healthMonitor.enabled and node.healthMonitor.enabled to true. To change the monitor interval, set controller.healthMonitor.interval parameter. -## Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod (ALPHA FEATURE) +## Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod Use `ReadWriteOncePod(RWOP)` access mode if you want to ensure that only one pod across the whole cluster can read that PVC or write to it. This is only supported for CSI Driver for PowerMax 2.2.0+ and Kubernetes version 1.22+. -To use this feature, enable the ReadWriteOncePod feature gate for kube-apiserver, kube-scheduler, and kubelet, by setting command line arguments: -`--feature-gates="...,ReadWriteOncePod=true"` - ### Creating a PersistentVolumeClaim ```yaml kind: PersistentVolumeClaim @@ -570,7 +567,7 @@ spec: When this feature is enabled, the existing `ReadWriteOnce(RWO)` access mode restricts volume access to a single node and allows multiple pods on the same node to read from and write to the same volume. -To migrate existing PersistentVolumes to use `ReadWriteOncePod`, please follow the instruction from [here](https://kubernetes.io/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#migrating-existing-persistentvolumes). +To migrate existing PersistentVolumes to use `ReadWriteOncePod`, please follow the instruction from [here](https://kubernetes.io/docs/tasks/administer-cluster/change-pv-access-mode-readwriteoncepod/). ## Support for auto RDM for vSphere over FC diff --git a/content/docs/csidriver/features/powerscale.md b/content/docs/csidriver/features/powerscale.md index f66cb4740d..a48842b538 100644 --- a/content/docs/csidriver/features/powerscale.md +++ b/content/docs/csidriver/features/powerscale.md @@ -660,15 +660,11 @@ For example, if a volume were to be deleted from the array, or unmounted outside 1. For controller plugin, by setting attribute `controller.healthMonitor.enabled` to `true` in `values.yaml` file. Also health monitoring interval can be changed through attribute `controller.healthMonitor.interval` in `values.yaml` file. 2. For node plugin, by setting attribute `node.healthMonitor.enabled` to `true` in `values.yaml` file and by enabling the alpha feature gate `CSIVolumeHealth`. -## Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod (ALPHA FEATURE) +## Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod Use `ReadWriteOncePod(RWOP)` access mode if you want to ensure that only one pod across the whole cluster can read that PVC or write to it. This is supported for CSI Driver for PowerScale 2.1.0+ and Kubernetes version 1.22+. -To use this feature, enable the ReadWriteOncePod feature gate for kube-apiserver, kube-scheduler, and kubelet, by setting command line arguments: -`--feature-gates="...,ReadWriteOncePod=true"` - ### Creating a PersistentVolumeClaim - ```yaml kind: PersistentVolumeClaim apiVersion: v1 @@ -684,4 +680,4 @@ spec: When this feature is enabled, the existing `ReadWriteOnce(RWO)` access mode restricts volume access to a single node and allows multiple pods on the same node to read from and write to the same volume. -To migrate existing PersistentVolumes to use `ReadWriteOncePod`, please follow the instruction from [here](https://kubernetes.io/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#migrating-existing-persistentvolumes). +To migrate existing PersistentVolumes to use `ReadWriteOncePod`, please follow the instruction from [here](https://kubernetes.io/docs/tasks/administer-cluster/change-pv-access-mode-readwriteoncepod/). diff --git a/content/docs/csidriver/features/powerstore.md b/content/docs/csidriver/features/powerstore.md index a5d2460a12..df62811796 100644 --- a/content/docs/csidriver/features/powerstore.md +++ b/content/docs/csidriver/features/powerstore.md @@ -633,18 +633,11 @@ The user will be able to install the driver and able to create pods. CSI Driver for Dell Powerstore 2.1.0 and above supports volume health monitoring. To enable Volume Health Monitoring from the node side, the alpha feature gate CSIVolumeHealth needs to be enabled. To use this feature, set controller.healthMonitor.enabled and node.healthMonitor.enabled to true. To change the monitor interval, set controller.healthMonitor.interval parameter. -## Single Pod Access Mode for PersistentVolumes +## Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod -Starting from version 2.1, CSI Driver for Powerstore now supports a new access mode `ReadWriteOncePod` for PersistentVolumes and PersistentVolumeClaims. With this feature, CSI Driver for Powerstore allows restricting volume access to a single pod in the cluster and within a worker node. +Use `ReadWriteOncePod(RWOP)` access mode if you want to ensure that only one pod across the whole cluster can read that PVC or write to it. This is supported for CSI Driver for PowerStore 2.1.0+ and Kubernetes version 1.22+. -Prerequisites - -1. Enable the ReadWriteOncePod feature gate for kube-apiserver, kube-scheduler, and kubelet as ReadWriteOncePod access mode is in alpha for Kubernetes v1.22 and is supported only for CSI volumes. You can enable the feature by setting command-line argument: -```bash ---feature-gates="...,ReadWriteOncePod=true" -``` - -2. Create a PVC with access mode set to ReadWriteOncePod like shown in the sample below +### Creating a PersistentVolumeClaim ```yaml kind: PersistentVolumeClaim apiVersion: v1 @@ -660,6 +653,10 @@ spec: >Note: The access mode ReadWriteOnce allows multiple pods to access a single volume within a single worker node and the behavior is consistent across all supported Kubernetes versions. +When this feature is enabled, the existing `ReadWriteOnce(RWO)` access mode restricts volume access to a single node and allows multiple pods on the same node to read from and write to the same volume. + +To migrate existing PersistentVolumes to use `ReadWriteOncePod`, please follow the instruction from [here](https://kubernetes.io/docs/tasks/administer-cluster/change-pv-access-mode-readwriteoncepod/). + ## POSIX mode bits and NFSv4 ACLs CSI PowerStore driver version 2.2.0 and later allows users to set user-defined permissions on NFS target mount directory using POSIX mode bits or NFSv4 ACLs. diff --git a/content/docs/csidriver/features/unity.md b/content/docs/csidriver/features/unity.md index 8205ebf1ce..717842a75d 100644 --- a/content/docs/csidriver/features/unity.md +++ b/content/docs/csidriver/features/unity.md @@ -514,27 +514,29 @@ CSI Driver for Dell Unity XT is supported in the NAT environment for NFS protoco The user will be able to install the driver and able to create pods. -## Single Pod Access Mode for PersistentVolumes -CSI Driver for Unity XT supports a new accessmode `ReadWriteOncePod` for PersistentVolumes and PersistentVolumeClaims. With this feature, CSI Driver for Unity XT restricts volume access to a single pod in the cluster - -Prerequisites -1. Enable the ReadWriteOncePod feature gate for kube-apiserver, kube-scheduler, and kubelet as the ReadWriteOncePod access mode is in alpha for Kubernetes v1.22 and is only supported for CSI volumes. You can enable the feature by setting command line arguments: - ```bash - --feature-gates="...,ReadWriteOncePod=true" - ``` -2. Create a PVC with access mode set to ReadWriteOncePod like shown in the sample below - ```yaml - kind: PersistentVolumeClaim - apiVersion: v1 - metadata: - name: single-writer-only - spec: - accessModes: - - ReadWriteOncePod # Allow only a single pod to access single-writer-only. - resources: - requests: - storage: 1Gi - ``` +**NOTE:** On Unity, management port does not support NAT. NAT needs to be disabled on the Unity array's management network. + +## Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod + +Use `ReadWriteOncePod(RWOP)` access mode if you want to ensure that only one pod across the whole cluster can read that PVC or write to it. This is only supported for CSI Driver for Unity 2.1.0+ and Kubernetes version 1.22+. + +### Creating a PersistentVolumeClaim +```yaml +kind: PersistentVolumeClaim +apiVersion: v1 +metadata: +name: single-writer-only +spec: +accessModes: +- ReadWriteOncePod # Allow only a single pod to access single-writer-only. +resources: +requests: + storage: 1Gi +``` + +When this feature is enabled, the existing `ReadWriteOnce(RWO)` access mode restricts volume access to a single node and allows multiple pods on the same node to read from and write to the same volume. + +To migrate existing PersistentVolumes to use `ReadWriteOncePod`, please follow the instruction from [here](https://kubernetes.io/docs/tasks/administer-cluster/change-pv-access-mode-readwriteoncepod/). ## Volume Health Monitoring CSI Driver for Unity XT supports volume health monitoring. This is an alpha feature and requires feature gate to be enabled by setting command line arguments diff --git a/content/docs/csidriver/release/powerflex.md b/content/docs/csidriver/release/powerflex.md index 1e35e36b9d..42425381bf 100644 --- a/content/docs/csidriver/release/powerflex.md +++ b/content/docs/csidriver/release/powerflex.md @@ -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 @@ -37,7 +38,10 @@ A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the erro | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | | 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. | +| Helm install of CSM for PowerFlex v1.10.0 is failing due to a duplicate `mountPath: /host_opt_emc_path` being added to volumeMounts charts/csi-vxflexos/templates/node.yaml. Error message is `Error: INSTALLATION FAILED: 1 error occurred: DaemonSet.apps "vxflexos-node" is invalid: spec.template.spec.initContainers[0].volumeMounts[4].mountPath: Invalid value: "/host_opt_emc_path": must be unique` | The issue can be resolved by removing the duplicate entry in [https://github.com/dell/helm-charts/blob/main/charts/csi-vxflexos/templates/node.yaml](https://github.com/dell/helm-charts/blob/main/charts/csi-vxflexos/templates/node.yaml) | + ### 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. +- Support for Kubernetes alpha features like Volume Health Monitoring 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`. diff --git a/content/docs/csidriver/release/powermax.md b/content/docs/csidriver/release/powermax.md index 2917a2ce46..d117bc9503 100644 --- a/content/docs/csidriver/release/powermax.md +++ b/content/docs/csidriver/release/powermax.md @@ -36,6 +36,7 @@ description: Release notes for PowerMax CSI driver | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | | Automatic SRDF group creation is failing with "Unable to get Remote Port on SAN for Auto SRDF" for PowerMaxOS 10.1 arrays | Create the SRDF Group and add it to the storage class | | [Node stage is failing with error "wwn for FC device not found"](https://github.com/dell/csm/issues/1070)| This is an intermittent issue, rebooting the node will resolve this issue | +| When the driver is installed using CSM Operator , few times, pods created using block volume are getting stuck in containercreating/terminating state or devices are not available inside the pod. | Update the daemonset with parameter `mountPropagation: "Bidirectional"` for volumedevices-path under volumeMounts section.| ### 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. +- Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters. diff --git a/content/docs/csidriver/release/powerscale.md b/content/docs/csidriver/release/powerscale.md index 2631bcb00d..c16bd31c2a 100644 --- a/content/docs/csidriver/release/powerscale.md +++ b/content/docs/csidriver/release/powerscale.md @@ -40,4 +40,4 @@ description: Release notes for PowerScale CSI driver ### 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. +- Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters. diff --git a/content/docs/csidriver/release/powerstore.md b/content/docs/csidriver/release/powerstore.md index 8b4aa101a8..7882b2c850 100644 --- a/content/docs/csidriver/release/powerstore.md +++ b/content/docs/csidriver/release/powerstore.md @@ -41,4 +41,4 @@ description: Release notes for PowerStore CSI driver ### 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. +- Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters. diff --git a/content/docs/csidriver/release/unity.md b/content/docs/csidriver/release/unity.md index 31908217ce..eb10d6451d 100644 --- a/content/docs/csidriver/release/unity.md +++ b/content/docs/csidriver/release/unity.md @@ -33,6 +33,7 @@ description: Release notes for Unity XT CSI driver | When a node goes down, the block volumes attached to the node cannot be attached to another node | This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround:
1. Force delete the pod running on the node that went down
2. Delete the VolumeAttachment to the node that went down.
Now the volume can be attached to the new node. | | A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the error `"error when creating pod: the pod uses an inline volume provided by CSIDriver csi-unity.dellemc.com, and the namespace has a pod security enforcement level that is lower than privileged."` | This issue occurs because OpenShift 4.13 introduced the CSI Volume Admission plugin to restrict the use of a CSI driver capable of provisioning CSI ephemeral volumes during pod admission. Therefore, an additional label `security.openshift.io/csi-ephemeral-volume-profile` in [csidriver.yaml](https://github.com/dell/helm-charts/blob/csi-unity-2.8.0/charts/csi-unity/templates/csidriver.yaml) file with the required security profile value should be provided. Follow [OpenShift 4.13 documentation for CSI Ephemeral Volumes](https://docs.openshift.com/container-platform/4.13/storage/container_storage_interface/ephemeral-storage-csi-inline.html) for more information. | | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | +| fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter | ### 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. +- Support for Kubernetes alpha features like Volume Health Monitoring will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters. diff --git a/content/docs/csidriver/troubleshooting/powerscale.md b/content/docs/csidriver/troubleshooting/powerscale.md index 9d783f7693..260b9a1555 100644 --- a/content/docs/csidriver/troubleshooting/powerscale.md +++ b/content/docs/csidriver/troubleshooting/powerscale.md @@ -20,3 +20,4 @@ Here are some installation failures that might be encountered and how to mitigat |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.22.0 < 1.25.0 which is incompatible with Kubernetes V1.22.11-mirantis-1 | If you are using an extended Kubernetes version, please see the [helm Chart](https://github.com/dell/helm-charts/blob/main/charts/csi-isilon/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.| | Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | | Driver install fails because of the incompatible helm values file specified in ```dell-csi-helm-installer``` - expected: v2.9.x, found: v2.8.0. | Change driver version in each file in ```dell/csi-powerscale/dell-csi-helm-installer``` from 2.8.0 to 2.9.x | +| fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter | diff --git a/content/docs/csidriver/troubleshooting/powerstore.md b/content/docs/csidriver/troubleshooting/powerstore.md index 2c9d9cd4a9..89dfb05623 100644 --- a/content/docs/csidriver/troubleshooting/powerstore.md +++ b/content/docs/csidriver/troubleshooting/powerstore.md @@ -19,3 +19,4 @@ description: Troubleshooting PowerStore Driver | Faulty paths in the multipath | Ensure that the configuration of the multipath is correct and connectivity to the underlying hardware is intact. | | Unable to install or upgrade the driver due to minimum Kubernetes version or Openshift version | Currently CSM only supports n, n-1, n-2 version of Kubernetes and Openshift, if you still wanted to continue with existing version update the `verify.sh` to continue.| | Volumes are not getting deleted on the array when PV's are deleted | Ensure `persistentVolumeReclaimPolicy` is set to Delete. | +| fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter | diff --git a/content/docs/csidriver/troubleshooting/unity.md b/content/docs/csidriver/troubleshooting/unity.md index e3a180e923..679e2a7110 100644 --- a/content/docs/csidriver/troubleshooting/unity.md +++ b/content/docs/csidriver/troubleshooting/unity.md @@ -15,3 +15,4 @@ description: Troubleshooting Unity XT Driver | 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.24.0 < 1.29.0 which is incompatible with Kubernetes 1.24.6-mirantis-1` | If you are using an extended Kubernetes version, see the helm Chart at `helm/csi-unity/Chart.yaml` and use the alternate `kubeVersion` check that is provided in the comments. *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
2. Delete the VolumeAttachment to the node that went down.
Now the volume can be attached to the new node. | | Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment --replicas=1 -n ``` | +| fsGroupPolicy may not work as expected without root privileges for NFS only [https://github.com/kubernetes/examples/issues/260](https://github.com/kubernetes/examples/issues/260) | To get the desired behavior set “RootClientEnabled” = “true” in the storage class parameter | diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template index b88527f6d5..99155d6415 100644 --- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template +++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.9.3-values.template @@ -261,6 +261,24 @@ csi-vxflexos: enabled: $VG_SNAPSHOT_ENABLED podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-vxflexos" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/vxflexos-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/vxflexos.emc.dell.com/csi_sock" + - "--labelvalue=csi-vxflexos" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/vxflexos-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" authorization: enabled: $AUTHORIZATION_ENABLED proxyHost: $AUTHORIZATION_PROXY_HOST @@ -352,6 +370,30 @@ csi-isilon: # Enable this feature only after contact support for additional information podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-isilon" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-isilon.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/csi-isilon/csi_sock" + - "--labelvalue=csi-isilon" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-isilon.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/csi-isilon-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + + podmonAPIPort: 8083 ## K8S/CSI-Unity ATTRIBUTES ########################################## @@ -422,6 +464,26 @@ csi-unity: maxUnityVolumesPerNode: $MAX_VOLUMES_PER_NODE podmon: enabled: $RESILIENCY_ENABLED + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-unity" + - "--driverPath=csi-unity.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/unity-config/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/unity.emc.dell.com/csi_sock" + - "--labelvalue=csi-unity" + - "--driverPath=csi-unity.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/unity-config/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" ## K8S/Replication Module ATTRIBUTES ########################################## diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md index dc662f6d1e..f58e26a11c 100644 --- a/content/docs/deployment/csmoperator/_index.md +++ b/content/docs/deployment/csmoperator/_index.md @@ -2,7 +2,7 @@ title: "CSM Operator" linkTitle: "CSM Operator" description: Container Storage Modules Operator -weight: 1 +weight: 2 --- The Dell Container Storage Modules Operator is a Kubernetes Operator, which can be used to install and manage the CSI Drivers and CSM Modules provided by Dell for various storage platforms. This operator is available as a community operator for upstream Kubernetes and can be deployed using OperatorHub.io. The operator can be installed using OLM (Operator Lifecycle Manager) or manually. @@ -29,9 +29,9 @@ The table below lists the driver and modules versions installable with the CSM O | CSI Unity XT | 2.10.0 | ❌ | ❌ | ❌ | ❌ | | CSI Unity XT | 2.9.0 | ❌ | ❌ | ❌ | ❌ | ->NOTE: ->- Refer to sample files [here](https://github.com/dell/csm-operator/tree/main/samples). +These CR will be used for new deployment or upgrade. In most case, it is recommended to use the latest available version. +The full compatibility matrix of CSI/CSM versions for the CSM Operator is available [here](../../prerequisites/#csm-operator-compatibility-matrix) ## Installation Dell CSM Operator can be installed manually or via Operator Hub. @@ -46,7 +46,14 @@ The installation process involves the creation of a `Subscription` object either ![OpenShit Operator Hub CSM install](operator_hub_install.gif) ->NOTE: Dell CSM Operator is distributed as both `Certified` & `Community` editions. Both editions have the same codebase and are supported by Dell Technologies, the only difference is that the `Certified` version is validated by RedHat. The `Certified` version is often released couple of days/weeks after the `Community` version. +### Certified vs Community +Dell CSM Operator is distributed as both `Certified` & `Community` editions. + +Both editions have the same codebase and are supported by Dell Technologies, the only differences are: +* The `Certified` version is officially supported by Redhat by partnering with software vendors. +* The `Certified` version is often released couple of days/weeks after the `Community` version. +* The `Certified` version is specific to Openshift and can only be installed on specific Openshift versions where it is certified. +* The `Community` can be installed on any Kubernetes distributions. ### Manual Installation on a cluster without OLM diff --git a/content/docs/deployment/helm/drivers/upgrade/powerflex.md b/content/docs/deployment/helm/drivers/upgrade/powerflex.md index 68fca334b8..2b3328d4e4 100644 --- a/content/docs/deployment/helm/drivers/upgrade/powerflex.md +++ b/content/docs/deployment/helm/drivers/upgrade/powerflex.md @@ -10,7 +10,7 @@ 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. diff --git a/content/docs/deployment/helm/modules/_index.md b/content/docs/deployment/helm/modules/_index.md index c38d75e6b9..5493a71b5a 100644 --- a/content/docs/deployment/helm/modules/_index.md +++ b/content/docs/deployment/helm/modules/_index.md @@ -1,6 +1,6 @@ --- -title: "CSM modules" -linkTitle: "CSM modules" -description: Deployment of Dell CSM modules using helm +title: "CSM Modules" +linkTitle: "CSM Modules" +description: Deployment of Dell CSM Modules using helm weight: 1 --- \ No newline at end of file diff --git a/content/docs/deployment/helm/modules/installation/_index.md b/content/docs/deployment/helm/modules/installation/_index.md index 2ac5c65f62..61a683caa1 100644 --- a/content/docs/deployment/helm/modules/installation/_index.md +++ b/content/docs/deployment/helm/modules/installation/_index.md @@ -1,6 +1,6 @@ --- title: "Installation" linkTitle: "Installation" -description: Deployment of Dell CSM modules using helm +description: Deployment of Dell CSM Modules using helm weight: 1 --- \ No newline at end of file diff --git a/content/docs/deployment/helm/modules/installation/applicationmobility/_index.md b/content/docs/deployment/helm/modules/installation/applicationmobility/_index.md index 68c07a9e6a..a642325d42 100644 --- a/content/docs/deployment/helm/modules/installation/applicationmobility/_index.md +++ b/content/docs/deployment/helm/modules/installation/applicationmobility/_index.md @@ -7,7 +7,7 @@ Description: > --- ## Pre-requisites -- [Request a License for Application Mobility](../../../../../license/) +- [Request a License for Application Mobility](../../../../../support/license/) - Object store bucket accessible by both the source and target clusters ## Installation diff --git a/content/docs/deployment/helm/modules/installation/authorization/_index.md b/content/docs/deployment/helm/modules/installation/authorization/_index.md index 1a6149d2bb..3a2231ab19 100644 --- a/content/docs/deployment/helm/modules/installation/authorization/_index.md +++ b/content/docs/deployment/helm/modules/installation/authorization/_index.md @@ -6,7 +6,7 @@ description: > --- {{% pageinfo color="primary" %}} -The CSM Authorization karavictl CLI is no longer actively maintained or supported. It will be deprecated in CSM 2.0. +The CSM Authorization karavictl CLI is no longer actively maintained or supported. It will be deprecated in a future release. {{% /pageinfo %}} CSM Authorization can be installed by using the provided Helm v3 charts on Kubernetes platforms. @@ -28,9 +28,15 @@ The following third-party components are optionally installed in the specified n ## Install CSM Authorization **Steps** -1. Run `git clone https://github.com/dell/helm-charts.git` to clone the git repository. - -2. Ensure that you have created a namespace where you want to install CSM Authorization. You can run `kubectl create namespace authorization` to create a new one. +1. Create a namespace where you want to install CSM Authorization. + ```bash + kubectl create namespace authorization + ``` + +2. Add the Dell Helm Charts repo + ```bash + helm repo add dell https://dell.github.io/helm-charts + ``` 3. Prepare `samples/csm-authorization/config.yaml` which contains the JWT signing secret. The following table lists the configuration parameters. diff --git a/content/docs/deployment/helm/modules/installation/encryption/_index.md b/content/docs/deployment/helm/modules/installation/encryption/_index.md index f4b44dfaf2..6a70cf3b31 100644 --- a/content/docs/deployment/helm/modules/installation/encryption/_index.md +++ b/content/docs/deployment/helm/modules/installation/encryption/_index.md @@ -82,7 +82,7 @@ Apart from any secrets and config maps described in the CSI driver documentation ### Secret *encryption-license* -Request a trial license following instructions on the [License page](../../../../../license). You will be provided with a YAML file similar to: +Request a trial license following instructions on the [License page](../../../../../support/license/). You will be provided with a YAML file similar to: ```yaml apiVersion: v1 diff --git a/content/docs/deployment/helm/modules/uninstall/_index.md b/content/docs/deployment/helm/modules/uninstall/_index.md index de68ea70fd..1cd30cebac 100644 --- a/content/docs/deployment/helm/modules/uninstall/_index.md +++ b/content/docs/deployment/helm/modules/uninstall/_index.md @@ -1,6 +1,6 @@ --- title: "Uninstallation" linkTitle: "Uninstallation" -description: Uninstallation of Dell CSM modules using helm +description: Uninstallation of Dell CSM Modules using helm weight: 1 --- \ No newline at end of file diff --git a/content/docs/deployment/helm/modules/uninstall/authorization.md b/content/docs/deployment/helm/modules/uninstall/authorization.md index 0c8bb62789..9774f920b0 100644 --- a/content/docs/deployment/helm/modules/uninstall/authorization.md +++ b/content/docs/deployment/helm/modules/uninstall/authorization.md @@ -6,24 +6,20 @@ description: > Dell Technologies (Dell) Container Storage Modules (CSM) for Authorization Uninstallation --- -{{% pageinfo color="primary" %}} -The CSM Authorization RPM will be deprecated in a future release. It is highly recommended that you use CSM Authorization Helm deployment or CSM Operator going forward. -{{% /pageinfo %}} - This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization. -## Uninstalling the RPM +## Uninstall the CSM for Authorization Helm Chart -To uninstall the rpm package on the system, you must first uninstall the K3s SELinux package if SELinux is enabled. To uninstall the K3s SELinux package, run: +The command below removes all the Kubernetes components associated with the chart. ```bash -rpm -e k3s-selinux +helm uninstall authorization --namespace authorization ``` -To uninstall the CSM Authorization rpm package on the system, run: +You may also want to delete the karavi-config-secret secret. ```bash -rpm -e +kubectl delete secret karavi-config-secret -n authorization ``` ## Uninstalling the sidecar-proxy in the CSI Driver diff --git a/content/docs/deployment/helm/modules/upgrade/authorization.md b/content/docs/deployment/helm/modules/upgrade/authorization.md index 1645c89789..31a3b5f9c0 100644 --- a/content/docs/deployment/helm/modules/upgrade/authorization.md +++ b/content/docs/deployment/helm/modules/upgrade/authorization.md @@ -3,64 +3,39 @@ title: Authorization linktitle: Authorization weight: 3 description: > - Upgrade Dell Technologies (Dell) Container Storage Modules (CSM) for Authorization + Dell Technologies (Dell) Container Storage Modules (CSM) for Authorization Upgrade --- -{{% pageinfo color="primary" %}} -The CSM Authorization RPM will be deprecated in a future release. It is highly recommended that you use CSM Authorization Helm deployment or CSM Operator going forward. -{{% /pageinfo %}} - This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts: -- Upgrading the CSM for Authorization proxy server +- Helm Chart Upgrade - Upgrading the Dell CSI drivers with CSM for Authorization enabled -### Upgrading CSM for Authorization proxy server - -Obtain the latest single binary installer RPM by following one of our two options [here](../../installation/authorization#single-binary-installer). - -To update the rpm package on the system, run the below command from within the extracted folder: - -```bash -sh install_karavi_auth.sh --upgrade -``` - -As an option, on version 1.6.0, the Nodeports for the ingress controller can be specified: - -```bash +## Helm Chart Upgrade -sh install_karavi_auth.sh --upgrade --traefik_web_port --traefik_websecure_port -``` -Ex.: -```bash +1. To upgrade an existing Helm installation of CSM for Authorization to the latest release, download the latest Helm charts. + ```bash + helm repo update + ``` -sh install_karavi_auth.sh --upgrade --traefik_web_port 30001 --traefik_websecure_port 30002 -``` +2. Check if the latest Helm chart version is available: + ```bash + helm search repo dell + ``` -To verify that the new version of the rpm is installed and K3s has been updated, run the below commands: + ``` + NAME CHART VERSION APP VERSION DESCRIPTION + dell/csm-authorization 1.10.0 1.10.0 CSM for Authorization is part of the [Container... + ``` -```bash -rpm -qa | grep karavi -k3s kubectl version -``` +3. Upgrade to the latest CSM for Authorization release: + ```bash + helm upgrade --version $latest_chart_version -f myvalues.yaml authorization dell/csm-authorization -n authorization + ``` ->__Note__: The above steps manage install and upgrade of all dependencies that are required by the CSM for Authorization proxy server. - -### Upgrading Dell CSI Driver(s) with CSM for Authorization enabled +## Upgrading Dell CSI Driver(s) with CSM for Authorization enabled Given a setup where the CSM for Authorization proxy server is already upgraded to the latest version, follow the upgrade instructions for the applicable CSI Driver(s) to upgrade the driver and the CSM for Authorization sidecar - [Upgrade PowerFlex CSI driver](../../../drivers/upgrade/powerflex/) - [Upgrade PowerMax CSI driver](../../../drivers/upgrade/powermax/) - [Upgrade PowerScale CSI driver](../../../drivers/upgrade/isilon/) - -## Rollback - -This section outlines the rollback steps for Container Storage Modules (CSM) for Authorization. -### Rollback CSM for Authorization proxy server - -To rollback the rpm package on the system, run the below command: - -```bash - -rpm -Uvh --oldpackage karavi-authorization-.x86_64.rpm --nopreun --nopostun -``` diff --git a/content/docs/deployment/rpm/_index.md b/content/docs/deployment/rpm/_index.md new file mode 100644 index 0000000000..4fbf59604c --- /dev/null +++ b/content/docs/deployment/rpm/_index.md @@ -0,0 +1,8 @@ +--- +title: "RPM" +linkTitle: "RPM" +description: RPM Deployment of Container Storage Modules +weight: 5 +--- + +RPM Deployment of Container Storage Modules \ No newline at end of file diff --git a/content/docs/deployment/rpm/modules/_index.md b/content/docs/deployment/rpm/modules/_index.md new file mode 100644 index 0000000000..0b44d7d9db --- /dev/null +++ b/content/docs/deployment/rpm/modules/_index.md @@ -0,0 +1,6 @@ +--- +title: "CSM Modules" +linkTitle: "CSM Modules" +description: Deployment of Dell CSM Modules using RPM +weight: 1 +--- \ No newline at end of file diff --git a/content/docs/deployment/rpm/modules/installation/_index.md b/content/docs/deployment/rpm/modules/installation/_index.md new file mode 100644 index 0000000000..a0a63d2a78 --- /dev/null +++ b/content/docs/deployment/rpm/modules/installation/_index.md @@ -0,0 +1,6 @@ +--- +title: "Installation" +linkTitle: "Installation" +description: Deployment of Dell CSM Modules using RPM +weight: 1 +--- diff --git a/content/docs/deployment/rpm/modules/installation/authorization/authorization.md b/content/docs/deployment/rpm/modules/installation/authorization/authorization.md new file mode 100644 index 0000000000..e4e1a55af0 --- /dev/null +++ b/content/docs/deployment/rpm/modules/installation/authorization/authorization.md @@ -0,0 +1,194 @@ +--- +title: Authorization +linktitle: Authorization +description: > + Dell Technologies (Dell) Container Storage Modules (CSM) for Authorization RPM deployment +--- + +{{% pageinfo color="primary" %}} +The CSM Authorization RPM will be deprecated in a future release. It is highly recommended that you use CSM Authorization Helm deployment or CSM Operator going forward. +{{% /pageinfo %}} + +This section outlines the deployment steps for Container Storage Modules (CSM) for Authorization. The deployment of CSM for Authorization is handled in 2 parts: +- Deploying the CSM for Authorization proxy server, to be controlled by storage administrators +- Configuring one to many [supported](../../../../../../prerequisites/#supported-csm-modules) Dell CSI drivers with CSM for Authorization + +## Prerequisites + +The CSM for Authorization proxy server requires a Linux host with the following minimum resource allocations: +- 32 GB of memory +- 4 CPU +- 200 GB local storage + +The following package needs to be installed on the Linux host: +- container-selinux + +Use the appropriate package manager on the machine to install the package. + +### Using yum on CentOS/RedHat 7: + +yum install -y container-selinux + +### Using yum on CentOS/RedHat 8: + +yum install -y container-selinux + +### Dark Sites + +For environments where `yum` will not work, obtain the supported version of container-selinux for your OS version and install it. + +The container-selinux RPMs for CentOS/RedHat 7 and 8 can be downloaded from [https://centos.pkgs.org/7/centos-extras-x86_64/](https://centos.pkgs.org/7/centos-extras-x86_64/) and [https://centos.pkgs.org/8-stream/centos-appstream-x86_64/](https://centos.pkgs.org/8-stream/centos-appstream-x86_64/), respectively. + +## Deploying the CSM Authorization Proxy Server + +The first part of deploying CSM for Authorization is installing the proxy server. This activity and the administration of the proxy server will be owned by the storage administrator. + +The CSM for Authorization proxy server is installed using a shell script after extracting from a tar archive. + +If CSM for Authorization is being installed on a system where SELinux is enabled, you must ensure the proper SELinux policies have been installed. + +### Shell Script Installer + +The easiest way to obtain the tar archive with the shell script installer is directly from the [GitHub repository's releases](https://github.com/dell/karavi-authorization/releases) section. + +Alternatively, the tar archive can be built from source by cloning the [GitHub repository](https://github.com/dell/karavi-authorization) and using the following Makefile targets to build the installer: + +```bash +make dist build-installer rpm package +``` + +The `build-installer` step creates a binary at `karavi-authorization/bin/deploy` and embeds all components required for installation. The `rpm` step generates an RPM package and stores it at `karavi-authorization/deploy/rpm/x86_64/`. The `package` step bundles the install script, authorization package, pre-downloaded K3s-SELinux packages, and policies folder together for the installation in the `packages/` directory. +This allows CSM for Authorization to be installed in network-restricted environments. + +A Storage Administrator can execute the shell script, install_karavi_auth.sh as a root user or via `sudo`. + +### Installing the RPM + +1. Before installing the rpm, some network and security configuration inputs need to be provided in json format. The json file should be created in the location `$HOME/.karavi/config.json` having the following contents: + + ```json + { + "web": { + "jwtsigningsecret": "secret" + }, + "proxy": { + "host": ":8080" + }, + "zipkin": { + "collectoruri": "http://zipkin-addr:9411/api/v2/spans", + "probability": 1 + }, + "certificate": { + "keyFile": "path_to_private_key_file", + "crtFile": "path_to_host_cert_file", + "rootCertificate": "path_to_root_CA_file" + }, + "hostname": "DNS-hostname" + } + ``` + + In an instance where a secure deployment is not required, an insecure deployment is possible. Please note that self-signed certificates will be created for you using cert-manager to allow TLS encryption for communication on the CSM for Authorization proxy server. However, this is not recommended for production environments. For an insecure deployment, the json file in the location `$HOME/.karavi/config.json` only requires the following contents: + + ```json + { + "hostname": "DNS-hostname" + } + ``` + +>__Note__: +> - `DNS-hostname` refers to the hostname of the system in which the CSM for Authorization server will be installed. This hostname can be found by running `nslookup ` +> - There are a number of ways to create certificates. In a production environment, certificates are usually created and managed by an IT administrator. Otherwise, certificates can be created using OpenSSL. +3. To install the rpm package on the system, you must first extract the contents of the tar file with the command: + + ```shell + tar -xvf karavi_authorization_ + ``` + +4. Afterwards, you must enter the extracted folder's directory and run the shell script: + + ```shell + cd karavi_authorization_ + sh install_karavi_auth.sh + ``` + + As an option, on version 1.6.0, the Nodeports for the ingress controller can be specified: + ```bash + + sh install_karavi_auth.sh --traefik_web_port --traefik_websecure_port + ```` + Ex.: + ```bash + sh install_karavi_auth.sh --traefik_web_port 30001 --traefik_websecure_port 30002 + ``` + +5. After installation, application data will be stored on the system under `/var/lib/rancher/k3s/storage/`. + +If errors occur during installation, review the [Troubleshooting](../../../../../../authorization/troubleshooting) section. + +## Configuring the CSM for Authorization Proxy Server + +The first part of CSM for Authorization deployment is to configure the proxy server. This is controlled by the Storage Administrator. + +Please follow the steps outlined in the [proxy server](../../../../../../authorization/configuration/proxy-server) configuration. + +## Configuring a Dell CSI Driver with CSM for Authorization + +The second part of CSM for Authorization deployment is to configure one or more of the [supported](../../../../../../prerequisites/#supported-csm-modules) CSI drivers. This is controlled by the Kubernetes tenant administrator. + +Please follow the steps outlined in [PowerFlex](../../../../../../authorization/configuration/powerflex), [PowerMax](../../../../../../authorization/configuration/powermax), or [PowerScale](../../../../../../authorization/configuration/powerscale) to configure the CSI Driver to work with the Authorization sidecar. + +## Updating CSM for Authorization Proxy Server Configuration + +CSM for Authorization has a subset of configuration parameters that can be updated dynamically: + +| Parameter | Type | Default | Description | +| -------------------- | ------ | -------- | ---------------------------------- | +| web.jwtsigningsecret | String | "secret" | The secret used to sign JWT tokens | + +Updating configuration parameters can be done by editing the `karavi-config-secret` on the CSM for the Authorization Server. The secret can be queried using k3s and kubectl like so: + +```bash +k3s kubectl -n karavi get secret/karavi-config-secret +``` + +To update or add parameters, you must edit the base64 encoded data in the secret. The` karavi-config-secret` data can be decoded like so: + +```bash +k3s kubectl -n karavi get secret/karavi-config-secret -o yaml | grep config.yaml | head -n 1 | awk '{print $2}' | base64 -d +``` + +Save the output to a file or copy it to an editor to make changes. Once you are done with the changes, you must encode the data to base64. If your changes are in a file, you can encode it like so: + +```bash +cat | base64 +``` + +Copy the new, encoded data and edit the `karavi-config-secret` with the new data. Run this command to edit the secret: + +```bash +k3s kubectl -n karavi edit secret/karavi-config-secret +``` + +Replace the data in `config.yaml` under the `data` field with your new, encoded data. Save the changes and CSM for Authorization will read the changed secret. + +>__Note__: If you are updating the signing secret, the tenants need to be updated with new tokens via the `karavictl generate token` command like so. The `--insecure` flag is required if certificates were not provided in `$HOME/.karavi/config.json` + +```bash +karavictl generate token --tenant $TenantName --insecure --addr DNS-hostname | sed -e 's/"Token": //' -e 's/[{}"]//g' -e 's/\\n/\n/g' | kubectl -n $namespace apply -f - +``` + +## CSM for Authorization Proxy Server Dynamic Configuration Settings + +Some settings are not stored in the `karavi-config-secret` but in the csm-config-params ConfigMap, such as LOG_LEVEL and LOG_FORMAT. To update the CSM for Authorization logging settings during runtime, run the below command on the K3s cluster, make your changes, and save the updated configmap data. + +```bash +k3s kubectl -n karavi edit configmap/csm-config-params +``` + +This edit will not update the logging level for the sidecar-proxy containers running in the CSI Driver pods. To update the sidecar-proxy logging levels, you must update the associated CSI Driver ConfigMap in a similar fashion: + +```bash +kubectl -n [CSM_CSI_DRVIER_NAMESPACE] edit configmap/-config-params +``` + +Using PowerFlex as an example, `kubectl -n vxflexos edit configmap/vxflexos-config-params` can be used to update the logging level of the sidecar-proxy and the driver. diff --git a/content/docs/deployment/rpm/modules/uninstall/_index.md b/content/docs/deployment/rpm/modules/uninstall/_index.md new file mode 100644 index 0000000000..914120aa2c --- /dev/null +++ b/content/docs/deployment/rpm/modules/uninstall/_index.md @@ -0,0 +1,7 @@ +--- +title: "Uninstallation" +linkTitle: "Uninstallation" +description: Uninstallation of Dell CSM Modules using RPM +weight: 1 +--- + diff --git a/content/docs/deployment/rpm/modules/uninstall/authorization.md b/content/docs/deployment/rpm/modules/uninstall/authorization.md new file mode 100644 index 0000000000..253817347e --- /dev/null +++ b/content/docs/deployment/rpm/modules/uninstall/authorization.md @@ -0,0 +1,31 @@ +--- +title: Authorization +linktitle: Authorization +weight: 2 +description: > + Dell Technologies (Dell) Container Storage Modules (CSM) for Authorization Uninstallation +--- + +{{% pageinfo color="primary" %}} +The CSM Authorization RPM will be deprecated in a future release. It is highly recommended that you use CSM Authorization Helm deployment or CSM Operator going forward. +{{% /pageinfo %}} + +This section outlines the uninstallation steps for Container Storage Modules (CSM) for Authorization. + +## Uninstalling the RPM + +To uninstall the rpm package on the system, you must first uninstall the K3s SELinux package if SELinux is enabled. To uninstall the K3s SELinux package, run: + +```bash +rpm -e k3s-selinux +``` + +To uninstall the CSM Authorization rpm package on the system, run: + +```bash +rpm -e +``` + +## Uninstalling the sidecar-proxy in the CSI Driver + +To uninstall the sidecar-proxy in the CSI Driver, [uninstall](../../../../helm/drivers/uninstall) the driver and [reinstall](../../../../helm/drivers/installation) the driver using the original configuration secret. diff --git a/content/docs/deployment/rpm/modules/upgrade/_index.md b/content/docs/deployment/rpm/modules/upgrade/_index.md new file mode 100644 index 0000000000..53c6a58240 --- /dev/null +++ b/content/docs/deployment/rpm/modules/upgrade/_index.md @@ -0,0 +1,7 @@ +--- +title: "Upgrade" +tags: + - upgrade +weight: 3 +Description: Upgrade of Dell CSM Modules using RPM +--- diff --git a/content/docs/deployment/rpm/modules/upgrade/authorization.md b/content/docs/deployment/rpm/modules/upgrade/authorization.md new file mode 100644 index 0000000000..af14f3404b --- /dev/null +++ b/content/docs/deployment/rpm/modules/upgrade/authorization.md @@ -0,0 +1,66 @@ +--- +title: Authorization +linktitle: Authorization +weight: 3 +description: > + Dell Technologies (Dell) Container Storage Modules (CSM) for Authorization Upgrade +--- + +{{% pageinfo color="primary" %}} +The CSM Authorization RPM will be deprecated in a future release. It is highly recommended that you use CSM Authorization Helm deployment or CSM Operator going forward. +{{% /pageinfo %}} + +This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization RPM is handled in 2 parts: +- Upgrading the CSM for Authorization proxy server +- Upgrading the Dell CSI drivers with CSM for Authorization enabled + +## Upgrading CSM for Authorization proxy server + +Obtain the latest single binary installer RPM by following one of our two options [here](../../installation/authorization/authorization#single-binary-installer). + +To update the rpm package on the system, run the below command from within the extracted folder: + +```bash +sh install_karavi_auth.sh --upgrade +``` + +As an option, on version 1.6.0, the Nodeports for the ingress controller can be specified: + +```bash + +sh install_karavi_auth.sh --upgrade --traefik_web_port --traefik_websecure_port +``` +Ex.: +```bash + +sh install_karavi_auth.sh --upgrade --traefik_web_port 30001 --traefik_websecure_port 30002 +``` + +To verify that the new version of the rpm is installed and K3s has been updated, run the below commands: + +```bash +rpm -qa | grep karavi +k3s kubectl version +``` + +>__Note__: The above steps manage install and upgrade of all dependencies that are required by the CSM for Authorization proxy server. + +## Upgrading Dell CSI Driver(s) with CSM for Authorization enabled + +Given a setup where the CSM for Authorization proxy server is already upgraded to the latest version, follow the upgrade instructions for the applicable CSI Driver(s) to upgrade the driver and the CSM for Authorization sidecar + +- [Upgrade PowerFlex CSI driver](../../../../helm/drivers/upgrade/powerflex/) +- [Upgrade PowerMax CSI driver](../../../../helm/drivers/upgrade/powermax/) +- [Upgrade PowerScale CSI driver](../../../../helm/drivers/upgrade/isilon/) + +## Rollback + +This section outlines the rollback steps for Container Storage Modules (CSM) for Authorization. +### Rollback CSM for Authorization proxy server + +To rollback the rpm package on the system, run the below command: + +```bash + +rpm -Uvh --oldpackage karavi-authorization-.x86_64.rpm --nopreun --nopostun +``` diff --git a/content/docs/interactive-tutorials/_index.md b/content/docs/interactive-tutorials/_index.md index 5529bff269..51eca852bf 100644 --- a/content/docs/interactive-tutorials/_index.md +++ b/content/docs/interactive-tutorials/_index.md @@ -9,18 +9,15 @@ Welcome to Dell CSM's interactive tutorials section! Try the different modules w Our interactive tutorials provide step-by-step guidance on how to use our CSM products in the context of PowerFlex Software-Defined-Storage. -
- /* 16:9 Aspect Ratio (divide 9 by 16 = 0.5625) */ - -
+{{< cardpane >}} + {{< card header="[**CSM Quickstart**](csm-quickstart/)">}} + If you are new to Dell CSM, start here and use the different modules interactively. + {{< /card >}} +{{< /cardpane >}} -> NOTE: It takes about 15 minutes for the lab to be ready to use. + +{{< cardpane >}} + {{< card header="[**CSM Operator**](csm-operator/)">}} + In this tutorial, you will learn how to install and use the CSM Operator. + {{< /card >}} +{{< /cardpane >}} diff --git a/content/docs/interactive-tutorials/csm-operator/_index.md b/content/docs/interactive-tutorials/csm-operator/_index.md new file mode 100644 index 0000000000..c1f14b1b7d --- /dev/null +++ b/content/docs/interactive-tutorials/csm-operator/_index.md @@ -0,0 +1,29 @@ +--- +title: "How to install the Dell Container Storage Modules (CSM) Operator" +linkTitle: "CSM Operator" +no_list: true +description: Learn how to install Dell Container Storage Modules Operator and enable the Resiliency module. +weight: 2 +--- +This track demonstrates how to: +- Download and install the CSM Operator. +- Enable CSI for PowerFlex using the CSM Operator. +- Use of CSI for Dell PowerFlex. +- Enable the Resiliency module using the CSM Operator. +- Use Resiliency once it is enabled. + +
+ /* 16:9 Aspect Ratio (divide 9 by 16 = 0.5625) */ + +
+ +> NOTE: It takes about 15 minutes for the lab to be ready to use. diff --git a/content/docs/interactive-tutorials/csm-quickstart/_index.md b/content/docs/interactive-tutorials/csm-quickstart/_index.md new file mode 100644 index 0000000000..8ef39b262b --- /dev/null +++ b/content/docs/interactive-tutorials/csm-quickstart/_index.md @@ -0,0 +1,29 @@ +--- +title: "Getting Started with Dell Container Storage Modules (CSM)" +linkTitle: "CSM Quickstart" +no_list: true +description: Learn the basics of Container Storage Modules from Dell Technologies +weight: 1 +--- +Learn the basics of Dell Container Storage Modules by using: + - CSI for PowerFlex + - CSM Authentication + - CSM Resiliency + - CSM Observability + + +
+ /* 16:9 Aspect Ratio (divide 9 by 16 = 0.5625) */ + +
+ +> NOTE: It takes about 15 minutes for the lab to be ready to use. diff --git a/content/docs/prerequisites/_index.md b/content/docs/prerequisites/_index.md index a82f4c3dac..9411ece5b8 100644 --- a/content/docs/prerequisites/_index.md +++ b/content/docs/prerequisites/_index.md @@ -24,18 +24,18 @@ weight: 1 ## Supported Container Orchestrator Platforms {{
}} -| Platform | Version | -|---------------|:----------------:| -| Kubernetes | 1.27, 1.28, 1.29 | -| Red Hat OpenShift | 4.13, 4.14 | -| Mirantis Kubernetes Engine | 3.7.x | -| Google Anthos | 1.15 | -| Rancher Kubernetes Engine | 1.4.x | -| VMware Tanzu | 7.0 | +| Platform | Version | +|----------------------------|:----------------:| +| Kubernetes | 1.27, 1.28, 1.29 | +| Red Hat OpenShift | 4.13, 4.14 | +| Mirantis Kubernetes Engine | 3.7.x | +| Google Anthos | 1.15 | +| Rancher Kubernetes Engine | 1.4.x | +| VMware Tanzu | 7.0 | {{
}} > Notes: -> * Any orchestrator platform or version that's not mentioned here must be self-certified using [Cert-CSI](../cert-csi/) in order to be supported. Although not mandatory, we recommend users to use orchestrator platforms and versions that have not met their end of life. +> * Any orchestrator platform or version that's not mentioned here must be self-certified using [Cert-CSI](../support/cert-csi/) in order to be supported. Although not mandatory, we recommend users to use orchestrator platforms and versions that have not met their end of life. ## Tested Host Operating Systems @@ -47,20 +47,45 @@ Container Storage Modules (CSM) does not officially support specific operating s > Notes: > * The host operating system/version being used must align with what each Dell Storage platform supports. Please visit [E-Lab Navigator](https://elabnavigator.dell.com/eln/modernHomeSSM) for specific Dell Storage platform host operating system level support matrices. -> * Any operating system or version that's not mentioned here must be self-certified using [Cert-CSI](../cert-csi/) in order to be supported. Although not mandatory, we recommend users to use operating systems and versions that have not met their end of life. +> * Any operating system or version that's not mentioned here must be self-certified using [Cert-CSI](../support/cert-csi/) in order to be supported. Although not mandatory, we recommend users to use operating systems and versions that have not met their end of life. ## Supported CSM Modules {{}} -| CSM Module | PowerMax | PowerFlex | Unity XT | PowerScale | PowerStore | -|---------------|:----------------:|:----------------:|:----------------:|:----------------:|:----------------:| -| [CSM Authorization](../authorization/) | Yes | Yes | Yes | Yes | No | -| [CSM Observability](../observability/) | Yes | Yes | No | Yes | Yes | -| [CSM Replication](../replication/) | Yes | Yes | No | Yes | Yes | -| [CSM Resiliency](../resiliency/) | No | Yes | Yes | Yes | Yes | -| [CSM Encryption](../secure/encryption/) | No | No | No | Yes | No | -| [CSM Application Mobility](../applicationmobility/) | Yes | Yes | Yes | Yes | Yes | +| CSM Module | PowerMax | PowerFlex | Unity XT | PowerScale | PowerStore | +|----------------------------------------|:--------:|:---------:|:--------:|:----------:|:----------:| +| [CSM Authorization](../authorization/) | Yes | Yes | Yes | Yes | No | +| [CSM Observability](../observability/) | Yes | Yes | No | Yes | Yes | +| [CSM Replication](../replication/) | Yes | Yes | No | Yes | Yes | +| [CSM Resiliency](../resiliency/) | No | Yes | Yes | Yes | Yes | +| [CSM Encryption](../secure/encryption/)| No | No | No | Yes | No | +| [CSM Application Mobility](../applicationmobility/) | Yes | Yes | Yes | Yes | Yes | +| [Volume Group Snapshot](../snapshots/volume-group-snapshots/) | No | Yes | No | No | Yes | + {{
}} > Notes: > * Encryption and Application Mobility are available as a Technical Preview only and are not officially supported. + +## CSM Operator compatibility matrix + +The table below lists the driver and modules versions installable with the CSM Operator: +{{}} +| CSI Driver | Version | CSM Authorization | CSM Replication | CSM Observability | CSM Resiliency | +| ------------------ |---------|-------------------|-----------------|-------------------|----------------| +| CSI PowerScale | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ✔ 1.9.0 | +| CSI PowerScale | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | +| CSI PowerScale | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ✔ 1.7.0 | +| CSI PowerFlex | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ✔ 1.9.0 | +| CSI PowerFlex | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ✔ 1.8.0 | +| CSI PowerFlex | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ✔ 1.7.0 | +| CSI PowerStore | 2.10.0 | ❌ | ❌ | ❌ | ✔ 1.9.0 | +| CSI PowerStore | 2.9.0 | ❌ | ❌ | ❌ | ✔ 1.8.0 | +| CSI PowerStore | 2.8.0 | ❌ | ❌ | ❌ | ✔ 1.7.0 | +| CSI PowerMax | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ❌ | +| CSI PowerMax | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ❌ | +| CSI PowerMax | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ❌ | +| CSI Unity XT | 2.10.0 | ❌ | ❌ | ❌ | ❌ | +| CSI Unity XT | 2.9.0 | ❌ | ❌ | ❌ | ❌ | +| CSI Unity XT | 2.8.0 | ❌ | ❌ | ❌ | ❌ | +{{
}} diff --git a/content/docs/references/FAQ/_index.md b/content/docs/references/FAQ/_index.md deleted file mode 100644 index 19199ffd2d..0000000000 --- a/content/docs/references/FAQ/_index.md +++ /dev/null @@ -1,112 +0,0 @@ ---- -title: "CSM FAQ" -linktitle: "FAQ" -description: Frequently asked questions of Dell Technologies (Dell) Container Storage Modules -weight: 1 ---- - -- [What are Dell Container Storage Modules (CSM)? How different is it from a CSI driver?](#what-are-dell-container-storage-modules-csm-how-different-is-it-from-a-csi-driver) -- [Where do I start with Dell Container Storage Modules (CSM)?](#where-do-i-start-with-dell-container-storage-modules-csm) -- [What are the prerequisites for deploying Container Storage Modules?](#what-are-the-prerequisites-for-deploying-container-storage-modules) -- [How do I uninstall or disable a module?](#how-do-i-uninstall-or-disable-a-module) -- [How do I troubleshoot Container Storage Modules?](#how-do-i-troubleshoot-container-storage-modules) -- [Can I use the CSM functionality like Prometheus collection or Authorization quotas for my non-Kubernetes storage clients?](#can-i-use-the-csm-functionality-like-prometheus-collection-or-authorization-quotas-for-my-non-kubernetes-storage-clients) -- [Should I install the module in the same namespace as the driver or another?](#should-i-install-the-module-in-the-same-namespace-as-the-driver-or-another) -- [Which Kubernetes distributions are supported?](#which-kubernetes-distributions-are-supported) -- [How do I get a list of Container Storage Modules deployed in my cluster with their versions?](#how-do-i-get-a-list-of-container-storage-modules-deployed-in-my-cluster-with-their-versions) -- [Do all Container Storage Modules need to be the same version, or can I mix and match?](#do-all-container-storage-modules-need-to-be-the-same-version-or-can-i-mix-and-match) -- [Can I run Container Storage Modules in a production environment?](#can-i-run-container-storage-modules-in-a-production-environment) -- [Is Dell Container Storage Modules (CSM) supported by Dell Technologies?](#is-dell-container-storage-modules-csm-supported-by-dell-technologies) -- [Can I modify a module or contribute to the project?](#can-i-modify-a-module-or-contribute-to-the-project) -- [What is coming next?](#what-is-coming-next) - -### What are Dell Container Storage Modules (CSM)? How different is it from a CSI driver? -Dell **C**ontainer **S**torage **M**odules are a set of modules that aim to extend features beyond what is available in the [CSI specification](https://kubernetes-csi.github.io/docs/). - -The main goal with CSM modules is to expose storage array enterprise features directly within Kubernetes so developers are empowered to leverage them for their deployment in a seamless way. - -### Where do I start with Dell Container Storage Modules (CSM)? -The umbrella repository for every Dell Container Storage Module is: [https://github.com/dell/csm](https://github.com/dell/csm). - -### What are the prerequisites for deploying Container Storage Modules? -Prerequisites can be found on the respective module deployment pages: -- [Dell Container Storage Module for Observability Deployment](../../deployment/helm/modules/installation/observability/deployment#prerequisites) -- [Dell Container Storage Module for Authorization Deployment](../../deployment/helm/modules/installation/authorization#prerequisites) -- [Dell Container Storage Module for Resiliency Deployment](../../deployment/helm/modules/installation/resiliency) -- [Dell Container Storage Module for Replication Deployment](../../deployment/helm/modules/installation/replication/installation/#before-you-begin) -- [Dell Container Storage Module for Application Mobility Deployment](../../deployment/helm/modules/installation/applicationmobility#pre-requisites) -- [Dell Container Storage Module for Encryption Deployment](../../deployment/helm/modules/installation/encryption#vault-server) - -Prerequisites for deploying the Dell CSI drivers can be found here: -- [Dell CSI Drivers Deployment](../../deployment/helm/drivers/installation/) - -### How do I uninstall or disable a module? -- [Dell Container Storage Module for Authorization](../../deployment/helm/modules/uninstall/authorization/) -- [Dell Container Storage Module for Observability](../../deployment/helm/modules/uninstall/observability/) -- [Dell Container Storage Module for Resiliency](../../deployment/helm/modules/uninstall/resiliency/) -- [Dell Container Storage Module for Replication](../../deployment/helm/modules/uninstall/replication/) -- [Dell Container Storage Module for Application Mobility](../../deployment/helm/modules/uninstall/applicationmobility/) -- [Dell Container Storage Module for Encryption](../../deployment/helm/modules/uninstall/encryption/) - -### How do I troubleshoot Container Storage Modules? -- [Dell CSI Drivers](../../csidriver/troubleshooting/) -- [Dell Container Storage Module for Authorization](../../authorization/troubleshooting/) -- [Dell Container Storage Module for Observability](../../observability/troubleshooting/) -- [Dell Container Storage Module for Replication](../../replication/troubleshooting/) -- [Dell Container Storage Module for Resiliency](../../resiliency/troubleshooting/) -- [Dell Container Storage Module for Application Mobility](../../applicationmobility/troubleshooting/) -- [Dell Container Storage Module for Encryption](../../secure/encryption/troubleshooting/) - -### Can I use the CSM functionality like Prometheus collection or Authorization quotas for my non-Kubernetes storage clients? -No, all the modules have been designed to work inside Kubernetes with Dell CSI drivers. - -### Should I install the module in the same namespace as the driver or another? -It is recommended to install CSM for Observability in a namespace separate from the Dell CSI drivers because it works across multiple drivers. All other modules either run as standalone or with the Dell CSI driver as a sidecar. - -### Which Kubernetes distributions are supported? -The supported Kubernetes distributions for Container Storage Modules are documented: -- [Dell Container Storage Module for Authorization](../../authorization/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Observability](../../observability/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Replication](../../replication/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Resiliency](../../resiliency/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Application Mobility](../../applicationmobility/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Encryption](../../secure/encryption/#supported-operating-systemscontainer-orchestrator-platforms) - -The supported distros for the Dell CSI Drivers are located [here](../../csidriver/#supported-operating-systemscontainer-orchestrator-platforms). - -### How do I get a list of Container Storage Modules deployed in my cluster with their versions? -The easiest way to find the module version is to check the image tag for the module. For all the namespaces you can execute the following: -``` -kubectl get pods -A -o jsonpath="{..image}" | tr -s '[[:space:]]' '\n' | grep 'csm\|karavi' | sort | uniq -c -``` -Or if you know the namespace: -``` -kubectl get deployment,daemonset -o wide -n {{namespace}} -``` - -### Do all Container Storage Modules need to be the same version, or can I mix and match? -It is advised to comply with the support matrices (links below) and not deviate from it with mixed versions. -- [Dell Container Storage Module for Authorization](../../authorization/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Observability](../../observability/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Replication](../../replication/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Resiliency](../../resiliency/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Application Mobility](../../applicationmobility/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell Container Storage Module for Encryption](../../secure/encryption/#supported-operating-systemscontainer-orchestrator-platforms) -- [Dell CSI Drivers](../../csidriver/#supported-operating-systemscontainer-orchestrator-platforms). - -### Can I run Container Storage Modules in a production environment? - -Currently, the Container Storage Modules Authorization, Observability, Replication, and Resiliency are GA and ready for production systems. The modules Encryption and Application Mobility are launched for Tech Preview Release and it is not intended to use in the Production systems. - -### Is Dell Container Storage Modules (CSM) supported by Dell Technologies? -Yes! - -If you find an issue, please follow our [support process](../../support/) - -### Can I modify a module or contribute to the project? -Yes! - -All Container Storage Modules are released as open-source projects under Apache-2.0 License. You are free to contribute directly following the [contribution guidelines](https://github.com/dell/csm/blob/main/docs/CONTRIBUTING.md), fork the projects, modify them, and of course share feedback or open tickets ;-) - -### What is coming next? -This is just the beginning of the journey for Dell Container Storage Modules, and there is a full roadmap with more to come, which you can check under the [GitHub Milestones](https://github.com/dell/csm/milestones) page. diff --git a/content/docs/references/_index.md b/content/docs/references/_index.md deleted file mode 100644 index ce3be78438..0000000000 --- a/content/docs/references/_index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "References" -linkTitle: "References" -weight: 14 -Description: > - Dell Technologies (Dell) Container Storage Modules (CSM) References ---- diff --git a/content/docs/references/policies/_index.md b/content/docs/references/policies/_index.md deleted file mode 100644 index a5e2875d16..0000000000 --- a/content/docs/references/policies/_index.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -title: "Policies" -linkTitle: "Policies" -weight: 4 -Description: > - Dell Technologies (Dell) Container Storage Modules (CSM) Policies ---- diff --git a/content/docs/release/_index.md b/content/docs/release/_index.md deleted file mode 100644 index 248ba5ebae..0000000000 --- a/content/docs/release/_index.md +++ /dev/null @@ -1,27 +0,0 @@ ---- -title: "Release notes" -linkTitle: "Release notes" -weight: 12 -Description: > - Dell Container Storage Modules (CSM) release notes ---- - -Release notes for Container Storage Modules: - -[CSI Drivers](../csidriver/release) - -[CSM for Authorization](../authorization/release) - -[CSM for Observability](../observability/release) - -[CSM for Replication](../replication/release) - -[CSM for Resiliency](../resiliency/release) - -[CSM for Encryption](../secure/encryption/release) - -[CSM for Application Mobility](../applicationmobility/release) - -[CSM Operator](../deployment/csmoperator/release) - -[CSM Installation Wizard](../deployment/csminstallationwizard/release) diff --git a/content/docs/resiliency/_index.md b/content/docs/resiliency/_index.md index 8682218523..78fa586121 100644 --- a/content/docs/resiliency/_index.md +++ b/content/docs/resiliency/_index.md @@ -129,6 +129,8 @@ The following provisioning types are supported and have been tested: * Multiple instances of the same driver type (for example two CSI driver for Dell PowerFlex deployments.) +* PowerFlex with Resiliency is not supported for NFS protocol. + ## Deploying and Managing Applications Protected by CSM for Resiliency The first thing to remember about _CSM for Resiliency_ is that it only takes action on pods configured with the designated label. Both the key and the value have to match what is in the podmon helm configuration. CSM for Resiliency emits a log message at startup with the label key and value it is using to monitor pods: diff --git a/content/docs/secure/encryption/_index.md b/content/docs/secure/encryption/_index.md index 63d9a98e86..9a75bacee6 100644 --- a/content/docs/secure/encryption/_index.md +++ b/content/docs/secure/encryption/_index.md @@ -14,7 +14,7 @@ Encryption provides the capability to encrypt user data residing on volumes crea > **NOTE:** This tech-preview release is not intended for use in production environment. -> **NOTE:** Encryption requires a time-based license to create new encrypted volumes. Request a [trial license](../../license) prior to deployment. +> **NOTE:** Encryption requires a time-based license to create new encrypted volumes. Request a [trial license](../../support/license) prior to deployment. > > After the license expiration, existing encrypted volume can still be unlocked and used, but no new encrypted volumes can be created. diff --git a/content/docs/secure/encryption/troubleshooting.md b/content/docs/secure/encryption/troubleshooting.md index addc94b034..f19fbb1bbf 100644 --- a/content/docs/secure/encryption/troubleshooting.md +++ b/content/docs/secure/encryption/troubleshooting.md @@ -81,7 +81,7 @@ This may manifest in: - failure to create a new encrypted volume Resolution: -- obtain a [new valid license](../../../license) +- obtain a [new valid license](../../../support/license) - check the license is for the cluster on which the encrypted volumes are created - check [encryption-license secret](../../../deployment/helm/modules/installation/encryption#secret-encryption-license) diff --git a/content/docs/securitypolicy/_index.md b/content/docs/securitypolicy/_index.md deleted file mode 100644 index 06223eb64f..0000000000 --- a/content/docs/securitypolicy/_index.md +++ /dev/null @@ -1,15 +0,0 @@ ---- -title: "Security Policy" -linkTitle: "Security Policy" -weight: 13 -Description: > - Dell Container Storage Modules (CSM) Security Policy ---- - -# Reporting Security Issues/Vulnerabilities - -The Dell Container Storage Modules team and community take security bugs seriously. We sincerely appreciate all your efforts and responsibility to disclose your findings. - -To report a security issue, please submit the security advisory form ["Report a Vulnerability"](https://github.com/dell/csm/security/advisories/new). - ->CSM recommends staying on the [latest release](https://github.com/dell/csm/releases/latest) of Dell Container Storage Modules to take advantage of new features, enhancements, bug fixes, and security fixes. diff --git a/content/docs/support/_index.md b/content/docs/support/_index.md index 54535f32f8..1cea4e05c9 100644 --- a/content/docs/support/_index.md +++ b/content/docs/support/_index.md @@ -5,7 +5,19 @@ weight: 13 Description: > Dell Container Storage Modules (CSM) support --- - +### Where can I get support ? For all your support needs or to follow the latest ongoing discussions and updates, join our Slack group. Click [Here](http://del.ly/Slack_request) to request your invite. -You can also interact with us on [GitHub](https://github.com/dell/csm) by creating a [GitHub Issue](https://github.com/dell/csm/issues). \ No newline at end of file +You can also interact with us on [GitHub](https://github.com/dell/csm) by creating a [GitHub Issue](https://github.com/dell/csm/issues). + +If you have a support contract for a Dell Storage Backend that has a CSI Driver you can open a service request on [https://dell.com/support](https://dell.com/support) and select the **CSI Driver** product. + + +### How to report Security Issues or Vulnerabilities ? + +The Dell Container Storage Modules team and community take security bugs seriously. We sincerely appreciate all your efforts and responsibility to disclose your findings. + +To report a security issue, please submit the security advisory form ["Report a Vulnerability"](https://github.com/dell/csm/security/advisories/new). + +>CSM recommends staying on the [latest release](https://github.com/dell/csm/releases/latest) of Dell Container Storage Modules to take advantage of new features, enhancements, bug fixes, and security fixes. + diff --git a/content/docs/cert-csi/_index.md b/content/docs/support/cert-csi/_index.md similarity index 98% rename from content/docs/cert-csi/_index.md rename to content/docs/support/cert-csi/_index.md index d5993d4bce..f36ba596ac 100644 --- a/content/docs/cert-csi/_index.md +++ b/content/docs/support/cert-csi/_index.md @@ -1,7 +1,7 @@ --- title: Cert-CSI linktitle: Cert-CSI -weight: 13 +weight: 3 description: Tool to validate Dell CSI Drivers --- @@ -376,7 +376,7 @@ storageClasses: > NOTE: For testing/debugging purposes, it can be useful to use the `--no-cleanup` so resources do not get deleted. -> NOTE: If you are using CSI PowerScale with [SmartQuotas](../csidriver/features/powerscale/#usage-of-smartquotas-to-limit-storage-consumption) disabled, the `Volume Expansion` suite is expected to timeout due to the way PowerScale provisions storage. Set `storageClasses.expansion` to `false` to skip this suite. +> NOTE: If you are using CSI PowerScale with [SmartQuotas](../../csidriver/features/powerscale/#usage-of-smartquotas-to-limit-storage-consumption) disabled, the `Volume Expansion` suite is expected to timeout due to the way PowerScale provisions storage. Set `storageClasses.expansion` to `false` to skip this suite. ```bash cert-csi certify --cert-config --vsc @@ -533,7 +533,7 @@ Run `cert-csi test clone-volume -h` for more options. > Raw block volumes cannot be verified since there is no filesystem. -> If you are using CSI PowerScale with [SmartQuotas](../csidriver/features/powerscale/#usage-of-smartquotas-to-limit-storage-consumption) disabled, the `Volume Expansion` suite is expected to timeout due to the way PowerScale provisions storage. +> If you are using CSI PowerScale with [SmartQuotas](../../csidriver/features/powerscale/#usage-of-smartquotas-to-limit-storage-consumption) disabled, the `Volume Expansion` suite is expected to timeout due to the way PowerScale provisions storage. ```bash cert-csi test expansion --sc diff --git a/content/docs/cert-csi/img/HTMLReport.png b/content/docs/support/cert-csi/img/HTMLReport.png similarity index 100% rename from content/docs/cert-csi/img/HTMLReport.png rename to content/docs/support/cert-csi/img/HTMLReport.png diff --git a/content/docs/cert-csi/img/interruptTest.png b/content/docs/support/cert-csi/img/interruptTest.png similarity index 100% rename from content/docs/cert-csi/img/interruptTest.png rename to content/docs/support/cert-csi/img/interruptTest.png diff --git a/content/docs/cert-csi/img/listRuns.png b/content/docs/support/cert-csi/img/listRuns.png similarity index 100% rename from content/docs/cert-csi/img/listRuns.png rename to content/docs/support/cert-csi/img/listRuns.png diff --git a/content/docs/cert-csi/img/longevity.png b/content/docs/support/cert-csi/img/longevity.png similarity index 100% rename from content/docs/cert-csi/img/longevity.png rename to content/docs/support/cert-csi/img/longevity.png diff --git a/content/docs/cert-csi/img/multiDBTabularReport.png b/content/docs/support/cert-csi/img/multiDBTabularReport.png similarity index 100% rename from content/docs/cert-csi/img/multiDBTabularReport.png rename to content/docs/support/cert-csi/img/multiDBTabularReport.png diff --git a/content/docs/cert-csi/img/resourceUsage.png b/content/docs/support/cert-csi/img/resourceUsage.png similarity index 100% rename from content/docs/cert-csi/img/resourceUsage.png rename to content/docs/support/cert-csi/img/resourceUsage.png diff --git a/content/docs/cert-csi/img/scaling.PNG b/content/docs/support/cert-csi/img/scaling.PNG similarity index 100% rename from content/docs/cert-csi/img/scaling.PNG rename to content/docs/support/cert-csi/img/scaling.PNG diff --git a/content/docs/cert-csi/img/tabularReport.png b/content/docs/support/cert-csi/img/tabularReport.png similarity index 100% rename from content/docs/cert-csi/img/tabularReport.png rename to content/docs/support/cert-csi/img/tabularReport.png diff --git a/content/docs/cert-csi/img/textReport.png b/content/docs/support/cert-csi/img/textReport.png similarity index 100% rename from content/docs/cert-csi/img/textReport.png rename to content/docs/support/cert-csi/img/textReport.png diff --git a/content/docs/cert-csi/img/unifiedTest.png b/content/docs/support/cert-csi/img/unifiedTest.png similarity index 100% rename from content/docs/cert-csi/img/unifiedTest.png rename to content/docs/support/cert-csi/img/unifiedTest.png diff --git a/content/docs/cert-csi/qualified.md b/content/docs/support/cert-csi/qualified.md similarity index 100% rename from content/docs/cert-csi/qualified.md rename to content/docs/support/cert-csi/qualified.md diff --git a/content/docs/references/cli/_index.md b/content/docs/support/cli/_index.md similarity index 99% rename from content/docs/references/cli/_index.md rename to content/docs/support/cli/_index.md index f27b4925cf..d2dc3763e0 100644 --- a/content/docs/references/cli/_index.md +++ b/content/docs/support/cli/_index.md @@ -1,7 +1,7 @@ --- title: "CLI" linkTitle: "CLI" -weight: 1 +weight: 4 Description: > CLI for Dell Container Storage Modules (CSM) --- diff --git a/content/docs/references/contributionguidelines/_index.md b/content/docs/support/contributionguidelines/_index.md similarity index 99% rename from content/docs/references/contributionguidelines/_index.md rename to content/docs/support/contributionguidelines/_index.md index 427bd231af..633c8c6977 100644 --- a/content/docs/references/contributionguidelines/_index.md +++ b/content/docs/support/contributionguidelines/_index.md @@ -1,7 +1,7 @@ --- title: "Contribution Guidelines" linkTitle: "Contribution Guidelines" -weight: 3 +weight: 5 Description: > Dell Technologies (Dell) Container Storage Modules (CSM) docs Contribution Guidelines --- diff --git a/content/docs/references/policies/deprecationpolicy/_index.md b/content/docs/support/deprecationpolicy/_index.md similarity index 99% rename from content/docs/references/policies/deprecationpolicy/_index.md rename to content/docs/support/deprecationpolicy/_index.md index 19a4783ba1..c21a1d5fab 100644 --- a/content/docs/references/policies/deprecationpolicy/_index.md +++ b/content/docs/support/deprecationpolicy/_index.md @@ -1,7 +1,7 @@ --- title: "Deprecation Policy" linkTitle: "Deprecation Policy" -weight: 1 +weight: 4 Description: > Dell Technologies (Dell) Container Storage Modules (CSM) Deprecation Policy --- diff --git a/content/docs/references/learn/_index.md b/content/docs/support/learn/_index.md similarity index 95% rename from content/docs/references/learn/_index.md rename to content/docs/support/learn/_index.md index 51dcf458c4..482e079410 100644 --- a/content/docs/references/learn/_index.md +++ b/content/docs/support/learn/_index.md @@ -1,7 +1,7 @@ --- -title: Learn +title: Learn more about CSM Description: Blogs and Youtube videos for CSM -weight: 2 +weight: 7 --- You can learn more and engage with the CSM community over different channels by: * Reading the official [blogs](https://infohub.delltechnologies.com/t/blogs-99/) and [white paper](https://infohub.delltechnologies.com/t/persistent-storage-for-containerized-applications-on-kubernetes-with-powermax-san-storage-13/) are on [https://infohub.delltechnologies.com/](https://infohub.delltechnologies.com/) diff --git a/content/docs/license/_index.md b/content/docs/support/license/_index.md similarity index 94% rename from content/docs/license/_index.md rename to content/docs/support/license/_index.md index ec7bd9d734..c12954dba9 100644 --- a/content/docs/license/_index.md +++ b/content/docs/support/license/_index.md @@ -1,9 +1,9 @@ --- title: "License" linkTitle: "License" -weight: 12 +weight: 6 Description: > - Dell Container Storage Modules (CSM) License + Obtain trial License for Tech-preview of Dell Container Storage Modules (CSM) --- The tech-preview releases of [Container Storage Modules](https://github.com/dell/csm) for Application Mobility and Encryption require a license. This section details how to request a license. diff --git a/content/docs/support/release/_index.md b/content/docs/support/release/_index.md new file mode 100644 index 0000000000..e17a6c86f0 --- /dev/null +++ b/content/docs/support/release/_index.md @@ -0,0 +1,27 @@ +--- +title: "Release notes" +linkTitle: "Release notes" +weight: 1 +Description: > + Dell Container Storage Modules (CSM) release notes +--- + +Release notes for Container Storage Modules: + +[CSI Drivers](../../csidriver/release) + +[CSM for Authorization](../../authorization/release) + +[CSM for Observability](../../observability/release) + +[CSM for Replication](../../replication/release) + +[CSM for Resiliency](../../resiliency/release) + +[CSM for Encryption](../../secure/encryption/release) + +[CSM for Application Mobility](../../applicationmobility/release) + +[CSM Operator](../../deployment/csmoperator/release) + +[CSM Installation Wizard](../../deployment/csminstallationwizard/release) diff --git a/content/docs/support/troubleshooting/_index.md b/content/docs/support/troubleshooting/_index.md new file mode 100644 index 0000000000..c987433b32 --- /dev/null +++ b/content/docs/support/troubleshooting/_index.md @@ -0,0 +1,25 @@ +--- +title: "Troubleshooting" +linkTitle: "Troubleshooting" +weight: 2 +Description: > + Dell Container Storage Modules (CSM) troubleshooting information +--- + +Troubleshooting links for Container Storage Modules: + +[CSI Drivers](../../csidriver/troubleshooting) + +[CSM for Authorization](../../authorization/troubleshooting) + +[CSM for Observability](../../observability/troubleshooting) + +[CSM for Replication](../../replication/troubleshooting) + +[CSM for Resiliency](../../resiliency/troubleshooting) + +[CSM for Encryption](../../secure/encryption/troubleshooting) + +[CSM for Application Mobility](../../applicationmobility/troubleshooting) + +[CSM Operator](../../deployment/csmoperator/troubleshooting) \ No newline at end of file diff --git a/content/docs/troubleshooting/_index.md b/content/docs/troubleshooting/_index.md deleted file mode 100644 index 07e9260af6..0000000000 --- a/content/docs/troubleshooting/_index.md +++ /dev/null @@ -1,25 +0,0 @@ ---- -title: "Troubleshooting" -linkTitle: "Troubleshooting" -weight: 11 -Description: > - Dell Container Storage Modules (CSM) troubleshooting information ---- - -Troubleshooting links for Container Storage Modules: - -[CSI Drivers](../csidriver/troubleshooting) - -[CSM for Authorization](../authorization/troubleshooting) - -[CSM for Observability](../observability/troubleshooting) - -[CSM for Replication](../replication/troubleshooting) - -[CSM for Resiliency](../resiliency/troubleshooting) - -[CSM for Encryption](../secure/encryption/troubleshooting) - -[CSM for Application Mobility](../applicationmobility/troubleshooting) - -[CSM Operator](../deployment/csmoperator/troubleshooting) \ No newline at end of file diff --git a/content/v1/authorization/release/_index.md b/content/v1/authorization/release/_index.md index 3bcadd9408..07b4881533 100644 --- a/content/v1/authorization/release/_index.md +++ b/content/v1/authorization/release/_index.md @@ -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| diff --git a/content/v1/csidriver/release/powermax.md b/content/v1/csidriver/release/powermax.md index 2c5ccb9cd1..60bde1a5ad 100644 --- a/content/v1/csidriver/release/powermax.md +++ b/content/v1/csidriver/release/powermax.md @@ -43,6 +43,7 @@ description: Release notes for PowerMax CSI driver | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | | Automatic SRDF group creation is failing with "Unable to get Remote Port on SAN for Auto SRDF" for PowerMaxOS 10.1 arrays | Create the SRDF Group and add it to the storage class | | [Node stage is failing with error "wwn for FC device not found"](https://github.com/dell/csm/issues/1070)| This is an intermittent issue, rebooting the node will resolve this issue | +| When the driver is installed using CSM Operator , few times, pods created using block volume are getting stuck in containercreating/terminating state or devices are not available inside the pod. | Update the daemonset with parameter `mountPropagation: "Bidirectional"` for volumedevices-path under volumeMounts section.| ### 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. diff --git a/content/v1/deployment/csmoperator/release/_index.md b/content/v1/deployment/csmoperator/release/_index.md index a7c6b08e83..0efac132a7 100644 --- a/content/v1/deployment/csmoperator/release/_index.md +++ b/content/v1/deployment/csmoperator/release/_index.md @@ -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 `| +| 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 diff --git a/content/v1/resiliency/_index.md b/content/v1/resiliency/_index.md index a72b8b35b6..52711c75c6 100644 --- a/content/v1/resiliency/_index.md +++ b/content/v1/resiliency/_index.md @@ -129,6 +129,8 @@ The following provisioning types are supported and have been tested: * Multiple instances of the same driver type (for example two CSI driver for Dell PowerFlex deployments.) +* PowerFlex with Resiliency is not supported for NFS protocol. + ## Deploying and Managing Applications Protected by CSM for Resiliency The first thing to remember about _CSM for Resiliency_ is that it only takes action on pods configured with the designated label. Both the key and the value have to match what is in the podmon helm configuration. CSM for Resiliency emits a log message at startup with the label key and value it is using to monitor pods: diff --git a/content/v2/authorization/release/_index.md b/content/v2/authorization/release/_index.md index a64bec93ca..c2b85c06e0 100644 --- a/content/v2/authorization/release/_index.md +++ b/content/v2/authorization/release/_index.md @@ -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| diff --git a/content/v2/csidriver/release/powermax.md b/content/v2/csidriver/release/powermax.md index 4c4ca10a66..c6a29b8244 100644 --- a/content/v2/csidriver/release/powermax.md +++ b/content/v2/csidriver/release/powermax.md @@ -34,6 +34,7 @@ description: Release notes for PowerMax CSI driver | Unable to update Host: A problem occurred modifying the host resource | This issue occurs when the nodes do not have unique hostnames or when an IP address/FQDN with same sub-domains are used as hostnames. The workaround is to use unique hostnames or FQDN with unique sub-domains| | When a node goes down, the block volumes attached to the node cannot be attached to another node | This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround:
1. Force delete the pod running on the node that went down
2. Delete the volumeattachment to the node that went down.
Now the volume can be attached to the new node | | If the volume limit is exhausted and there are pending pods and PVCs due to `exceed max volume count`, the pending PVCs will be bound to PVs and the pending pods will be scheduled to nodes when the driver pods are restarted. | It is advised not to have any pending pods or PVCs once the volume limit per node is exhausted on a CSI Driver. There is an open issue reported with kubenetes at https://github.com/kubernetes/kubernetes/issues/95911 with the same behavior. | +| When the driver is installed using CSM Operator , few times, pods created using block volume are getting stuck in containercreating/terminating state or devices are not available inside the pod. | Update the daemonset with parameter `mountPropagation: "Bidirectional"` for volumedevices-path under volumeMounts section.| ### 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. diff --git a/content/v2/deployment/csmoperator/release/_index.md b/content/v2/deployment/csmoperator/release/_index.md index 5ac816b526..b5f331afa9 100644 --- a/content/v2/deployment/csmoperator/release/_index.md +++ b/content/v2/deployment/csmoperator/release/_index.md @@ -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. \ No newline at end of file +| 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| \ No newline at end of file diff --git a/content/v2/resiliency/_index.md b/content/v2/resiliency/_index.md index 246992cfe6..4ad6bb981f 100644 --- a/content/v2/resiliency/_index.md +++ b/content/v2/resiliency/_index.md @@ -131,6 +131,8 @@ The following provisioning types are supported and have been tested: * Multiple instances of the same driver type (for example two CSI driver for Dell PowerFlex deployments.) +* PowerFlex with Resiliency is not supported for NFS protocol. + ## Deploying and Managing Applications Protected by CSM for Resiliency The first thing to remember about _CSM for Resiliency_ is that it only takes action on pods configured with the designated label. Both the key and the value have to match what is in the podmon helm configuration. CSM for Resiliency emits a log message at startup with the label key and value it is using to monitor pods: diff --git a/content/v3/authorization/release/_index.md b/content/v3/authorization/release/_index.md index 5383614d75..3390a862c4 100644 --- a/content/v3/authorization/release/_index.md +++ b/content/v3/authorization/release/_index.md @@ -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| \ No newline at end of file diff --git a/content/v3/csidriver/release/powermax.md b/content/v3/csidriver/release/powermax.md index 7ec91a65c2..57a0ead4a2 100644 --- a/content/v3/csidriver/release/powermax.md +++ b/content/v3/csidriver/release/powermax.md @@ -31,6 +31,7 @@ There are no fixed issues in this release. |-------|------------| | Unable to update Host: A problem occurred modifying the host resource | This issue occurs when the nodes do not have unique hostnames or when an IP address/FQDN with same sub-domains are used as hostnames. The workaround is to use unique hostnames or FQDN with unique sub-domains| | When a node goes down, the block volumes attached to the node cannot be attached to another node | This is a known issue and has been reported at https://github.com/kubernetes-csi/external-attacher/issues/215. Workaround:
1. Force delete the pod running on the node that went down
2. Delete the volumeattachment to the node that went down.
Now the volume can be attached to the new node | +| When the driver is installed using CSM Operator , few times, pods created using block volume are getting stuck in containercreating/terminating state or devices are not available inside the pod. | Update the daemonset with parameter `mountPropagation: "Bidirectional"` for volumedevices-path under volumeMounts section.| ### Note: diff --git a/content/v3/deployment/csmoperator/release/_index.md b/content/v3/deployment/csmoperator/release/_index.md index 397664e60b..5278fedd50 100644 --- a/content/v3/deployment/csmoperator/release/_index.md +++ b/content/v3/deployment/csmoperator/release/_index.md @@ -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. \ No newline at end of file +| 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| \ No newline at end of file From 943c4161a9d4bc33cc9758eadd384152505922aa Mon Sep 17 00:00:00 2001 From: Aaron Tye Date: Tue, 28 May 2024 09:55:15 -0400 Subject: [PATCH 18/49] Add note for OCP support for CSM Authorization (#1104) * add note * Update _index.md --------- Co-authored-by: gallacher <35462391+gallacher@users.noreply.github.com> --- content/docs/prerequisites/_index.md | 1 + 1 file changed, 1 insertion(+) diff --git a/content/docs/prerequisites/_index.md b/content/docs/prerequisites/_index.md index 9411ece5b8..70f37aea4c 100644 --- a/content/docs/prerequisites/_index.md +++ b/content/docs/prerequisites/_index.md @@ -36,6 +36,7 @@ weight: 1 > Notes: > * Any orchestrator platform or version that's not mentioned here must be self-certified using [Cert-CSI](../support/cert-csi/) in order to be supported. Although not mandatory, we recommend users to use orchestrator platforms and versions that have not met their end of life. +> * CSM Authorization is not supported on Red Hat OpenShift. ## Tested Host Operating Systems From efa8d6c5e313c04396be6f62c5ff61152e3b9d61 Mon Sep 17 00:00:00 2001 From: gallacher <35462391+gallacher@users.noreply.github.com> Date: Tue, 28 May 2024 11:30:20 -0300 Subject: [PATCH 19/49] Update _index.md (#1114) --- content/docs/prerequisites/_index.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/content/docs/prerequisites/_index.md b/content/docs/prerequisites/_index.md index 70f37aea4c..4795ab4318 100644 --- a/content/docs/prerequisites/_index.md +++ b/content/docs/prerequisites/_index.md @@ -55,14 +55,13 @@ Container Storage Modules (CSM) does not officially support specific operating s {{}} | CSM Module | PowerMax | PowerFlex | Unity XT | PowerScale | PowerStore | |----------------------------------------|:--------:|:---------:|:--------:|:----------:|:----------:| -| [CSM Authorization](../authorization/) | Yes | Yes | Yes | Yes | No | +| [CSM Authorization](../authorization/) | Yes | Yes | No | Yes | No | | [CSM Observability](../observability/) | Yes | Yes | No | Yes | Yes | | [CSM Replication](../replication/) | Yes | Yes | No | Yes | Yes | | [CSM Resiliency](../resiliency/) | No | Yes | Yes | Yes | Yes | | [CSM Encryption](../secure/encryption/)| No | No | No | Yes | No | | [CSM Application Mobility](../applicationmobility/) | Yes | Yes | Yes | Yes | Yes | | [Volume Group Snapshot](../snapshots/volume-group-snapshots/) | No | Yes | No | No | Yes | - {{
}} > Notes: From b7a8f6b84ca7d30f593ae1028dd705f13fa08d6a Mon Sep 17 00:00:00 2001 From: Wilson Radadia <159131702+WilsonRadadia20@users.noreply.github.com> Date: Thu, 30 May 2024 15:28:44 +0530 Subject: [PATCH 20/49] Updated the release notes (#1128) --- content/docs/applicationmobility/release/_index.md | 2 +- content/docs/csidriver/release/powerflex.md | 4 ++-- content/docs/csidriver/release/powermax.md | 2 +- content/docs/csidriver/release/powerscale.md | 2 +- content/docs/csidriver/release/powerstore.md | 2 +- content/docs/csidriver/release/unity.md | 2 +- .../docs/deployment/csminstallationwizard/release/_index.md | 2 +- content/docs/deployment/csmoperator/release/_index.md | 2 +- content/docs/replication/release/_index.md | 2 +- 9 files changed, 10 insertions(+), 10 deletions(-) diff --git a/content/docs/applicationmobility/release/_index.md b/content/docs/applicationmobility/release/_index.md index b252668f77..69c92138a5 100644 --- a/content/docs/applicationmobility/release/_index.md +++ b/content/docs/applicationmobility/release/_index.md @@ -6,7 +6,7 @@ Description: > Release Notes --- -## Release Notes - CSM Application Mobility v1.0.2 +## Release Notes - CSM Application Mobility v1.0.4 ### New Features/Changes diff --git a/content/docs/csidriver/release/powerflex.md b/content/docs/csidriver/release/powerflex.md index 42425381bf..60f10f0b99 100644 --- a/content/docs/csidriver/release/powerflex.md +++ b/content/docs/csidriver/release/powerflex.md @@ -3,7 +3,7 @@ title: PowerFlex description: Release notes for PowerFlex CSI driver --- -## Release Notes - CSI PowerFlex v2.10.0 +## Release Notes - CSI PowerFlex v2.11.0 @@ -44,4 +44,4 @@ A CSI ephemeral pod may not get created in OpenShift 4.13 and fail with the erro ### Note: - Support for Kubernetes alpha features like Volume Health Monitoring 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`. +- 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.11.0`. diff --git a/content/docs/csidriver/release/powermax.md b/content/docs/csidriver/release/powermax.md index d117bc9503..7bbed8ee76 100644 --- a/content/docs/csidriver/release/powermax.md +++ b/content/docs/csidriver/release/powermax.md @@ -3,7 +3,7 @@ title: PowerMax description: Release notes for PowerMax CSI driver --- -## Release Notes - CSI PowerMax v2.10.0 +## Release Notes - CSI PowerMax v2.11.0 >Note: Auto SRDF group creation is currently not supported in PowerMaxOS 10.1 (6079) Arrays. diff --git a/content/docs/csidriver/release/powerscale.md b/content/docs/csidriver/release/powerscale.md index c16bd31c2a..3bc658c275 100644 --- a/content/docs/csidriver/release/powerscale.md +++ b/content/docs/csidriver/release/powerscale.md @@ -4,7 +4,7 @@ description: Release notes for PowerScale CSI driver --- -## Release Notes - CSI Driver for PowerScale v2.10.0 +## Release Notes - CSI Driver for PowerScale v2.11.0 diff --git a/content/docs/csidriver/release/powerstore.md b/content/docs/csidriver/release/powerstore.md index 7882b2c850..f9f8280ecd 100644 --- a/content/docs/csidriver/release/powerstore.md +++ b/content/docs/csidriver/release/powerstore.md @@ -3,7 +3,7 @@ title: PowerStore description: Release notes for PowerStore CSI driver --- -## Release Notes - CSI PowerStore v2.10.0 +## Release Notes - CSI PowerStore v2.11.0 diff --git a/content/docs/csidriver/release/unity.md b/content/docs/csidriver/release/unity.md index eb10d6451d..092e07f07b 100644 --- a/content/docs/csidriver/release/unity.md +++ b/content/docs/csidriver/release/unity.md @@ -3,7 +3,7 @@ title: Unity XT description: Release notes for Unity XT CSI driver --- -## Release Notes - CSI Unity XT v2.10.0 +## Release Notes - CSI Unity XT v2.11.0 diff --git a/content/docs/deployment/csminstallationwizard/release/_index.md b/content/docs/deployment/csminstallationwizard/release/_index.md index b78a9f9b7d..e3501247e6 100644 --- a/content/docs/deployment/csminstallationwizard/release/_index.md +++ b/content/docs/deployment/csminstallationwizard/release/_index.md @@ -5,7 +5,7 @@ weight: 5 description: Release notes for CSM Installation Wizard --- -## Release Notes - CSM Installation Wizard 1.2.1 +## Release Notes - CSM Installation Wizard 1.3.0 diff --git a/content/docs/deployment/csmoperator/release/_index.md b/content/docs/deployment/csmoperator/release/_index.md index 5803fd15c0..e0708ad2bf 100644 --- a/content/docs/deployment/csmoperator/release/_index.md +++ b/content/docs/deployment/csmoperator/release/_index.md @@ -6,7 +6,7 @@ Description: > Release notes for Dell Container Storage Modules Operator --- -## Release Notes - Container Storage Modules Operator v1.5.0 +## Release Notes - Container Storage Modules Operator v1.6.0 diff --git a/content/docs/replication/release/_index.md b/content/docs/replication/release/_index.md index 4f9937bb33..f29ceb3fa4 100644 --- a/content/docs/replication/release/_index.md +++ b/content/docs/replication/release/_index.md @@ -6,7 +6,7 @@ Description: > Dell Container Storage Modules (CSM) release notes for replication --- -## Release Notes - CSM Replication 1.7.1 +## Release Notes - CSM Replication 1.9.0 From 45cfcdb6159158441bc006879dc4541fd2666439 Mon Sep 17 00:00:00 2001 From: delldubey Date: Mon, 3 Jun 2024 15:47:47 +0530 Subject: [PATCH 21/49] Update Resiliency support for pmax in Helm and Operator (#1130) Signed-off-by: Utkarsh Dubey --- .../csmoperator/modules/resiliency.md | 8 +++++ .../modules/installation/resiliency/_index.md | 34 +++++++++++++++++++ content/docs/prerequisites/_index.md | 6 ++-- content/docs/resiliency/_index.md | 25 ++++++++++---- 4 files changed, 63 insertions(+), 10 deletions(-) diff --git a/content/docs/deployment/csmoperator/modules/resiliency.md b/content/docs/deployment/csmoperator/modules/resiliency.md index 421cdcef42..349e61782d 100644 --- a/content/docs/deployment/csmoperator/modules/resiliency.md +++ b/content/docs/deployment/csmoperator/modules/resiliency.md @@ -18,6 +18,14 @@ When utilizing CSM for Resiliency module, it is crucial to note that it will sol ```bash kubectl get pods -A -l podmon.dellemc.com/driver=csi-vxflexos ``` +Similarly, labels for for csi-powerscale, csi-unity, csi-powerstore and csi-powermax would be as: + ```bash + podmon.dellemc.com/driver:csi-isilon + podmon.dellemc.com/driver:csi-unity + podmon.dellemc.com/driver:csi-powerstore + podmon.dellemc.com/driver:csi-powermax +``` + ``` NAMESPACE NAME READY STATUS RESTARTS AGE pmtu1 podmontest-0 1/1 Running 0 3m7s diff --git a/content/docs/deployment/helm/modules/installation/resiliency/_index.md b/content/docs/deployment/helm/modules/installation/resiliency/_index.md index 005c23c7b8..8d8f926ce8 100644 --- a/content/docs/deployment/helm/modules/installation/resiliency/_index.md +++ b/content/docs/deployment/helm/modules/installation/resiliency/_index.md @@ -16,6 +16,8 @@ For information on the PowerScale CSI driver, see [PowerScale CSI Driver](https: For information on the PowerStore CSI driver, see [PowerStore CSI Driver](https://github.com/dell/csi-powerstore). +For information on the PowerStore CSI driver, see [PowerMax CSI Driver](https://github.com/dell/csi-powermax). + Configure all the helm chart parameters described below before installing the drivers. ## Helm Chart Installation @@ -194,6 +196,38 @@ podmon: - "--ignoreVolumelessPods=false" ``` +## PowerMax Specific Recommendations + +Here is a typical installation used for testing: + +```yaml +podmon: + enabled: false + controller: + args: + - "--csisock=unix:/var/run/csi/csi.sock" + - "--labelvalue=csi-powermax" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powermax.dellemc.com" + - "--mode=controller" + - "--skipArrayConnectionValidation=false" + - "--driver-config-params=/powermax-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" + + node: + args: + - "--csisock=unix:/var/lib/kubelet/plugins/powermax.emc.dell.com/csi_sock" + - "--labelvalue=csi-powermax" + - "--arrayConnectivityPollRate=60" + - "--driverPath=csi-powermax.dellemc.com" + - "--mode=node" + - "--leaderelection=false" + - "--driver-config-params=/powermax-config-params/driver-config-params.yaml" + - "--driverPodLabelValue=dell-storage" + - "--ignoreVolumelessPods=false" +``` + ## Dynamic parameters CSM for Resiliency has configuration parameters that can be updated dynamically, such as the logging level and format. This can be diff --git a/content/docs/prerequisites/_index.md b/content/docs/prerequisites/_index.md index 4795ab4318..b323a3456a 100644 --- a/content/docs/prerequisites/_index.md +++ b/content/docs/prerequisites/_index.md @@ -58,7 +58,7 @@ Container Storage Modules (CSM) does not officially support specific operating s | [CSM Authorization](../authorization/) | Yes | Yes | No | Yes | No | | [CSM Observability](../observability/) | Yes | Yes | No | Yes | Yes | | [CSM Replication](../replication/) | Yes | Yes | No | Yes | Yes | -| [CSM Resiliency](../resiliency/) | No | Yes | Yes | Yes | Yes | +| [CSM Resiliency](../resiliency/) | Yes | Yes | Yes | Yes | Yes | | [CSM Encryption](../secure/encryption/)| No | No | No | Yes | No | | [CSM Application Mobility](../applicationmobility/) | Yes | Yes | Yes | Yes | Yes | | [Volume Group Snapshot](../snapshots/volume-group-snapshots/) | No | Yes | No | No | Yes | @@ -82,9 +82,9 @@ The table below lists the driver and modules versions installable with the CSM O | CSI PowerStore | 2.10.0 | ❌ | ❌ | ❌ | ✔ 1.9.0 | | CSI PowerStore | 2.9.0 | ❌ | ❌ | ❌ | ✔ 1.8.0 | | CSI PowerStore | 2.8.0 | ❌ | ❌ | ❌ | ✔ 1.7.0 | -| CSI PowerMax | 2.10.0 | ✔ 1.10.0 | ✔ 1.8.0 | ✔ 1.8.0 | ❌ | +| CSI PowerMax | 2.11.0 | ✔ 1.11.0 | ✔ 1.9.0 | ✔ 1.9.0 | ✔ 1.10.0 | +| CSI PowerMax | 2.10.1 | ✔ 1.10.1 | ✔ 1.8.1 | ✔ 1.8.1 | ❌ | | CSI PowerMax | 2.9.0 | ✔ 1.9.0 | ✔ 1.7.0 | ✔ 1.7.0 | ❌ | -| CSI PowerMax | 2.8.0 | ✔ 1.8.0 | ✔ 1.6.0 | ✔ 1.6.0 | ❌ | | CSI Unity XT | 2.10.0 | ❌ | ❌ | ❌ | ❌ | | CSI Unity XT | 2.9.0 | ❌ | ❌ | ❌ | ❌ | | CSI Unity XT | 2.8.0 | ❌ | ❌ | ❌ | ❌ | diff --git a/content/docs/resiliency/_index.md b/content/docs/resiliency/_index.md index 78fa586121..f9d86c95ab 100644 --- a/content/docs/resiliency/_index.md +++ b/content/docs/resiliency/_index.md @@ -31,9 +31,9 @@ CSM for Resiliency provides the following capabilities: {{}} | Capability | PowerScale | Unity XT | PowerStore | PowerFlex | PowerMax | | --------------------------------------- | :--------: | :------: | :--------: | :-------: | :------: | -| Detect pod failures when: Node failure, K8S Control Plane Network failure, K8S Control Plane failure, Array I/O Network failure | yes | yes | yes | yes | no | -| Cleanup pod artifacts from failed nodes | yes | yes | yes | yes | no | -| Revoke PV access from failed nodes | yes | yes | yes | yes | no | +| Detect pod failures when: Node failure, K8S Control Plane Network failure, K8S Control Plane failure, Array I/O Network failure | yes | yes | yes | yes | yes | +| Cleanup pod artifacts from failed nodes | yes | yes | yes | yes | yes | +| Revoke PV access from failed nodes | yes | yes | yes | yes | yes | {{
}} ## Supported Operating Systems/Container Orchestrator Platforms @@ -48,9 +48,9 @@ CSM for Resiliency provides the following capabilities: ## Supported Storage Platforms {{}} -| | PowerFlex | Unity XT | PowerScale | PowerStore | -| ------------- | :----------: | :-------------------------------: | :-------------------------------------: | :---------------------------: | -| Storage Array | 3.6.x, 4.0.x, 4.5 | 5.1.x, 5.2.x, 5.3.0 | OneFS 9.3, 9.4, 9.5.0.x (x >= 5) | 3.0, 3.2, 3.5, 3.6 | +| | PowerFlex | Unity XT | PowerScale | PowerStore | PowerMax | +| ------------- | :----------: | :-------------------------------: | :-------------------------------------: | :---------------------------: | :---------------------------: | +| Storage Array | 3.6.x, 4.0.x, 4.5 | 5.1.x, 5.2.x, 5.3.0 | OneFS 9.3, 9.4, 9.5.0.x (x >= 5) | 3.0, 3.2, 3.5, 3.6 | 2500/8500 PowerMax OS 10 (6079), Unisphere 10.x | {{
}} ## Supported CSI Drivers @@ -63,6 +63,7 @@ CSM for Resiliency supports the following CSI drivers and versions. | CSI Driver for Dell Unity XT | [csi-unity](https://github.com/dell/csi-unity) | v2.0.0 + | | CSI Driver for Dell PowerScale | [csi-powerscale](https://github.com/dell/csi-powerscale) | v2.3.0 + | | CSI Driver for Dell PowerStore | [csi-powerstore](https://github.com/dell/csi-powerstore) | v2.6.0 + | +| CSI Driver for Dell PowerMax | [csi-powermax](https://github.com/dell/csi-powermax) | v2.11.0 + | {{}} ### PowerFlex Support @@ -102,6 +103,14 @@ PowerStore is a highly scalable array that is very well suited to Kubernetes dep * A robust mechanism to detect if Nodes are actively doing I/O to volumes. * Low latency REST API supports fast CSI provisioning and de-provisioning operations. +### PowerMax Support + +PowerMax is the highest performing block storage array that is very well suited to Kubernetes deployments. The CSM for Resiliency support for PowerMax leverages the following PowerMax features: + +* Detection of Array I/O Network Connectivity status changes. +* A robust mechanism to detect if Nodes are actively doing I/O to volumes. +* Low latency REST API supports fast CSI provisioning and de-provisioning operations. + ## Limitations and Exclusions This file contains information on Limitations and Exclusions that users should be aware of. Additionally, there are driver specific limitations and exclusions that may be called out in the [Deploying CSM for Resiliency](../deployment/helm/modules/installation/resiliency/) page. @@ -161,10 +170,12 @@ 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 shown respectively. +Similarly, the label selector for csi-powerscale, csi-unity, csi-powerstore and csi-powermax would be as shown respectively. ```yaml labelSelector: {map[podmon.dellemc.com/driver:csi-isilon] labelSelector: {map[podmon.dellemc.com/driver:csi-unity] + labelSelector: {map[podmon.dellemc.com/driver:csi-powerstore] + labelSelector: {map[podmon.dellemc.com/driver:csi-powermax] ``` #### Important From 9dbbc5f765bfc26a23b096e2715502ce1161a362 Mon Sep 17 00:00:00 2001 From: Chiman Jain <36687396+chimanjain@users.noreply.github.com> Date: Wed, 5 Jun 2024 16:06:03 +0530 Subject: [PATCH 22/49] Add observability upgrade support documentation (#1134) * add documentation for obs upgrade * update notes for observability upgrade * fix link --- content/docs/deployment/csmoperator/_index.md | 41 +++++++++++++++++++ .../csmoperator/modules/observability.md | 14 +++++-- 2 files changed, 51 insertions(+), 4 deletions(-) diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md index f58e26a11c..fb482693af 100644 --- a/content/docs/deployment/csmoperator/_index.md +++ b/content/docs/deployment/csmoperator/_index.md @@ -363,6 +363,47 @@ The following notes explain some of the general items to take care of. configVersion: v2.10.0 ``` +### Upgrade Observability module using Dell CSM Operator + +The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource. + +* Modifying the existing driver and module installation directly via `kubectl edit` + + ```sh + $ kubectl get -n + ``` + + For example - If the CSI PowerScale driver is installed then run this command to get the object name + + ```sh + # Replace driver-namespace with the namespace where the CSI PowerScale driver is installed + $ kubectl get csm -n + ``` + + use the object name in `kubectl edit` command. + + ```sh + $ kubectl edit csm / -n + ``` + + For example - If the object name is isilon then use the name as isilon + + ```sh + # Replace object-name with the isilon + $ kubectl edit csm isilon -n + ``` + +* Modify the installation + + * Update the driver config version and image tag + + * Update the Observability config version, csm-topology image and the driver metrics images(e.g. for CSI PowerScale driver, the metrics driver image would be `csm-metrics-powerscale`) + +>NOTE: + +* In observability module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current observability version is `v1.7.x`, it can be upgraded to `1.8.x`. +* Upgrade to csm-operator and csi-driver first which support the corresponding observability module version. + ## Custom Resource Definitions As part of the Dell CSM Operator installation, a CRD representing configuration for the CSI Driver and CSM Modules is also installed. `containerstoragemodule` CRD is installed in API Group `storage.dell.com`. diff --git a/content/docs/deployment/csmoperator/modules/observability.md b/content/docs/deployment/csmoperator/modules/observability.md index 1e2dd58e5d..c26586255a 100644 --- a/content/docs/deployment/csmoperator/modules/observability.md +++ b/content/docs/deployment/csmoperator/modules/observability.md @@ -10,13 +10,16 @@ The CSM Observability module for supported Dell CSI Drivers can be installed via ## Prerequisites - Create a namespace `karavi` + ```bash kubectl create namespace karavi ``` + - Enable Observability module and components in [sample manifests](https://github.com/dell/csm-operator/tree/main/samples). If cert-manager has already been installed, don't enable it. - To use Observablity with CSM Authorization, the [Authorization Proxy Server](../authorization/) should be installed and configured first. Then, enable the Authorization module along with the Observability module in the sample manifest. - Observability will deploy with self-signed certificates by default. If you want to have custom certificates created instead, please generate certificates and private keys, encode them in base64, and insert them into the sample file as shown below for whichever components you are enabling: -``` + +```yaml # observability: allows to configure observability - name: observability ... @@ -44,13 +47,16 @@ The CSM Observability module for supported Dell CSI Drivers can be installed via privateKey: "" ... ``` + - Notes: - - If you enable `metrics-powerscale` or `metrics-powerflex`, you must enable `otel-collector` as well. - - otel-collector cannot be enabled without a metrics component also enabled. - - If you are deploying multiple drivers, only enable topology, otel-collector, and cert-manager in the first driver. For subsequent drivers, only enable the metrics component. When deleting the deployment, the driver that was created first must be deleted last. + - If you enable `metrics-powerscale` or `metrics-powerflex`, you must enable `otel-collector` as well. + - otel-collector cannot be enabled without a metrics component also enabled. + - If you are deploying multiple drivers, only enable topology, otel-collector, and cert-manager in the first driver. For subsequent drivers, only enable the metrics component. When deleting the deployment, the driver that was created first must be deleted last. ## Install Observability - Once you have prepared the sample file(s) (one per driver being installed), deploy by running `kubectl apply -f ` on the sample file. +## Upgrade Observability +- To upgrade observability module, please check the following section: [Upgrade Observability module using Dell CSM Operator](../../#upgrade-observability-module-using-dell-csm-operator) From 94ef14eb9184adb2f0c56767eb5b35f3763afb3e Mon Sep 17 00:00:00 2001 From: Rishabh Raj <120644626+rishabhatdell@users.noreply.github.com> Date: Fri, 7 Jun 2024 17:00:49 +0530 Subject: [PATCH 23/49] Updated templates for CSM 1.11 (#1129) * Updated templates for CSM 1.11 * fix unit tests * fix helm chart versions * fixed unit tests * updated hel charts version --- config.toml | 2 +- .../csm-versions/default-values.properties | 2 +- .../csminstallationwizard/src/index.html | 8 +- .../src/static/js/constants.js | 6 +- .../src/static/js/tests/generate-yaml.test.js | 6 +- .../src/static/js/tests/ui-functions.test.js | 10 +-- .../src/static/js/tests/utility.test.js | 6 +- .../src/static/js/ui-functions.js | 16 ++-- .../templates/helm/csm-1.11.0-values.template | 76 +++++++++---------- .../operator/csm-isilon-1.11.0.template | 20 ++--- .../operator/csm-powermax-1.11.0.template | 14 ++-- .../operator/csm-powerstore-1.11.0.template | 6 +- 12 files changed, 86 insertions(+), 86 deletions(-) diff --git a/config.toml b/config.toml index ad977d6d2a..919f68ed82 100644 --- a/config.toml +++ b/config.toml @@ -176,7 +176,7 @@ enable = false url = "https://dell.github.io/csm-docs/docs/" [[params.versions]] - version = "v1.10.0" + version = "v1.10.2" url = "https://dell.github.io/csm-docs/v1" [[params.versions]] diff --git a/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties b/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties index 61fd4afa52..7ec130a487 100644 --- a/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties +++ b/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties @@ -1,4 +1,4 @@ -csmVersion=1.10.1 +csmVersion=1.11.0 imageRepository=dellemc controllerCount=1 nodeSelectorLabel=node-role.kubernetes.io/control-plane: diff --git a/content/docs/deployment/csminstallationwizard/src/index.html b/content/docs/deployment/csminstallationwizard/src/index.html index 6cebdb07d0..df2597bfd4 100644 --- a/content/docs/deployment/csminstallationwizard/src/index.html +++ b/content/docs/deployment/csminstallationwizard/src/index.html @@ -90,10 +90,10 @@
diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js index b4975024fd..c11ae18901 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js @@ -40,10 +40,10 @@ const CONSTANTS = { PROPERTIES: ".properties", HELM: "helm", OPERATOR: "operator", - CSM_HELM_V170: "1.0.0", CSM_HELM_V180: "1.1.0", - CSM_HELM_V190: "1.2.1", - CSM_HELM_V1101: "1.3.1", + CSM_HELM_V190: "1.2.2", + CSM_HELM_V1102: "1.3.2", + CSM_HELM_V1110: "1.4.0", HELM_TAINTS: ` - key: "$KEY" operator: "Exists" diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js b/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js index d3f86ca24f..44164efc64 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js @@ -42,10 +42,10 @@ const CONSTANTS = { PROPERTIES: ".properties", HELM: "helm", OPERATOR: "operator", - CSM_HELM_V170: "1.0.0", CSM_HELM_V180: "1.1.0", - CSM_HELM_V190: "1.2.0", - CSM_HELM_V1100: "1.3.0", + CSM_HELM_V190: "1.2.2", + CSM_HELM_V1102: "1.3.2", + CSM_HELM_V1110: "1.4.0", HELM_TAINTS: ` - key: "$KEY" operator: "Exists" diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js b/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js index eb6e90a452..d4096b888c 100644 --- a/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js +++ b/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js @@ -68,10 +68,10 @@ const CONSTANTS = { PROPERTIES: ".properties", HELM: "helm", OPERATOR: "operator", - CSM_HELM_V170: "1.0.0", CSM_HELM_V180: "1.1.0", - CSM_HELM_V190: "1.2.0", - CSM_HELM_V1100: "1.3.0", + CSM_HELM_V190: "1.2.2", + CSM_HELM_V1102: "1.3.2", + CSM_HELM_V1110: "1.4.0", }; describe("GIVEN onAuthorizationChange function", () => { @@ -718,7 +718,7 @@ describe("GIVEN displayCommands function", () => { - +