Revert "Add troubleshooting entry (#187)" (#188)

This reverts commit 17359e3.

config.toml

@@ -172,19 +172,19 @@ enable = false
 #	icon = "fa fa-envelope"
 #        desc = "Discuss development issues around the project"
 [[params.versions]]
-  version = "Current(v1.3)"
+  version = "Current(v1.2)"
   url = "https://dell.github.io/csm-docs/docs/"
 
 [[params.versions]]
-  version = "v1.2"
+  version = "v1.1"
   url = "https://dell.github.io/csm-docs/v1"
 
 [[params.versions]]
-  version = "v1.1"
+  version = "v1.0.1"
   url = "https://dell.github.io/csm-docs/v2"
 
 [[params.versions]]
-  version = "v1.0.1"
+  version = "v1.0"
   url = "https://dell.github.io/csm-docs/v3"  
 
 [[menu.main]]

content/docs/FAQ/_index.md

@@ -32,7 +32,7 @@ The umbrella repository for every Dell Container Storage Module is: [https://git
 ### Is the Container Storage Module XYZ available for my array?
 Please see module and the respectice CSI driver version available for each array:
 
-| CSM Module        | CSI PowerFlex v2.3 | CSI PowerScale v2.3 | CSI PowerStore v2.3 | CSI PowerMax v2.3 | CSI Unity XT v2.3    |
+| CSM Module        | CSI PowerFlex v2.2 | CSI PowerScale v2.2 | CSI PowerStore v2.2 | CSI PowerMax v2.2 | CSI Unity XT v2.2    |
 | ----------------- | -------------- | --------------- | --------------- | ------------- | --------------- |
 | Authorization v1.2| ✔️              | ✔️               | ❌              | ✔️             | ❌            |
 | Observability v1.1| ✔️              | ❌              | ✔️               | ❌            | ❌            |

content/docs/_index.md

@@ -18,14 +18,14 @@ CSM is made up of multiple components including modules (enterprise capabilities
 
 ## CSM Supported Modules and Dell CSI Drivers
 
-| Modules/Drivers | CSM 1.3 | [CSM 1.2](../v1/) | [CSM 1.1](../v2/) | [CSM 1.0.1](../v3/) | 
+| Modules/Drivers | CSM 1.2 | [CSM 1.1](../v1/) | [CSM 1.0.1](../v1/) | [CSM 1.0](../v2/) | 
 | - | :-: | :-: | :-: | :-: |
-| [Authorization](https://hub.docker.com/r/dellemc/csm-authorization-sidecar) | 1.2 | 1.2 | 1.1 | 1.0 |
-| [Observability](https://hub.docker.com/r/dellemc/csm-topology) | 1.1 | 1.1 | 1.0.1 | 1.0.1 |
-| [Replication](https://hub.docker.com/r/dellemc/dell-csi-replicator) | 1.2 | 1.2 | 1.1 | 1.0 |
-| [Resiliency](https://hub.docker.com/r/dellemc/podmon) | 1.1 | 1.1 | 1.0.1 | 1.0.1 |
-| [CSI Driver for PowerScale](https://hub.docker.com/r/dellemc/csi-isilon/tags) | v2.3 | v2.2 | v2.1 | v2.0 | 
-| [CSI Driver for Unity](https://hub.docker.com/r/dellemc/csi-unity/tags) | v2.3 | v2.2 | v2.1 | v2.0 |
-| [CSI Driver for PowerStore](https://hub.docker.com/r/dellemc/csi-powerstore/tags) | v2.3 | v2.2 | v2.1 | v2.0 |
-| [CSI Driver for PowerFlex](https://hub.docker.com/r/dellemc/csi-vxflexos/tags) | v2.3 | v2.2 | v2.1 | v2.0 |
-| [CSI Driver for PowerMax](https://hub.docker.com/r/dellemc/csi-powermax/tags) | v2.3 | v2.2 | v2.1 | v2.0 |
+| [Authorization](https://hub.docker.com/r/dellemc/csm-authorization-sidecar) | 1.2 | 1.1 | 1.0 | 1.0 |
+| [Observability](https://hub.docker.com/r/dellemc/csm-topology) | 1.1 | 1.0.1 | 1.0.1 | 1.0 |
+| [Replication](https://hub.docker.com/r/dellemc/dell-csi-replicator) | 1.2 | 1.1 | 1.0 | 1.0 |
+| [Resiliency](https://hub.docker.com/r/dellemc/podmon) | 1.1 | 1.0.1 | 1.0.1 | 1.0 |
+| [CSI Driver for PowerScale](https://hub.docker.com/r/dellemc/csi-isilon/tags) | v2.2 | v2.1 | v2.0 | v2.0 | 
+| [CSI Driver for Unity](https://hub.docker.com/r/dellemc/csi-unity/tags) | v2.2 | v2.1 | v2.0 | v2.0 |
+| [CSI Driver for PowerStore](https://hub.docker.com/r/dellemc/csi-powerstore/tags) | v2.2 | v2.1 | v2.0 | v2.0 |
+| [CSI Driver for PowerFlex](https://hub.docker.com/r/dellemc/csi-vxflexos/tags) | v2.2 | v2.1 | v2.0 | v2.0 |
+| [CSI Driver for PowerMax](https://hub.docker.com/r/dellemc/csi-powermax/tags) | v2.2 | v2.1 | v2.0 | v2.0 |

content/docs/authorization/_index.md

@@ -53,9 +53,9 @@ CSM for Authorization supports the following CSI drivers and versions.
 {{<table "table table-striped table-bordered table-sm">}}
 | Storage Array | CSI Driver | Supported Versions |
 | ------------- | ---------- | ------------------ |
-| CSI Driver for Dell PowerFlex | [csi-powerflex](https://github.com/dell/csi-powerflex) | v2.0 + |
-| CSI Driver for Dell PowerMax | [csi-powermax](https://github.com/dell/csi-powermax) | v2.0 + |
-| CSI Driver for Dell PowerScale | [csi-powerscale](https://github.com/dell/csi-powerscale) | v2.0 + |
+| CSI Driver for Dell PowerFlex | [csi-powerflex](https://github.com/dell/csi-powerflex) | v2.0, v2.1, v2.2 |
+| CSI Driver for Dell PowerMax | [csi-powermax](https://github.com/dell/csi-powermax) | v2.0, v2.1 ,v2.2 |
+| CSI Driver for Dell PowerScale | [csi-powerscale](https://github.com/dell/csi-powerscale) | v2.0, v2.1, v2.2 |
 {{</table>}}
 
 **NOTE:** If the deployed CSI driver has a number of controller pods equal to the number of schedulable nodes in your cluster, CSM for Authorization may not be able to inject properly into the driver's controller pod.

content/docs/csidriver/_index.md

@@ -34,7 +34,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 {{<table "table table-striped table-bordered table-sm">}}
 | Features                 | PowerMax | PowerFlex | Unity  | PowerScale | PowerStore |
 |--------------------------|:--------:|:---------:|:------:|:----------:|:----------:|
-| CSI Driver version       | 2.3.0    | 2.3.0     | 2.3.0  | 2.3.0      | 2.3.0      |
+| CSI Driver version       | 2.2.0    | 2.2.0     | 2.2.0  | 2.2.0      | 2.2.0      |
 | Static Provisioning      | yes      | yes       | yes    | yes        | yes        |
 | Dynamic Provisioning     | yes      | yes       | yes    | yes        | yes        |
 | Expand Persistent Volume | yes      | yes       | yes    | yes        | yes        |

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

@@ -120,7 +120,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
 ## Install the Driver
 
 **Steps**
-1. Run `git clone -b v2.3.0 https://github.com/dell/csi-powerscale.git` to clone the git repository.
+1. Run `git clone -b v2.2.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*.
 4. Copy *the helm/csi-isilon/values.yaml* into a new location with name say *my-isilon-settings.yaml*, to customize settings for installation.

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

@@ -109,7 +109,7 @@ kubectl create -f deploy/kubernetes/snapshot-controller
 ## Install the Driver
 
 **Steps**
-1. Run `git clone -b v2.3.0 https://github.com/dell/csi-powerflex.git` to clone the git repository.
+1. Run `git clone -b v2.2.0 https://github.com/dell/csi-powerflex.git` to clone the git repository.
 
 2. Ensure that you have created a namespace where you want to install the driver. You can run `kubectl create namespace vxflexos` to create a new one.
 

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

@@ -162,7 +162,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
 
 **Steps**
 
-1. Run `git clone -b v2.3.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.2.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, 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:

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

@@ -174,7 +174,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
 ## Install the Driver
 
 **Steps**
-1. Run `git clone -b v2.3.0 https://github.com/dell/csi-powerstore.git` to clone the git repository.
+1. Run `git clone -b v2.2.0 https://github.com/dell/csi-powerstore.git` to clone the git repository.
 2. Ensure that you have created namespace where you want to install the driver. You can run `kubectl create namespace csi-powerstore` to create a new one. "csi-powerstore" is just an example. You can choose any name for the namespace.
    But make sure to align to the same namespace during the whole installation.
 3. Check `helm/csi-powerstore/driver-image.yaml` and confirm the driver image points to new image.

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

@@ -39,7 +39,7 @@ Install CSI Driver for Unity using this procedure.
 
 *Before you begin*
 
- * You must have the downloaded files, including the Helm chart from the source [git repository](https://github.com/dell/csi-unity) with the command ```git clone -b v2.3.0 https://github.com/dell/csi-unity.git```, as a pre-requisite for running this procedure.
+ * You must have the downloaded files, including the Helm chart from the source [git repository](https://github.com/dell/csi-unity) with the command ```git clone -b v2.2.0 https://github.com/dell/csi-unity.git```, as a pre-requisite for running this procedure.
  * In the top-level dell-csi-helm-installer directory, there should be two scripts, `csi-install.sh` and `csi-uninstall.sh`.
  * Ensure _unity_ namespace exists in Kubernetes cluster. Use the `kubectl create namespace unity` command to create the namespace if the namespace is not present.
 

content/docs/csidriver/installation/operator/_index.md

@@ -275,7 +275,7 @@ The below notes explain some of the general items to take care of.
 1. If you are trying to upgrade the CSI driver from an older version, make sure to modify the _configVersion_ field if required.
    ```yaml
       driver:
-        configVersion: v2.3.0
+        configVersion: v2.2.0
    ```
 2. Volume Health Monitoring feature is optional and by default this feature is disabled for drivers when installed via operator.
    To enable this feature, we will have to modify the below block while upgrading the driver.To get the volume health state add 

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

@@ -159,12 +159,12 @@ metadata:
   namespace: test-vxflexos
 spec:
   driver:
-    configVersion: v2.3.0
+    configVersion: v2.2.0
     replicas: 1
     dnsPolicy: ClusterFirstWithHostNet
     forceUpdate: false
     common:
-      image: "dellemc/csi-vxflexos:v2.3.0"
+      image: "dellemc/csi-vxflexos:v2.2.0"
       imagePullPolicy: IfNotPresent
       envs:
         - name: X_CSI_VXFLEXOS_ENABLELISTVOLUMESNAPSHOT

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

@@ -199,8 +199,8 @@ metadata:
   namespace: test-powermax
 spec:
   driver:
-    # Config version for CSI PowerMax v2.3.0 driver
-    configVersion: v2.3.0
+    # Config version for CSI PowerMax v2.2.0 driver
+    configVersion: v2.2.0
     # replica: Define the number of PowerMax controller nodes
     # to deploy to the Kubernetes release
     # Allowed values: n, where n > 0
@@ -209,8 +209,8 @@ spec:
     dnsPolicy: ClusterFirstWithHostNet
     forceUpdate: false
     common:
-      # Image for CSI PowerMax driver v2.3.0
-      image: dellemc/csi-powermax:v2.3.0
+      # Image for CSI PowerMax driver v2.2.0
+      image: dellemc/csi-powermax:v2.2.0
       # imagePullPolicy: Policy to determine if the image should be pulled prior to starting the container.
       # Allowed values:
       #  Always: Always pull the image.

content/docs/csidriver/installation/operator/powerstore.md

@@ -69,13 +69,13 @@ metadata:
   namespace: test-powerstore
 spec:
   driver:
-    configVersion: v2.3.0
+    configVersion: v2.2.0
     replicas: 2
     dnsPolicy: ClusterFirstWithHostNet
     forceUpdate: false
     fsGroupPolicy: ReadWriteOnceWithFSType
     common:
-      image: "dellemc/csi-powerstore:v2.3.0"
+      image: "dellemc/csi-powerstore:v2.2.0"
       imagePullPolicy: IfNotPresent
       envs:
         - name: X_CSI_POWERSTORE_NODE_NAME_PREFIX

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

@@ -97,12 +97,12 @@ metadata:
   namespace: test-unity
 spec:
   driver:
-    configVersion: v2.3.0
+    configVersion: v2.2.0
     replicas: 2
     dnsPolicy: ClusterFirstWithHostNet
     forceUpdate: false
     common:
-      image: "dellemc/csi-unity:v2.3.0"
+      image: "dellemc/csi-unity:v2.2.0"
       imagePullPolicy: IfNotPresent
     sideCars:
       - name: provisioner

content/docs/csidriver/release/powerflex.md

@@ -3,9 +3,11 @@ title: PowerFlex
 description: Release notes for PowerFlex CSI driver
 ---
 
-## Release Notes - CSI PowerFlex v2.3.0
+## Release Notes - CSI PowerFlex v2.2.0
 
 ### New Features/Changes
+- Added support for Kubernetes 1.23.
+- Added support for Amazon Elastic Kubernetes Service Anywhere.
 
 ### Fixed Issues
 

content/docs/csidriver/release/powermax.md

@@ -3,10 +3,12 @@ title: PowerMax
 description: Release notes for PowerMax CSI driver
 ---
 
-## Release Notes - CSI PowerMax v2.3.0
+## Release Notes - CSI PowerMax v2.2.0
 
 ### New Features/Changes
-- Updated deprecated StorageClass parameter fsType with csi.storage.k8s.io/fstype.
+- Added support for new access modes in CSI Spec 1.5.
+- Added support for Volume Health Monitoring.
+- Added support for Kubernetes 1.23.
 
 ### Fixed Issues
 There are no fixed issues in this release.

content/docs/csidriver/release/powerscale.md

@@ -3,10 +3,14 @@ title: PowerScale
 description: Release notes for PowerScale CSI driver
 ---
 
-## Release Notes - CSI Driver for PowerScale v2.3.0
+## Release Notes - CSI Driver for PowerScale v2.2.0
 
 ### New Features/Changes
 
+- Added support for Replication.
+- Added support for Kubernetes 1.23.
+- Added support to configure fsGroupPolicy.
+- Added support for session based authentication along with basic authentication for PowerScale.
 
 ### Fixed Issues
 

content/docs/csidriver/release/powerstore.md

@@ -3,11 +3,14 @@ title: PowerStore
 description: Release notes for PowerStore CSI driver
 ---
 
-## Release Notes - CSI PowerStore v2.3.0
+## Release Notes - CSI PowerStore v2.2.0
 
 ### New Features/Changes
 
-
+- Added support for NVMe/TCP protocol.
+- Added support for Kubernetes 1.23.
+- Added support to configure fsGroupPolicy.
+- Added support for configuring permissions using POSIX mode bits and NFSv4 ACLs on NFS mount directory. 
 
 ### Fixed Issues
 

content/docs/csidriver/release/unity.md

@@ -3,10 +3,12 @@ title: Unity
 description: Release notes for Unity CSI driver
 ---
 
-## Release Notes - CSI Unity v2.3.0
+## Release Notes - CSI Unity v2.2.0
 
 ### New Features/Changes
 
+- Added support for Kubernetes 1.23.
+- Added support for Standalone Helm Charts.
 
 ### Fixed Issues
 

content/docs/csidriver/troubleshooting/powerflex.md

@@ -19,7 +19,6 @@ description: Troubleshooting PowerFlex Driver
 | When you run the command `kubectl apply -f snapclass-v1.yaml`, you get the error `error: unable to recognize "snapclass-v1.yaml": no matches for kind "VolumeSnapshotClass" in version "snapshot.storage.k8s.io/v1"` | Check to make sure that the v1 snapshotter CRDs are installed, and not the v1beta1 CRDs, which are no longer supported. |
 | The controller pod is stuck and producing errors such as" `Failed to watch *v1.VolumeSnapshotContent: failed to list *v1.VolumeSnapshotContent: the server could not find the requested resource (get volumesnapshotcontents.snapshot.storage.k8s.io)` | Make sure that v1 snapshotter CRDs and v1 snapclass are installed, and not v1beta1, which is no longer supported. |
 | 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.21.0 <= 1.23.0 which is incompatible with Kubernetes V1.21.11-mirantis-1` | If you are using an extended Kubernetes version, please see the helm Chart at `helm/csi-vxflexos/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. |
-| Volume metrics are missing | Enable [Volume Health Monitoring](../../features/powerflex#volume-health-monitoring) |
 
 >*Note*: `vxflexos-controller-*` is the controller pod that acquires leader lease
 

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

@@ -8,12 +8,12 @@ Description: Upgrade PowerScale CSI driver
 ---
 You can upgrade the CSI Driver for Dell PowerScale using Helm or Dell CSI Operator.
 
-## Upgrade Driver from version 2.2.0 to 2.3.0 using Helm
+## Upgrade Driver from version 2.1.0 to 2.2.0 using Helm
 
 **Note:** While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.
 
 **Steps**
-1. Clone the repository using `git clone -b v2.3.0 https://github.com/dell/csi-powerscale.git`, copy the helm/csi-isilon/values.yaml into a new location with a custom name say _my-isilon-settings.yaml_, to customize settings for installation. Edit _my-isilon-settings.yaml_ as per the requirements.
+1. Clone the repository using `git clone -b v2.2.0 https://github.com/dell/csi-powerscale.git`, copy the helm/csi-isilon/values.yaml into a new location with a custom name say _my-isilon-settings.yaml_, to customize settings for installation. Edit _my-isilon-settings.yaml_ as per the requirements.
 2. Change to directory dell-csi-helm-installer to install the Dell PowerScale `cd dell-csi-helm-installer`
 3. Upgrade the CSI Driver for Dell PowerScale using following command:
 

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

@@ -10,9 +10,9 @@ Description: Upgrade PowerFlex CSI driver
 
 You can upgrade the CSI Driver for Dell PowerFlex using Helm or Dell CSI Operator.
 
-## Update Driver from v2.2 to v2.3 using Helm 
+## Update Driver from v2.1 to v2.2 using Helm 
 **Steps**
-1. Run `git clone -b v2.3.0 https://github.com/dell/csi-powerflex.git` to clone the git repository and get the v2.3.0 driver.
+1. Run `git clone -b v2.2.0 https://github.com/dell/csi-powerflex.git` to clone the git repository and get the v2.2.0 driver.
 2. You need to create config.yaml with the configuration of your system.
    Check this section in installation documentation:  [Install the Driver](../../../installation/helm/powerflex#install-the-driver)
    You must set the only system managed in v1.5/v2.0/v2.1 driver as default in config.json in v2.2 so that the driver knows the existing volumes belong to that system.

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

@@ -10,10 +10,10 @@ Description: Upgrade PowerMax CSI driver
 
 You can upgrade CSI Driver for Dell PowerMax using Helm or Dell CSI Operator.
 
-## Update Driver from v2.2 to v2.3 using Helm
+## Update Driver from v2.1 to v2.2 using Helm
 
 **Steps**
-1. Run `git clone -b v2.3.0 https://github.com/dell/csi-powermax.git` to clone the git repository and get the v2.3 driver.
+1. Run `git clone -b v2.2.0 https://github.com/dell/csi-powermax.git` to clone the git repository and get the v2.2 driver.
 2. Update the values file as needed.
 2. Run the `csi-install` script with the option _\-\-upgrade_ by running: `cd ../dell-csi-helm-installer && ./csi-install.sh --namespace powermax --values ./my-powermax-settings.yaml --upgrade`.
 

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

@@ -9,12 +9,12 @@ Description: Upgrade PowerStore CSI driver
 
 You can upgrade the CSI Driver for Dell PowerStore using Helm or Dell CSI Operator.
 
-## Update Driver from v2.2 to v2.3 using Helm
+## Update Driver from v2.1 to v2.2 using Helm
 
 Note: While upgrading the driver via helm, controllerCount variable in myvalues.yaml can be at most one less than the number of worker nodes.
 
 **Steps**
-1. Run `git clone -b v2.3.0 https://github.com/dell/csi-powerstore.git` to clone the git repository and get the driver.
+1. Run `git clone -b v2.2.0 https://github.com/dell/csi-powerstore.git` to clone the git repository and get the driver.
 2. Edit `helm/config.yaml` file and configure connection information for your PowerStore arrays changing the following parameters:
     - *endpoint*: defines the full URL path to the PowerStore API.
     - *globalID*: specifies what storage cluster the driver should use  

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

@@ -20,9 +20,9 @@ You can upgrade the CSI Driver for Dell Unity using Helm or Dell CSI Operator.
 
 Preparing myvalues.yaml is the same as explained in the install section.
 
-To upgrade the driver from csi-unity v2.2 to csi-unity 2.3
+To upgrade the driver from csi-unity v2.1 to csi-unity 2.2
 
-1. Get the latest csi-unity 2.3 code from Github using using `git clone -b v2.3.0 https://github.com/dell/csi-unity.git`.
+1. Get the latest csi-unity 2.2 code from Github using using `git clone -b v2.2.0 https://github.com/dell/csi-unity.git`.
 2. Create myvalues.yaml.
 3. Copy the helm/csi-unity/values.yaml to the new location csi-unity/dell-csi-helm-installer with name say myvalues.yaml, to customize settings for installation edit myvalues.yaml as per the requirements.
 4. Navigate to common-helm-installer folder and execute the following command: