Merge branch 'release-1.8.0' into Ro_pvc_changes

content/docs/csidriver/_index.md

@@ -16,7 +16,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 {{<table "table table-striped table-bordered table-sm">}}
 |               | PowerMax         | PowerFlex           | Unity XT         | PowerScale        | PowerStore       |
 |---------------|:----------------:|:-------------------:|:----------------:|:-----------------:|:----------------:|
-| Kubernetes    | 1.26, 1.27, 1.28 | 1.25, 1.26, 1.27    | 1.25, 1.26, 1.27 | 1.26, 1.27, 1.28  | 1.25, 1.26, 1.27 |
+| Kubernetes    | 1.26, 1.27, 1.28 | 1.25, 1.26, 1.27    | 1.25, 1.26, 1.27 | 1.26, 1.27, 1.28  | 1.26, 1.27, 1.28 |
 | RHEL          |     7.x,8.x  |     7.x,8.x         |     7.x,8.x      |     7.x,8.x       |     7.x,8.x      |
 | Ubuntu        |       20.04      |       20.04         |  18.04, 20.04    | 20.04, 22.04      |        20.04     |
 | CentOS        |     7.8, 7.9     |      7.8, 7.9       |     7.9     |      7.8, 7.9     |     7.8, 7.9     |
@@ -41,14 +41,14 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 | Create VolumeSnapshot    | yes      | yes       | yes       | yes        | yes        |
 | Create Volume from Snapshot | yes   | yes       | yes       | yes        | yes        |
 | Delete Snapshot          | yes      | yes       | yes       | yes        | yes        |
-| [Access Mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes)| **FC/iSCSI:** <br>RWO/<br>RWOP<br> **Raw block:** <br>RWO/<br>RWX/<br>ROX/<br>RWOP | RWO/ROX/RWOP<br><br>RWX (Raw block & NFS only) | RWO/ROX/RWOP<br><br>RWX (Raw block & NFS only) | RWO/RWX/ROX/<br>RWOP | RWO/RWOP<br>(FC/iSCSI)<br>RWO/<br>RWX/<br>ROX/<br>RWOP<br>(RawBlock, NFS) |
+| [Access Mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes)| **FC/iSCSI:** <br>RWO/<br>RWOP<br> **Raw block/NFS:** <br>RWO/<br>RWX/<br>ROX/<br>RWOP | RWO/ROX/RWOP<br><br>RWX (Raw block & NFS only) | RWO/ROX/RWOP<br><br>RWX (Raw block & NFS only) | RWO/RWX/ROX/<br>RWOP | RWO/RWOP<br>(FC/iSCSI)<br>RWO/<br>RWX/<br>ROX/<br>RWOP<br>(RawBlock, NFS) |
 | CSI Volume Cloning       | yes      | yes       | yes       | yes        | yes        |
 | CSI Raw Block Volume     | yes      | yes       | yes       | no         | yes        |
 | CSI Ephemeral Volume     | no       | yes       | yes       | yes        | yes        |
 | Topology                 | yes      | yes       | yes       | yes        | yes        |
 | Multi-array              | yes      | yes       | yes       | yes        | yes        |
 | Volume Health Monitoring | yes      | yes       | yes       | yes        | yes        |
-| Storage Capacity Tracking | yes      | no        | yes        | yes        | yes        |
+| Storage Capacity Tracking | yes      | yes        | yes        | yes        | yes        |
 {{</table>}}
 ### Supported Storage Platforms
 {{<table "table table-striped table-bordered table-sm">}}
@@ -64,9 +64,9 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 | iSCSI         | yes              | N/A                | yes              | N/A              | yes              |
 | NVMeTCP       | N/A              | N/A                | N/A              | N/A              | yes              |
 | NVMeFC        | N/A              | N/A                | N/A              | N/A              | yes              |
-| NFS           | N/A              | N/A                | yes              | yes              | yes              |
+| NFS           | yes              | N/A                | yes              | yes              | yes              |
 | Other         | N/A              | ScaleIO protocol   | N/A              | N/A              | N/A              |
