PowerMax documentation changes-release1.8 (#802)

content/docs/csidriver/features/powermax.md

@@ -617,11 +617,11 @@ vSphere:
 
 CSI PowerMax driver version 2.8.0 and above supports Storage Capacity Tracking.
 
-This feature helps the scheduler to make more informed choices about where to start pods that depend on unbound volumes with late binding (aka “wait for first consumer”). Nodes satisfying the topology constraints, and with the requested capacity that is present on the storage array, will be available for scheduling the pods, Otherwise, the pods stay in pending state.
+This feature helps the scheduler to make more informed choices about where to start pods that depend on unbound volumes with late binding (aka “wait for first consumer”). Nodes satisfying the topology constraints, and with the requested capacity that is present on the storage array, will be available for scheduling the pods, Otherwise, the pods stay in pending state. External-provisioner makes one GetCapacity() call per storage class that is present on the cluster to get the AvailableCapacity for the array specified in the storage class that matches with the array mentioned during driver deployment.
 
 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 the ContainerCreating state. Storage capacity tracking eliminates unnecessary scheduling of pods when there is insufficient capacity.
 
-Storage Capacity can be tracked by setting the attribute `storageCapacity.enabled` to true in values.yaml (set to true by default) during driver installation. To configure how often driver checks for changed capacity, set `storageCapacity.pollInterval` (set to 5m by default) 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_powermax_v280.yaml) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar.
+Storage capacity can be tracked by setting the attribute `storageCapacity.enabled` to true in values.yaml (set to true by default) during driver installation. To configure how often driver checks for changed capacity, set the `storageCapacity.pollInterval` attribute (set to 5m by default). 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) by editing the `--capacity-poll-interval` argument present in the provisioner sidecar.
 
 >Note: This feature requires kubernetes v1.24 and above and will be automatically disabled in lower version of kubernetes.
 
@@ -633,7 +633,7 @@ The CSI Driver for Dell PowerMax allows users to specify the maximum number of P
 The user can set the volume limit for a node by creating a node label `max-powermax-volumes-per-node` and specifying the volume limit for that node.
 <br/> `kubectl label node <node_name> max-powermax-volumes-per-node=<volume_limit>`
 
-The user can also set the volume limit for all the nodes in the cluster by specifying the same to `maxPowerMaxVolumesPerNode` attribute in values.yaml. In case of driver installed via operator, this attribute can be modified in the sample file provided [here] /~https://github.com/dell/csm-operator/blob/main/samples/storage_csm_powermax_v280.yaml by editing the `X_CSI_MAX_VOLUMES_PER_NODE` parameter. 
+The user can also set the volume limit for all the nodes in the cluster by specifying the same to `maxPowerMaxVolumesPerNode` attribute in values.yaml. In case of driver installed via operator, this attribute can be modified in the sample file provided [here](/~https://github.com/dell/csm-operator/blob/main/samples) by editing the `X_CSI_MAX_VOLUMES_PER_NODE` parameter. 
 
 This feature is also supported for limiting the volume provisioning on Kubernetes clusters running on vSphere (VMware hypervisor) via RDM mechanism. User can set `vSphere.enabled` to true and also set volume limits to positive values less than or equal 60 via labels or in Values.yaml file.
 

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

@@ -207,7 +207,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
 
 **Steps**
 
-1. Run `git clone -b v2.7.0 /~https://github.com/dell/csi-powermax.git` to clone the git repository. This will include the Helm charts and dell-csi-helm-installer scripts.
+1. Run `git clone -b v2.8.0 /~https://github.com/dell/csi-powermax.git` to clone the git repository. This will include the Helm charts and dell-csi-helm-installer scripts.
 2. Ensure that you have created a namespace where you want to install the driver. You can run `kubectl create namespace powermax` to create a new one 
 3. Edit the `samples/secret/secret.yaml` file,to point to the correct namespace, and replace the values for the username and password parameters.
     These values can be obtained using base64 encoding as described in the following example:
@@ -222,7 +222,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
     ```
 5. Download the default values.yaml file 
     ```bash
-    cd dell-csi-helm-installer && wget -O my-powermax-settings.yaml /~https://github.com/dell/helm-charts/raw/csi-powerstore-2.8.0/charts/csi-powermax/values.yaml
+    cd dell-csi-helm-installer && wget -O my-powermax-settings.yaml /~https://github.com/dell/helm-charts/raw/csi-powermax-2.8.0/charts/csi-powermax/values.yaml
     ```
 6. Ensure the unisphere have 10.0 REST endpoint support by clicking on Unisphere -> Help (?) -> About in Unisphere for PowerMax GUI.
 7. Edit the newly created file and provide values for the following parameters 
@@ -309,7 +309,6 @@ CRDs should be configured during replication prepare stage with repctl as descri
 | 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   |
-| image | Image for storagecapacity sidecar. | No | "" |
 | 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   |

content/docs/csidriver/release/powermax.md

@@ -18,14 +18,12 @@ description: Release notes for PowerMax CSI driver
 - [#861 - [FEATURE]: CSM for PowerMax file support ](/~https://github.com/dell/csm/issues/861)
 - [#876 - [FEATURE]: CSI 1.5 spec support -StorageCapacityTracking](/~https://github.com/dell/csm/issues/876)
 - [#877 - [FEATURE]: Make standalone helm chart available from helm repository : https://dell.github.io/dell/helm-charts](/~https://github.com/dell/csm/issues/877)
-- [#926 - [FEATURE]: Set up golangci-lint for all CSM repositories](/~https://github.com/dell/csm/issues/926)
 - [#947 - [FEATURE]: K8S 1.28 support in CSM 1.8](/~https://github.com/dell/csm/issues/947)
 - [#878 - [FEATURE] CSI 1.5 spec support : Implement Volume Limits](/~https://github.com/dell/csm/issues/878)
 - [#937 - [FEATURE]: Google Anthos 1.15 support  for PowerMax](/~https://github.com/dell/csm/issues/937)
 
 ### Fixed Issues
 
-- [#887 - [BUG]: Unit tests failing for CSI-PowerMax](/~https://github.com/dell/csm/issues/887)
 - [#890 - [BUG]: Missing nodeSelector and tolerations entry in sample file ](/~https://github.com/dell/csm/issues/890)
 - [#907 - [BUG]: Cert Manager should display tooltip about the pre-requisite. ](/~https://github.com/dell/csm/issues/907)
 - [#951 - [BUG]: Powermax : Static provisioning is failing for NFS volume ](/~https://github.com/dell/csm/issues/951)
@@ -37,6 +35,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: <br /> 1. Force delete the pod running on the node that went down <br /> 2. Delete the volumeattachment to the node that went down. <br /> Now the volume can be attached to the new node |
+| 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. |
 
 ### Note:
 

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

@@ -52,8 +52,8 @@ You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSI Operator.
 
     ```
 
-## Upgrade using Dell CSI Operator:
+## Upgrade using Dell CSM Operator:
 **Note:** Upgrading the Operator does not upgrade the CSI Driver.
 
-1. Please upgrade the Dell CSI Operator by following [here](./../operator).
-2. Once the operator is upgraded, to upgrade the driver, refer [here](./../../../installation/operator/#update-csi-drivers).
+1. Upgrade the Dell CSM Operator by following [here](../../../../deployment/csmoperator/#to-upgrade-dell-csm-operator-perform-the-following-steps)
+2. Once the operator is upgraded, to upgrade the driver, refer [here](../../../../deployment/csmoperator/#upgrade-driver-using-dell-csm-operator)