diff --git a/content/docs/csidriver/_index.md b/content/docs/csidriver/_index.md
index 31bf3ed257..df58b92e63 100644
--- a/content/docs/csidriver/_index.md
+++ b/content/docs/csidriver/_index.md
@@ -41,7 +41,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
|---------------|:----------------:|:------------------:|:----------------:|:----------------:|:----------------:|
| Fibre Channel | yes | N/A | yes | N/A | yes |
| iSCSI | yes | N/A | yes | N/A | yes |
-| NVMeTCP | N/A | N/A | N/A | N/A | yes |
+| NVMeTCP | yes | N/A | N/A | N/A | yes |
| NVMeFC | N/A | N/A | N/A | N/A | yes |
| NFS | yes - SDNAS only (not eNAS) | yes | yes | yes | yes |
| Other | N/A | ScaleIO protocol | N/A | N/A | N/A |
@@ -50,3 +50,4 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
| Platform-specific configurable settings | Service Level selection
iSCSI CHAP | - | Host IO Limit
Tiering Policy
NFS Host IO size
Snapshot Retention duration | Access Zone
NFS version (3 or 4);Configurable Export IPs | iSCSI CHAP |
| Auto RDM(vSphere) | Yes(over FC) | N/A | N/A | N/A | N/A |
{{}}
+
diff --git a/content/docs/csidriver/features/powermax.md b/content/docs/csidriver/features/powermax.md
index be4d00bab7..a4a374541e 100644
--- a/content/docs/csidriver/features/powermax.md
+++ b/content/docs/csidriver/features/powermax.md
@@ -636,3 +636,13 @@ This feature is also supported for limiting the volume provisioning on Kubernete
>**NOTE:**
The default value of `maxPowerMaxVolumesPerNode` is 0.
If `maxPowerMaxVolumesPerNode` is set to zero, then CO shall decide how many volumes of this type can be published by the controller to the node.
The volume limit specified to `maxPowerMaxVolumesPerNode` attribute is applicable to all the nodes in the cluster for which node label `max-powermax-volumes-per-node` is not set.
Supported maximum number of RDM Volumes per VM is 60 as per the limitations.
If the value is set both by node label and values.yaml file then node label value will get the precedence and user has to remove the node label in order to reflect the values.yaml value.
+## NVMe/TCP Support
+
+The CSI Driver for Dell PowerMax supports NVMeTCP from v2.11.0. To enable NVMe/TCP provisioning, blockProtocol in settings file should be specified as NVMETCP.
+
+**Limitations**
+These are the CSM modules not supported with NVMeTCP protocol:
+- CSM Authorization
+- CSM Observability
+- CSM Application Mobility
+- Metro Replication
\ No newline at end of file
diff --git a/content/docs/deployment/csmoperator/drivers/powermax.md b/content/docs/deployment/csmoperator/drivers/powermax.md
index 4d3f5dffa9..c9327f60cf 100644
--- a/content/docs/deployment/csmoperator/drivers/powermax.md
+++ b/content/docs/deployment/csmoperator/drivers/powermax.md
@@ -15,6 +15,7 @@ The CSI Driver for Dell PowerMax can create PVC with different storage protocols
* direct Fiber Channel
* direct iSCSI
* NFS
+* NVMeTCP
* Fiber Channel via VMware Raw Device Mapping
In most cases, you will use one protocol only; therefore you should comply with the according prerequisites and not the others.
@@ -33,6 +34,24 @@ CSI Driver for Dell PowerMax supports Fibre Channel communication. Ensure that t
- Ensure that the HBA WWNs (initiators) appear on the list of initiators that are logged into the array.
- If the number of volumes that will be published to nodes is high, then configure the maximum number of LUNs for your HBAs on each node. See the appropriate HBA document to configure the maximum number of LUNs.
+### NVMeTCP requirements
+If you want to use the protocol, set up the NVMe initiators as follows:
+- Setup on Array
+ - When creating the NVMe endpoints, update the endpoint name as ```>```
+- Setup on Host
+ - The driver requires NVMe management command-line interface (nvme-cli) to use configure, edit, view or start the NVMe client and target. The nvme-cli utility provides a command-line and interactive shell option. The NVMe CLI tool is installed in the host using the below command.
+```bash
+sudo apt install nvme-cli
+```
+**Requirements for NVMeTCP**
+- Modules including the nvme, nvme_core, nvme_fabrics, and nvme_tcp are required for using NVMe over Fabrics using TCP. Load the NVMe and NVMe-OF Modules using the below commands:
+```bash
+modprobe nvme
+modprobe nvme_tcp
+```
+- The NVMe modules may not be available after a node reboot. Loading the modules at startup is recommended.
+- Generate and update the _/etc/nvme/hostnqn_ with hostNQN details.
+
### iSCSI Requirements
The CSI Driver for Dell PowerMax supports iSCSI connectivity. These requirements are applicable for the nodes that use iSCSI initiator to connect to the PowerMax arrays.
diff --git a/content/docs/deployment/helm/drivers/installation/powermax.md b/content/docs/deployment/helm/drivers/installation/powermax.md
index 43faee391d..15c447c90e 100644
--- a/content/docs/deployment/helm/drivers/installation/powermax.md
+++ b/content/docs/deployment/helm/drivers/installation/powermax.md
@@ -15,6 +15,7 @@ The following requirements must be met before installing CSI Driver for Dell Pow
- Fibre Channel requirements
- iSCSI requirements
- NFS requirements
+- NVMeTCP requirements
- Auto RDM for vSphere over FC requirements
- Certificate validation for Unisphere REST API calls
- Mount propagation is enabled on container runtime that is being used
@@ -81,6 +82,24 @@ CSI Driver for Dell PowerMax supports NFS communication. Ensure that the followi
- PowerMax Embedded Management guest to access Unisphere for PowerMax.
- Create the NAS server. Please refer [here](https://dl.dell.com/content/manual55638050-dell-powermax-file-quick-start-guide.pdf?language=en-us&ps=true) for more details.
+### NVMeTCP requirements
+If you want to use the protocol, set up the NVMe initiators as follows:
+- Setup on Array
+ - When creating the NVMe endpoints, update the endpoint name as ```>```
+- Setup on Host
+ - The driver requires NVMe management command-line interface (nvme-cli) to use configure, edit, view or start the NVMe client and target. The nvme-cli utility provides a command-line and interactive shell option. The NVMe CLI tool is installed in the host using the below command.
+```bash
+sudo apt install nvme-cli
+```
+**Requirements for NVMeTCP**
+- Modules including the nvme, nvme_core, nvme_fabrics, and nvme_tcp are required for using NVMe over Fabrics using TCP. Load the NVMe and NVMe-OF Modules using the below commands:
+```bash
+modprobe nvme
+modprobe nvme_tcp
+```
+- The NVMe modules may not be available after a node reboot. Loading the modules at startup is recommended.
+- Generate and update the _/etc/nvme/hostnqn_ with hostNQN details.
+
### Auto RDM for vSphere over FC requirements
The CSI Driver for Dell PowerMax supports auto RDM for vSphere over FC. These requirements are applicable for the clusters deployed on ESX/ESXi using virtualized environement.
@@ -261,87 +280,87 @@ CRDs should be configured during replication prepare stage with repctl as descri
vi my-powermax-settings.yaml
```
-| Parameter | Description | Required | Default |
-|-----------|--------------|------------|----------|
-| **global**| This section refers to configuration options for both CSI PowerMax Driver and Reverse Proxy | - | - |
-|defaultCredentialsSecret| This secret name refers to:
1 The proxy credentials if the driver is installed with proxy in StandAlone mode.
2. The default Unisphere credentials if credentialsSecret is not specified for a management server.| Yes | powermax-creds |
-| storageArrays| This section refers to the list of arrays managed by the driver and Reverse Proxy in StandAlone mode.| - | - |
-| storageArrayId | This refers to PowerMax Symmetrix ID.| Yes | 000000000001|
-| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes if Reverse Proxy mode is _StandAlone_ | https://primary-1.unisphe.re:8443 |
-| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on| Yes | https://backup-1.unisphe.re:8443 |
-| managementServers | This section refers to the list of configurations for Unisphere servers managing powermax arrays.| - | - |
-| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://primary-1.unisphe.re:8443 |
-| credentialsSecret| This refers to the user credentials for _endpoint_ | Yes| primary-1-secret|
-| skipCertificateValidation | This parameter should be set to false if you want to do client-side TLS verification of Unisphere for PowerMax SSL certificates.| No | "True" |
-| certSecret | The name of the secret in the same namespace containing the CA certificates of the Unisphere server | Yes, if skipCertificateValidation is set to false | Empty|
-| limits | This refers to various limits for Reverse Proxy | No | - |
-| maxActiveRead | This refers to the maximum concurrent READ request handled by the reverse proxy.| No | 5 |
-| maxActiveWrite | This refers to the maximum concurrent WRITE request handled by the reverse proxy.| No | 4 |
-| maxOutStandingRead | This refers to maximum queued READ request when reverse proxy receives more than _maxActiveRead_ requests. | No | 50 |
-| maxOutStandingWrite| This refers to maximum queued WRITE request when reverse proxy receives more than _maxActiveWrite_ requests.| No | 50 |
-| kubeletConfigDir | Specify kubelet config dir path | Yes | /var/lib/kubelet |
-| imagePullPolicy | The default pull policy is IfNotPresent which causes the Kubelet to skip pulling an image if it already exists. | Yes | IfNotPresent |
+| Parameter | Description | Required | Default |
+|-----------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|------------|----------|
+| **global**| This section refers to configuration options for both CSI PowerMax Driver and Reverse Proxy | - | - |
+|defaultCredentialsSecret| This secret name refers to:
1 The proxy credentials if the driver is installed with proxy in StandAlone mode.
2. The default Unisphere credentials if credentialsSecret is not specified for a management server. | Yes | powermax-creds |
+| storageArrays| This section refers to the list of arrays managed by the driver and Reverse Proxy in StandAlone mode. | - | - |
+| storageArrayId | This refers to PowerMax Symmetrix ID. | Yes | 000000000001|
+| endpoint | This refers to the URL of the Unisphere server managing _storageArrayId_. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes if Reverse Proxy mode is _StandAlone_ | https://primary-1.unisphe.re:8443 |
+| backupEndpoint | This refers to the URL of the backup Unisphere server managing _storageArrayId_, if Reverse Proxy is installed in _StandAlone_ mode. If authorization is enabled, backupEndpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://backup-1.unisphe.re:8443 |
+| managementServers | This section refers to the list of configurations for Unisphere servers managing powermax arrays. | - | - |
+| endpoint | This refers to the URL of the Unisphere server. If authorization is enabled, endpoint should be the HTTPS localhost endpoint that the authorization sidecar will listen on | Yes | https://primary-1.unisphe.re:8443 |
+| credentialsSecret| This refers to the user credentials for _endpoint_ | Yes| primary-1-secret|
+| skipCertificateValidation | This parameter should be set to false if you want to do client-side TLS verification of Unisphere for PowerMax SSL certificates. | No | "True" |
+| certSecret | The name of the secret in the same namespace containing the CA certificates of the Unisphere server | Yes, if skipCertificateValidation is set to false | Empty|
+| limits | This refers to various limits for Reverse Proxy | No | - |
+| maxActiveRead | This refers to the maximum concurrent READ request handled by the reverse proxy. | No | 5 |
+| maxActiveWrite | This refers to the maximum concurrent WRITE request handled by the reverse proxy. | No | 4 |
+| maxOutStandingRead | This refers to maximum queued READ request when reverse proxy receives more than _maxActiveRead_ requests. | No | 50 |
+| maxOutStandingWrite| This refers to maximum queued WRITE request when reverse proxy receives more than _maxActiveWrite_ requests. | No | 50 |
+| kubeletConfigDir | Specify kubelet config dir path | Yes | /var/lib/kubelet |
+| imagePullPolicy | The default pull policy is IfNotPresent which causes the Kubelet to skip pulling an image if it already exists. | Yes | IfNotPresent |
| clusterPrefix | Prefix that is used during the creation of various masking-related entities (Storage Groups, Masking Views, Hosts, and Volume Identifiers) on the array. The value that you specify here must be unique. Ensure that no other CSI PowerMax driver is managing the same arrays that are configured with the same prefix. The maximum length for this prefix is three characters. | Yes | "ABC" |
-| logLevel | CSI driver log level. Allowed values: "error", "warn"/"warning", "info", "debug". | Yes | "debug" |
-| logFormat | CSI driver log format. Allowed values: "TEXT" or "JSON". | Yes | "TEXT" |
-| kubeletConfigDir | kubelet config directory path. Ensure that the config.yaml file is present at this path. | Yes | /var/lib/kubelet |
-| defaultFsType | Used to set the default FS type for external provisioner | Yes | ext4 |
-| portGroups | List of comma-separated port group names. Any port group that is specified here must be present on all the arrays that the driver manages. | For iSCSI Only | "PortGroup1, PortGroup2, PortGroup3" |
-| skipCertificateValidation | Skip client-side TLS verification of Unisphere certificates | No | "True" |
-| transportProtocol | Set the preferred transport protocol for the Kubernetes cluster which helps the driver choose between FC and iSCSI when a node has both FC and iSCSI connectivity to a PowerMax array.| No | Empty|
-| nodeNameTemplate | Used to specify a template that will be used by the driver to create Host/IG names on the PowerMax array. To use the default naming convention, leave this value empty. | No | Empty|
-| modifyHostName | Change any existing host names. When nodenametemplate is set, it changes the name to the specified format else it uses driver default host name format. | No | false |
-| powerMaxDebug | Enables low level and http traffic logging between the CSI driver and Unisphere. Don't enable this unless asked to do so by the support team. | No | false |
-| enableCHAP | Determine if the driver is going to configure SCSI 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" | No | false |
-| fsGroupPolicy | Defines which FS Group policy mode to be used, Supported modes `None, File and ReadWriteOnceWithFSType` | No | "ReadWriteOnceWithFSType" |
-| version | Current version of the driver. Don't modify this value as this value will be used by the install script. | Yes | v2.10.0 |
-| images | List all the images used by the CSI driver and CSM. If you use a private repository, change the registries accordingly. | Yes | "" || driverRepository | Defines the registry of the container image used for the driver. | Yes | dellemc |
-| maxPowerMaxVolumesPerNode | Specifies the maximum number of volume that can be created on a node. | Yes| 0 |
-| **controller** | Allows configuration of the controller-specific parameters.| - | - |
-| controllerCount | Defines the number of csi-powerscale controller pods to deploy to the Kubernetes release| Yes | 2 |
-| volumeNamePrefix | Defines a string prefix for the names of PersistentVolumes created | Yes | "k8s" |
-| snapshot.enabled | Enable/Disable volume snapshot feature | Yes | true |
-| snapshot.snapNamePrefix | Defines a string prefix for the names of the Snapshots created | Yes | "snapshot" |
-| resizer.enabled | Enable/Disable volume expansion feature | Yes | true |
-| healthMonitor.enabled | Allows to enable/disable volume health monitor | No | false |
-| healthMonitor.interval | Interval of monitoring volume health condition | No | 60s |
-| nodeSelector | Define node selection constraints for pods of controller deployment | No | |
-| tolerations | Define tolerations for the controller deployment, if required | No | |
-| **node** | Allows configuration of the node-specific parameters.| - | - |
-| tolerations | Add tolerations as per requirement | No | - |
-| nodeSelector | Add node selectors as per requirement | No | - |
-| healthMonitor.enabled | Allows to enable/disable volume health monitor | No | false |
-| topologyControl.enabled | Allows to enable/disable topology control to filter topology keys | No | false |
-| **csireverseproxy**| This section refers to the configuration options for CSI PowerMax Reverse Proxy | - | - |
-| tlsSecret | This refers to the TLS secret of the Reverse Proxy Server.| Yes | csirevproxy-tls-secret |
-| deployAsSidecar | If set to _true_, the Reverse Proxy is installed as a sidecar to the driver's controller pod otherwise it is installed as a separate deployment.| Yes | "True" |
-| port | Specify the port number that is used by the NodePort service created by the CSI PowerMax Reverse Proxy installation| Yes | 2222 |
-| **certManager** | Auto-create TLS certificate for csi-reverseproxy | - | - |
-| selfSignedCert | Set selfSignedCert to use a self-signed certificate | No | true |
-| certificateFile | certificateFile has tls.key content in encoded format | No | tls.crt.encoded64 |
-| privateKeyFile | privateKeyFile has tls.key content in encoded format | No | tls.key.encoded64 |
-| **authorization** | [Authorization](../../../../../deployment/helm/modules/installation/authorization/) is an optional feature to apply credential shielding of the backend PowerMax. | - | - |
-| enabled | A boolean that enables/disables authorization feature. | No | false |
-| proxyHost | Hostname of the csm-authorization server. | No | Empty |
-| skipCertificateValidation | A boolean that enables/disables certificate validation of the csm-authorization proxy server. | No | true |
-| **migration** | [Migration](../../../../../replication/migration/migrating-volumes-same-array) is an optional feature to enable migration between storage classes | - | - |
-| enabled | A boolean that enables/disables migration feature. | No | false |
-| image | Image for dell-csi-migrator sidecar. | No | " " |
-| nodeRescanSidecarImage | Image for node rescan sidecar which rescans nodes for identifying new paths. | No | " " |
-| migrationPrefix | enables migration sidecar to read required information from the storage class fields | No | migration.storage.dell.com |
-| **replication** | [Replication](../../../../../deployment/helm/modules/installation/replication/) is an optional feature to enable replication & disaster recovery capabilities of PowerMax to Kubernetes clusters.| - | - |
-| enabled | A boolean that enables/disables replication feature. | No | false |
-| replicationContextPrefix | enables side cars to read required information from the volume context | No | powermax |
-| replicationPrefix | Determine if replication is enabled | No | replication.storage.dell.com |
-| **storageCapacity** | It is an optional feature that enable storagecapacity & helps the scheduler to check whether the requested capacity is available on the PowerMax array and allocate it to the nodes.| - | - |
-| enabled | A boolean that enables/disables storagecapacity feature. | - | true |
-| pollInterval | It configure how often external-provisioner polls the driver to detect changed capacity | - | 5m |
-| **vSphere**| This section refers to the configuration options for VMware virtualized environment support via RDM | - | - |
-| enabled | A boolean that enables/disables VMware virtualized environment support. | No | false |
-| fcPortGroup | Existing portGroup that driver will use for vSphere. | Yes | "" |
-| fcHostGroup | Existing host(initiator group)/hostgroup(cascaded initiator group) that driver will use for vSphere. | Yes | "" |
-| vCenterHost | URL/endpoint of the vCenter where all the ESX are present | Yes | "" |
-| vCenterCredSecret | Secret name for the vCenter credentials. | Yes | "" |
+| logLevel | CSI driver log level. Allowed values: "error", "warn"/"warning", "info", "debug". | Yes | "debug" |
+| logFormat | CSI driver log format. Allowed values: "TEXT" or "JSON". | Yes | "TEXT" |
+| kubeletConfigDir | kubelet config directory path. Ensure that the config.yaml file is present at this path. | Yes | /var/lib/kubelet |
+| defaultFsType | Used to set the default FS type for external provisioner | Yes | ext4 |
+| portGroups | List of comma-separated port group names. Any port group that is specified here must be present on all the arrays that the driver manages. | For iSCSI Only | "PortGroup1, PortGroup2, PortGroup3" |
+| skipCertificateValidation | Skip client-side TLS verification of Unisphere certificates | No | "True" |
+| transportProtocol | Set the preferred transport protocol for the Kubernetes cluster which helps the driver choose between FC, iSCSI and NVMeTCP, when a node has multiple protocol connectivity to a PowerMax array. | No | Empty|
+| nodeNameTemplate | Used to specify a template that will be used by the driver to create Host/IG names on the PowerMax array. To use the default naming convention, leave this value empty. | No | Empty|
+| modifyHostName | Change any existing host names. When nodenametemplate is set, it changes the name to the specified format else it uses driver default host name format. | No | false |
+| powerMaxDebug | Enables low level and http traffic logging between the CSI driver and Unisphere. Don't enable this unless asked to do so by the support team. | No | false |
+| enableCHAP | Determine if the driver is going to configure SCSI 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" | No | false |
+| fsGroupPolicy | Defines which FS Group policy mode to be used, Supported modes `None, File and ReadWriteOnceWithFSType` | No | "ReadWriteOnceWithFSType" |
+| version | Current version of the driver. Don't modify this value as this value will be used by the install script. | Yes | v2.10.0 |
+| images | List all the images used by the CSI driver and CSM. If you use a private repository, change the registries accordingly. | Yes | "" || driverRepository | Defines the registry of the container image used for the driver. | Yes | dellemc |
+| maxPowerMaxVolumesPerNode | Specifies the maximum number of volume that can be created on a node. | Yes| 0 |
+| **controller** | Allows configuration of the controller-specific parameters. | - | - |
+| controllerCount | Defines the number of csi-powerscale controller pods to deploy to the Kubernetes release | Yes | 2 |
+| volumeNamePrefix | Defines a string prefix for the names of PersistentVolumes created | Yes | "k8s" |
+| snapshot.enabled | Enable/Disable volume snapshot feature | Yes | true |
+| snapshot.snapNamePrefix | Defines a string prefix for the names of the Snapshots created | Yes | "snapshot" |
+| resizer.enabled | Enable/Disable volume expansion feature | Yes | true |
+| healthMonitor.enabled | Allows to enable/disable volume health monitor | No | false |
+| healthMonitor.interval | Interval of monitoring volume health condition | No | 60s |
+| nodeSelector | Define node selection constraints for pods of controller deployment | No | |
+| tolerations | Define tolerations for the controller deployment, if required | No | |
+| **node** | Allows configuration of the node-specific parameters. | - | - |
+| tolerations | Add tolerations as per requirement | No | - |
+| nodeSelector | Add node selectors as per requirement | No | - |
+| healthMonitor.enabled | Allows to enable/disable volume health monitor | No | false |
+| topologyControl.enabled | Allows to enable/disable topology control to filter topology keys | No | false |
+| **csireverseproxy**| This section refers to the configuration options for CSI PowerMax Reverse Proxy | - | - |
+| tlsSecret | This refers to the TLS secret of the Reverse Proxy Server. | Yes | csirevproxy-tls-secret |
+| deployAsSidecar | If set to _true_, the Reverse Proxy is installed as a sidecar to the driver's controller pod otherwise it is installed as a separate deployment. | Yes | "True" |
+| port | Specify the port number that is used by the NodePort service created by the CSI PowerMax Reverse Proxy installation | Yes | 2222 |
+| **certManager** | Auto-create TLS certificate for csi-reverseproxy | - | - |
+| selfSignedCert | Set selfSignedCert to use a self-signed certificate | No | true |
+| certificateFile | certificateFile has tls.key content in encoded format | No | tls.crt.encoded64 |
+| privateKeyFile | privateKeyFile has tls.key content in encoded format | No | tls.key.encoded64 |
+| **authorization** | [Authorization](../../../../../deployment/helm/modules/installation/authorization/) is an optional feature to apply credential shielding of the backend PowerMax. | - | - |
+| enabled | A boolean that enables/disables authorization feature. | No | false |
+| proxyHost | Hostname of the csm-authorization server. | No | Empty |
+| skipCertificateValidation | A boolean that enables/disables certificate validation of the csm-authorization proxy server. | No | true |
+| **migration** | [Migration](../../../../../replication/migration/migrating-volumes-same-array) is an optional feature to enable migration between storage classes | - | - |
+| enabled | A boolean that enables/disables migration feature. | No | false |
+| image | Image for dell-csi-migrator sidecar. | No | " " |
+| nodeRescanSidecarImage | Image for node rescan sidecar which rescans nodes for identifying new paths. | No | " " |
+| migrationPrefix | enables migration sidecar to read required information from the storage class fields | No | migration.storage.dell.com |
+| **replication** | [Replication](../../../../../deployment/helm/modules/installation/replication/) is an optional feature to enable replication & disaster recovery capabilities of PowerMax to Kubernetes clusters. | - | - |
+| enabled | A boolean that enables/disables replication feature. | No | false |
+| replicationContextPrefix | enables side cars to read required information from the volume context | No | powermax |
+| replicationPrefix | Determine if replication is enabled | No | replication.storage.dell.com |
+| **storageCapacity** | It is an optional feature that enable storagecapacity & helps the scheduler to check whether the requested capacity is available on the PowerMax array and allocate it to the nodes. | - | - |
+| enabled | A boolean that enables/disables storagecapacity feature. | - | true |
+| pollInterval | It configure how often external-provisioner polls the driver to detect changed capacity | - | 5m |
+| **vSphere**| This section refers to the configuration options for VMware virtualized environment support via RDM | - | - |
+| enabled | A boolean that enables/disables VMware virtualized environment support. | No | false |
+| fcPortGroup | Existing portGroup that driver will use for vSphere. | Yes | "" |
+| fcHostGroup | Existing host(initiator group)/hostgroup(cascaded initiator group) that driver will use for vSphere. | Yes | "" |
+| vCenterHost | URL/endpoint of the vCenter where all the ESX are present | Yes | "" |
+| vCenterCredSecret | Secret name for the vCenter credentials. | Yes | "" |
8. Install the driver using `csi-install.sh` bash script by running