-| Supported FS  | ext4 / xfs       | ext4 / xfs / NFS   | ext4 / xfs / NFS | NFS       | ext3 / ext4 / xfs / NFS |
+| Supported FS  | ext4 / xfs / NFS | ext4 / xfs / NFS   | ext4 / xfs / NFS | NFS       | ext3 / ext4 / xfs / NFS |
 | Thin / Thick provisioning | Thin  | Thin              | Thin/Thick       | N/A              | Thin             |
 | Platform-specific configurable settings | Service Level selection<br>iSCSI CHAP | - | Host IO Limit<br>Tiering Policy<br>NFS Host IO size<br>Snapshot Retention duration | Access Zone<br>NFS version (3 or 4);Configurable Export IPs | iSCSI CHAP |
 | Auto RDM(vSphere)  | Yes(over FC)  | N/A              | N/A      | N/A              | N/A             |

content/docs/csidriver/features/powerflex.md

@@ -658,6 +658,16 @@ Warning  VolumeConditionAbnormal      35s (x9 over 12m)  kubelet       Volume vo
 Warning  VolumeConditionAbnormal      5s                 kubelet       Volume vol2: Volume is not found by node driver at 2021-11-11 02:04:49
 ```
 
+## Storage Capacity Tracking
+CSI-PowerFlex driver version 2.8.0 and above supports Storage Capacity Tracking.
+
+This feature helps the scheduler to make more informed choices about where to schedule pods which depends on unbound volumes with late binding (aka "wait for first consumer"). Pods will be scheduled on a node (satisfying the topology constraints) only if the requested capacity is available on the storage array.
+If such a node is not available, the pods stay in Pending state. This means pods are not scheduled.
+
+Without storage capacity tracking, pods get scheduled on a node satisfying the topology constraints. If the required capacity is not available, volume attachment to the pods fails, and pods remain in ContainerCreating state. Storage capacity tracking eliminates unnecessary scheduling of pods when there is insufficient capacity.
+
+The attribute `storageCapacity.enabled` in `values.yaml` can be used to enable/disable the feature during driver installation using helm. This is by default set to true. To configure how often driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample file provided [here.](https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powerflex_v280.yaml) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar.
+
 ## Set QoS Limits
 Starting in version 2.5, CSI Driver for PowerFlex now supports setting the limits for the bandwidth and IOPS that one SDC generates for the specified volume. This enables the CSI driver to control the quality of service (QoS).
 In this release this is supported at the StorageClass level, so once a volume is created QoS Settings can't be adjusted later.

content/docs/csidriver/installation/helm/powerflex.md

@@ -193,6 +193,8 @@ Use the below command to replace or update the secret:
 | enabled | A boolean that enable/disable rename SDC feature. | No | false |
 | prefix | Defines a string for the prefix of the SDC. | No | " " |
 | approveSDC.enabled | A boolean that enable/disable SDC approval feature. | No | false |
+| storageCapacity.enabled | Enable/Disable storage capacity tracking | No | true |
+| storageCapacity.pollInterval | Configure how often the driver checks for changed capacity | No | 5m |
 | **monitor**              | This section allows the configuration of the SDC monitoring pod.                                                                                                                                                                                                                                                                                                                                                  | -        | -       |
 | enabled                  | Set to enable the usage of the monitoring pod.                                                                                                                                                                                                                                                                                                                                                                | Yes     | false |
 | hostNetwork              | Set whether the monitor pod should run on the host network or not.                                                                                                                                                                                                                                                                                                                                            | Yes     | true |

content/docs/csidriver/installation/helm/powermax.md

@@ -31,6 +31,7 @@ The following requirements must be met before installing CSI Driver for Dell Pow
 - Install Helm 3
 - Fibre Channel requirements
 - iSCSI requirements
+- NFS 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
@@ -90,6 +91,13 @@ Set up the iSCSI initiators as follows:
 
 For more information about configuring iSCSI, see [Dell Host Connectivity guide](https://www.delltechnologies.com/asset/zh-tw/products/storage/technical-support/docu5128.pdf).
 
+### NFS requirements
+
+CSI Driver for Dell PowerMax supports NFS communication. Ensure that the following requirements are met before you install CSI Driver:
+- Configure the NFS network. Please refer [here](https://dl.dell.com/content/manual57826791-dell-powermax-file-protocol-guide.pdf?language=en-us&ps=true) for more details.
+- 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.
+
 ### 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.

content/docs/csidriver/installation/helm/unity.md

@@ -331,22 +331,17 @@ Procedure
     /csi-install.sh --namespace unity --values ./myvalues.yaml --version latest
     ```
 
-8. You can also install the driver using standalone helm chart by running helm install command, first using the --dry-run flag to 
-   confirm various parameters are as desired. Once the parameters are validated, run the command without the --dry-run flag.
-   Note: This example assumes that the user is at repo root helm folder i.e csi-unity/helm.
+8. You can also install the driver using standalone helm chart by cloning the centralised helm charts and running the helm install command as shown.
 
    **Syntax**:
    ```bash
-   helm install --dry-run --values <myvalues.yaml location> --namespace <namespace> <name of secret> <helmPath>
-   ```
-   `<namespace>` - namespace of the driver installation.  <br/>
-   `<name of secret>` - unity in case of unity-creds and unity-certs-0 secrets. <br/>
-   `<helmPath>` - Path of the helm directory. <br/>
-   e.g: 
-   ```bash
-   helm install --dry-run --values ./csi-unity/myvalues.yaml --namespace unity unity ./csi-unity
-   ```
 
+   git clone -b csi-unity-2.8.0 https://github.com/dell/helm-charts
+
+   helm install <release-name> dell/container-storage-modules -n <namespace> --version <container-storage-module chart-version> -f <values.yaml location>
+
+   Example: helm install unity dell/container-storage-modules -n csi-unity --version 1.0.1 -f values.yaml
+   ```
 
 ## Certificate validation for Unisphere REST API calls 
 

content/docs/csidriver/release/powerflex.md

@@ -8,6 +8,7 @@ description: Release notes for PowerFlex CSI driver
 ### New Features/Changes
 - [Added support for OpenShift 4.13](https://github.com/dell/csm/issues/724)
 - [Enabled volume limits feature](https://github.com/dell/csm/issues/878)
+- [Added support for Storage Capacity Tracking feature](https://github.com/dell/csm/issues/876)
 - [Updated sdc version to 3.6.1](https://github.com/dell/csm/issues/885)
 - [Added support for NFS volumes](https://github.com/dell/csm/issues/763)
 

content/docs/csidriver/release/powermax.md

@@ -9,13 +9,16 @@ description: Release notes for PowerMax CSI driver
 
 > Note: Starting from CSI v2.4.0, Only Unisphere 10.0 REST endpoints are supported. It is mandatory that Unisphere should be updated to 10.0. Please find the instructions [here.](https://dl.dell.com/content/manual34878027-dell-unisphere-for-powermax-10-0-0-installation-guide.pdf?language=en-us&ps=true)
 
+>Note: File Replication for PowerMax is currently not supported 
+
 ### New Features/Changes
 - [Added support for OpenShift 4.13](https://github.com/dell/csm/issues/724)
 - [Added Storage Capacity Tracking feature for Powermax](https://github.com/dell/csm/issues/876)
 - [Make standalone helm chart available from helm repository](https://github.com/dell/csm/issues/877)
 - [Added support for Google Anthos 1.15](https://github.com/dell/csm/issues/937)
 - [Added support for Volume Limits feature](https://github.com/dell/csm/issues/878)
 - [Added support for Kubernetes 1.28](https://github.com/dell/csm/issues/947)
+- [Added support for File volumes](https://github.com/dell/csm/issues/861)
 ### Fixed Issues
 There are no fixed issues in this release.
 

content/docs/csidriver/upgradation/drivers/powermax.md

@@ -16,10 +16,10 @@ You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSI Operator.
 1. Upgrade the Unisphere to have 10.0 endpoint support.Please find the instructions [here.](https://dl.dell.com/content/manual34878027-dell-unisphere-for-powermax-10-0-0-installation-guide.pdf?language=en-us&ps=true)
 2. Update the `my-powermax-settings.yaml` to have endpoint with 10.0 support.
 
-## Update Driver from v2.6 to v2.7 using Helm
+## Update Driver from v2.7 to v2.8 using Helm
 
 **Steps**
-1. Run `git clone -b v2.7.0 https://github.com/dell/csi-powermax.git` to clone the git repository and get the driver.
+1. Run `git clone -b v2.8.0 https://github.com/dell/csi-powermax.git` to clone the git repository and get the driver.
 2. Update the values file as needed.
 3. Run the `csi-install` script with the option _\-\-upgrade_ by running: 
    ```bash