1.16.1 changes (#1751)

Author: anandrajak1

content/docs/concepts/csidriver/_index.md

@@ -42,15 +42,14 @@ The CSI Drivers implement an interface between [CSI](https://kubernetes-csi.gith
 | <div style="text-align: left"> iSCSI         | Yes              | N/A              | N/A                | Yes              | Yes               |
 | <div style="text-align: left"> NVMeTCP       | Yes              | N/A              | Yes                 | Yes              | N/A               |
 | <div style="text-align: left"> NVMeFC        | Yes              | N/A              | N/A                | N/A              | N/A               |
-| <div style="text-align: left"> NFS           | Yes              | Yes              | N/A*               | Yes - SDNAS only (No eNAS) | Yes     |
+| <div style="text-align: left"> NFS           | Yes              | Yes              | N/A               | Yes - SDNAS only (No eNAS) | Yes     |
 | <div style="text-align: left"> Other         | N/A              | N/A              | ScaleIO protocol   | N/A              | N/A               |
 | <div style="text-align: left"> Supported FS  | ext3 / ext4 / xfs / NFS | NFS       | ext4 / xfs / NFS   | ext4 / xfs / NFS | ext4 / xfs / NFS  |
 | <div style="text-align: left"> Thin / Thick provisioning | Thin | N/A              | Thin               | Thin             | Thin/Thick        |
 | <div style="text-align: left"> Platform-specific configurable settings | iSCSI CHAP | Access Zone<br>NFS version (3 or 4)<br>Configurable Export IPs | - | Service Level selection<br>iSCSI CHAP | Host IO Limit<br>Tiering Policy<br>NFS Host IO size<br>Snapshot Retention duration |
 | <div style="text-align: left"> Auto RDM(vSphere)  | N/A         | N/A              | N/A                | Yes(over FC)     | N/A              |
 | <div style="text-align: left"> Internet Protocol| IPv4          | IPv4             | IPv4               | IPv4             | IPv4             |
 {{</table>}}
-> **Note:** * PowerFlex supports NFS until version 3.6
 
 > **Note:** Please note Dual-Stack or IPv6 is not supported.
 

content/docs/concepts/csidriver/features/powerflex.md

@@ -462,8 +462,8 @@ on any worker node with access to the PowerMax array `000000000001` irrespective
 
 > A set of sample storage class definitions to enable topology-aware volume provisioning has been provided in the `csi-powermax/samples/storageclass` folder
 
-**Note** : 
-- From CSM 1.15 onwards, the CSI driver adds NFS labels to the CSI nodes only after verifying that NFS is enabled on the storage array. This ensures that node labeling accurately reflects the capabilities of the backend storage system. 
+**Note** :
+- From CSM 1.15 onwards, the CSI driver adds NFS labels to the CSI nodes only after verifying that NFS is enabled on the storage array. This ensures that node labeling accurately reflects the capabilities of the backend storage system.
 - It is assumed that NFS dependencies are configured by default on the node, as these dependencies are included in the default Linux OS package. For other protocols (iSCSI, FC, NVMe/TCP), all necessary connectivity checks between the initiator and target are performed before labels are added.
 
 You can check what labels your nodes contain by running
@@ -720,6 +720,8 @@ This method works with both `helm` and `operator` installations for PowerMax, au
 
 **Note:** ConfigMaps to specify credentials is deprecated as of CSI PowerMax v2.14.0 and will be removed in a future release. However, for backwards compatibility, you can still configure and use the PowerMax driver with the config map.
 
+**NOTE:** For each entry in `managementServers`, if `skipCertificateValidation` is set to `true`, then the `certSecret` field must not be present in that same entry.
+
 ## Multiple Availability Zones
 
 Starting with CSM 1.14.0, the PowerMax CSI driver supports multiple availability zones (AZ) for block protocols. Availability Zones permit provisioning of volumes on storage arrays that are dedicated to a set of cluster nodes. Cluster nodes in an AZ will only access storage in the same AZ. Arrays in an AZ will not be used to provision storage to nodes which are not in the same AZ. This may be of benefit when stricter control of access to storage is needed or for disaster preparation use cases. Unlike the [topology support](#topology-support) mentioned earlier, multi AZ support restricts driver access to storage to only from arrays within the cluster node's AZ. No host registration nor storage connectivity setup is performed to arrays not in the node's AZ.

content/docs/concepts/csidriver/features/powermax.md

@@ -1,6 +1,6 @@
 ---
 title: PowerMax
-linktitle: PowerMax 
+linktitle: PowerMax
 description: Troubleshooting PowerMax Driver
 ---
 <div class="tdleft">
@@ -21,7 +21,8 @@ description: Troubleshooting PowerMax Driver
 | `kubectl logs powermax-controller-<xyz> –n <namespace>` driver logs says connection refused and the reverseproxy logs says "Failed to setup server.(secrets \"secret-name\" not found)" | Make sure the given secret <secret-name> exist on the cluster |
 | nodestage is failing with error `Error invalid IQN Target iqn.EMC.0648.SE1F` | 1. Update initiator name to full default name , ex: iqn.1993-08.org.debian:01:e9afae962192 <br> 2.Ensure that the iSCSI initiators are available on all the nodes where the driver node plugin will be installed and it should be full default name. |
 | Volume mount is failing on few OS(ex:VMware Virtual Platform) during node publish with error `wrong fs type, bad option, bad superblock` | 1. Check the multipath configuration(if enabled) 2. Edit Vm Advanced settings->hardware and add the param `disk.enableUUID=true` and reboot the 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 <deployment_name> --replicas=1 -n <driver_namespace>``` |  
+| Standby controller pod is in crashloopbackoff state | Scale down the replica count of the controller pod's deployment to 1 using ```kubectl scale deployment <deployment_name> --replicas=1 -n <driver_namespace>``` |
 | When running CSI-PowerMax with Replication in a multi-cluster configuration, the driver on the target cluster fails and the following error is seen in logs: `error="CSI reverseproxy service host or port not found, CSI reverseproxy not installed properly"` | The reverseproxy service needs to be created manually on the target cluster. Follow [the instructions here](/docs/getting-started/installation/kubernetes/powermax/csmoperator/csm-modules/replication/#configuration-steps) to create it.|
 | PVC creation is failing with error `A problem occurred modifying the storage group resource: Failed to create batch task(s): The maximum allowed devices for a storage group has been exceeded`. This is because of a hardware limit of 4k devices in a storage group.| Create a separate Storage Class with a new unique `ApplicationPrefix` parameter (such as `ApplicationPrefix: OCPX`) or add a new unique `StorageGroup` parameter (such as `StorageGroup: "custom_SG_1"`) to place the provisioned volumes in a new Storage Group.|
+| Despite having `skipCertificateValidation` set to true, the driver fails to start with the following error appearing in the reverseproxy container logs: `[ERROR]  Failed to run server: secrets "xxx" not found`| Remove the `certSecret` field from your secret/configmap |
 </div>

content/docs/concepts/csidriver/troubleshooting/powermax.md

@@ -25,9 +25,9 @@ Replication provides the following capabilities:
 | Capability                                                                                                                            | PowerStore | PowerScale | PowerFlex | PowerMax | Unity XT |
 | ------------------------------------------------------------------------------------------------------------------------------------- |:----------:| :--------: | :-------: |:--------:| :---: |
 | <div style="text-align: left">Replicate data using native storage array based replication                                             |    Yes    |    Yes      |    Yes     |   Yes    |  No   |
-| <div style="text-align: left">Asynchronous file volume replication                                                                    |    No     |    Yes      |    N/A*     |    No    |  No   |
+| <div style="text-align: left">Asynchronous file volume replication                                                                    |    Yes     |    Yes      |    N/A     |    No    |  No   |
 | <div style="text-align: left">Asynchronous block volume replication                                                                   |    Yes    |    N/A      |    Yes     |   Yes    |  No   |
-| <div style="text-align: left">Synchronous file volume replication                                                                     |    No     |    No       |    N/A*     |    No    |  No   |
+| <div style="text-align: left">Synchronous file volume replication                                                                     |    Yes     |    No       |    N/A     |    No    |  No   |
 | <div style="text-align: left">Synchronous block volume replication                                                                    |    Yes    |    N/A      |    N/A     |   Yes    |  No   |
 | <div style="text-align: left">Active-Active (Metro) block volume replication                                                          |    Yes    |    N/A      |    N/A     |   Yes    |  No   |
 | <div style="text-align: left">Active-Active (Metro) file volume replication                                                           |    No     |    N/A      |    N/A     |    No    |  No   |
@@ -41,8 +41,6 @@ Replication provides the following capabilities:
 
 {{</table>}}
 
-> **Note:** * PowerFlex supports file Asynchronous/Synchronous volume replication until version 3.6
-
 > _**NOTE**_: To add or delete PVs on an existing SYNC Replication Group in
 > PowerStore, the user needs to pause, perform the operation and then resume the
 > replication group. For more details, please refer to the troubleshooting

content/docs/concepts/replication/_index.md

@@ -371,7 +371,7 @@ spec:
 | images.storageService               | The image to use for the storage-service.                                                                              | Yes      | quay.io/dell/container-storage-modules/csm-authorization-storage:{{< version-docs key="Authv2_csm_authorization_storage" >}} |
 | images.authorizationController      | The image to use for the controller.                                                                                   | Yes      | quay.io/dell/container-storage-modules/csm-authorization-controller                                                          |
 | images.opa                          | The image to use for Open Policy Agent.                                                                                | Yes      | openpolicyagent/opa                                                                                                          |
-| images.opaKubeMgmt                  | The image to use for Open Policy Agent kube-mgmt.                                                                      | Yes      | openpolicyagent/kube-mgmt:9.3.0                                                                                              |
+| images.opaKubeMgmt                  | The image to use for Open Policy Agent kube-mgmt.                                                                      | Yes      | openpolicyagent/kube-mgmt:9.2.1                                                                                              |
 | hostname                            | The hostname to configure the self-signed certificate (if applicable) and the proxy Ingress.                           | Yes      | csm-authorization.com                                                                                                        |
 | logLevel                            | Authorization log level. Allowed values: “error”, “warn”/“warning”, “info”, “debug”.                                   | Yes      | debug                                                                                                                        |
 | concurrentPowerFlexRequests         | Number of concurrent requests to PowerFlex. Used with dellctl to list tenant volumes.                                  | Yes      | 10                                                                                                                           |