From 68d07cef548f4e5cab19770d664c6879b7a51ef4 Mon Sep 17 00:00:00 2001
From: Chiman Jain <chimanjain15@gmail.com>
Date: Thu, 6 Jun 2024 14:49:39 +0530
Subject: [PATCH 1/7] restructure observability module upgrade docs

---
 content/docs/deployment/csmoperator/_index.md | 41 +------------------
 .../csmoperator/modules/observability.md      | 38 ++++++++++++++++-
 2 files changed, 39 insertions(+), 40 deletions(-)

diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md
index fb482693af..04b1b242fb 100644
--- a/content/docs/deployment/csmoperator/_index.md
+++ b/content/docs/deployment/csmoperator/_index.md
@@ -363,46 +363,9 @@ The following notes explain some of the general items to take care of.
         configVersion: v2.10.0
    ```
 
-### Upgrade Observability module using Dell CSM Operator
+### Upgrade Modules using Dell CSM Operator
 
-The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource.
-
-* Modifying the existing driver and module installation directly via `kubectl edit`
-
-  ```sh
-  $ kubectl get <driver-object> -n <driver-namespace>
-  ```
-
-  For example - If the CSI PowerScale driver is installed then run this command to get the object name
-
-  ```sh
-  # Replace driver-namespace with the namespace where the CSI PowerScale driver is installed
-  $ kubectl get csm -n <driver-namespace>
-  ```
-
-  use the object name in `kubectl edit` command.
-
-  ```sh
-  $ kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
-  ```
-
-  For example - If the object name is isilon then use the name as isilon
-
-  ```sh
-  # Replace object-name with the isilon
-  $ kubectl edit csm isilon -n <driver-namespace>
-  ```
-
-* Modify the installation
-
-  * Update the driver config version and image tag
-
-  * Update the Observability config version, csm-topology image and the driver metrics images(e.g. for CSI PowerScale driver, the metrics driver image would be `csm-metrics-powerscale`)
-
->NOTE:
-
-* In observability module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current observability version is `v1.7.x`, it can be upgraded to `1.8.x`.
-* Upgrade to csm-operator and csi-driver first which support the corresponding observability module version.
+* Refer [Upgrade Obsevability Module](./modules/observability/#upgrade-observability) to upgrade the Observability Module via Operator
 
 ## Custom Resource Definitions
 As part of the Dell CSM Operator installation, a CRD representing configuration for the CSI Driver and CSM Modules is also installed.
diff --git a/content/docs/deployment/csmoperator/modules/observability.md b/content/docs/deployment/csmoperator/modules/observability.md
index c26586255a..2e03727bd0 100644
--- a/content/docs/deployment/csmoperator/modules/observability.md
+++ b/content/docs/deployment/csmoperator/modules/observability.md
@@ -59,4 +59,40 @@ The CSM Observability module for supported Dell CSI Drivers can be installed via
 
 ## Upgrade Observability
 
-- To upgrade observability module, please check the following section: [Upgrade Observability module using Dell CSM Operator](../../#upgrade-observability-module-using-dell-csm-operator)
+The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource.
+
+- Modifying the existing driver and module installation directly via `kubectl edit`
+
+  ```sh
+  kubectl get <driver-object> -n <driver-namespace>
+  ```
+
+  For example - If the CSI PowerScale driver is installed then run this command to get the object name
+
+  ```sh
+  # Replace driver-namespace with the namespace where the CSI PowerScale driver is installed
+  $ kubectl get csm -n <driver-namespace>
+  ```
+
+  use the object name in `kubectl edit` command.
+
+  ```sh
+  kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
+  ```
+
+  For example - If the object name is isilon then use the name as isilon
+
+  ```sh
+  # Replace object-name with the isilon
+  kubectl edit csm isilon -n <driver-namespace>
+  ```
+
+- Modify the installation
+
+  - Update the driver config version and image tag
+  - Update the Observability config version, csm-topology image and the driver metrics images(e.g. for CSI PowerScale driver, the metrics driver image would be `csm-metrics-powerscale`)
+
+>NOTE:
+
+- In observability module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current observability version is `v1.7.x`, it can be upgraded to `1.8.x`.
+- Upgrade to csm-operator and csi-driver first which support the corresponding observability module version.

From e988117f669ad89f6d7b8853d7ad6857869bb9e7 Mon Sep 17 00:00:00 2001
From: Kakde <kshitija_kakde@dell.com>
Date: Fri, 7 Jun 2024 12:55:22 +0530
Subject: [PATCH 2/7] steps for Authorization upgrade added

---
 .../csmoperator/modules/authorization.md      | 73 +++++++++++++++++++
 1 file changed, 73 insertions(+)

diff --git a/content/docs/deployment/csmoperator/modules/authorization.md b/content/docs/deployment/csmoperator/modules/authorization.md
index 2db1d421a4..cb737d7b9e 100644
--- a/content/docs/deployment/csmoperator/modules/authorization.md
+++ b/content/docs/deployment/csmoperator/modules/authorization.md
@@ -144,3 +144,76 @@ Follow the instructions available in CSM Authorization for [Configuring the CSM
 ### Configure a Dell CSI Driver with CSM Authorization
 
 Follow the instructions available in CSM Authorization for [Configuring a Dell CSI Driver with CSM for Authorization](../../../helm/modules/installation/authorization/#configuring-a-dell-csi-driver-with-csm-for-authorization).
+
+### Upgrade CSM Authorization
+
+This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:
+1) Upgrading the Authorization proxy server
+2) Upgrading CSI Driver , Authorization sidecar with Authorization module enabled
+
+
+- Upgrading the Authorization Proxy Server
+
+  Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
+  kubectl get <csm-object> -n <module-namespace>
+  ```
+
+  For example - If the Authorization Proxy Server is installed then run this command to get the object name
+
+  ```sh
+  # Replace module-namespace with the namespace where the Authorization Proxy Server is installed
+  $ kubectl get csm -n <module-namespace>
+  ```
+
+  use the object name in `kubectl edit` command.
+
+  ```sh
+  kubectl edit csm <object-name> -n <module-namespace>
+  ```
+
+  For example - If the object name is authorization then use the name as authorization
+
+  ```sh
+  # Replace object-name with the authorization
+  kubectl edit csm authorization -n <module-namespace>
+
+  - Update the CSM Authorization Proxy Server configVersion  
+  - Update the images for proxyService, tenantService, roleService and storageService
+
+
+- Upgrading CSI Driver , Authorization sidecar with Authorization module enabled
+
+  Modifying the existing driver and module installation directly via `kubectl edit`
+
+  ```sh
+  kubectl get <driver-object> -n <driver-namespace>
+  ```
+
+  For example - If the CSI PowerFlex driver is installed then run this command to get the object name
+
+  ```sh
+  # Replace driver-namespace with the namespace where the CSI PowerFlex driver is installed
+  $ kubectl get csm -n <driver-namespace>
+  ```
+
+  use the object name in `kubectl edit` command.
+
+  ```sh
+  kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
+  ```
+
+  For example - If the object name is vxflexos then use the name as vxflexos
+
+  ```sh
+  # Replace object-name with the vxflexos
+  kubectl edit csm vxflexos -n <driver-namespace>
+  ```
+
+- Modify the installation
+
+  - Update the driver config version and image tag
+  - Update the Authorization config version and karavi-authorization-proxy image.
+
+>NOTE:
+
+- In Authorization module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current observability version is `v1.8.x`, it can be upgraded to `1.9.x`.

From b5aa8b14f8404559614477efba3de5706ab51fea Mon Sep 17 00:00:00 2001
From: Kakde <kshitija_kakde@dell.com>
Date: Fri, 7 Jun 2024 13:06:59 +0530
Subject: [PATCH 3/7] steps for Authorization upgrade added

---
 .../docs/deployment/csmoperator/modules/authorization.md    | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

diff --git a/content/docs/deployment/csmoperator/modules/authorization.md b/content/docs/deployment/csmoperator/modules/authorization.md
index cb737d7b9e..b8ce4060ec 100644
--- a/content/docs/deployment/csmoperator/modules/authorization.md
+++ b/content/docs/deployment/csmoperator/modules/authorization.md
@@ -154,7 +154,9 @@ This section outlines the upgrade steps for Container Storage Modules (CSM) for
 
 - Upgrading the Authorization Proxy Server
 
-  Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
+   Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
+ 
+  ```sh
   kubectl get <csm-object> -n <module-namespace>
   ```
 
@@ -177,6 +179,8 @@ This section outlines the upgrade steps for Container Storage Modules (CSM) for
   # Replace object-name with the authorization
   kubectl edit csm authorization -n <module-namespace>
 
+- Modify the installation
+
   - Update the CSM Authorization Proxy Server configVersion  
   - Update the images for proxyService, tenantService, roleService and storageService
 

From 71186fee920d07262fd38d7b002b01e7e02ae317 Mon Sep 17 00:00:00 2001
From: Kakde <kshitija_kakde@dell.com>
Date: Fri, 7 Jun 2024 13:18:47 +0530
Subject: [PATCH 4/7] link to authorization module added

---
 content/docs/deployment/csmoperator/_index.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md
index 04b1b242fb..12692bd810 100644
--- a/content/docs/deployment/csmoperator/_index.md
+++ b/content/docs/deployment/csmoperator/_index.md
@@ -367,6 +367,8 @@ The following notes explain some of the general items to take care of.
 
 * Refer [Upgrade Obsevability Module](./modules/observability/#upgrade-observability) to upgrade the Observability Module via Operator
 
+* Refer [Upgrade Authorization Module](./modules/authorization/#upgrade-csm-authorization) to upgrade the Authorization Module via Operator
+
 ## Custom Resource Definitions
 As part of the Dell CSM Operator installation, a CRD representing configuration for the CSI Driver and CSM Modules is also installed.
 `containerstoragemodule` CRD is installed in API Group `storage.dell.com`.

From 53195396cee2a4afb1607b3189208c97d6382126 Mon Sep 17 00:00:00 2001
From: Kakde <kshitija_kakde@dell.com>
Date: Fri, 7 Jun 2024 17:50:00 +0530
Subject: [PATCH 5/7] review comments addressed

---
 .../csmoperator/modules/authorization.md      | 87 +++++++++----------
 1 file changed, 42 insertions(+), 45 deletions(-)

diff --git a/content/docs/deployment/csmoperator/modules/authorization.md b/content/docs/deployment/csmoperator/modules/authorization.md
index b8ce4060ec..c8b831286a 100644
--- a/content/docs/deployment/csmoperator/modules/authorization.md
+++ b/content/docs/deployment/csmoperator/modules/authorization.md
@@ -149,74 +149,71 @@ Follow the instructions available in CSM Authorization for [Configuring a Dell C
 
 This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:
 1) Upgrading the Authorization proxy server
-2) Upgrading CSI Driver , Authorization sidecar with Authorization module enabled
+2) Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
 
 
-- Upgrading the Authorization Proxy Server
+## Upgrading the Authorization Proxy Server
 
-   Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
- 
-  ```sh
-  kubectl get <csm-object> -n <module-namespace>
-  ```
+  1. Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
+  
+    ```sh
+    kubectl get csm -n <module-namespace>
+    ```
 
-  For example - If the Authorization Proxy Server is installed then run this command to get the object name
+    For example - If the Authorization Proxy Server is installed in authorization namespace then run this command to get the object name
 
-  ```sh
-  # Replace module-namespace with the namespace where the Authorization Proxy Server is installed
-  $ kubectl get csm -n <module-namespace>
-  ```
+    ```sh
+    $ kubectl get csm -n authorization
+    ```
 
-  use the object name in `kubectl edit` command.
+    use the object name in `kubectl edit` command.
 
-  ```sh
-  kubectl edit csm <object-name> -n <module-namespace>
-  ```
+    ```sh
+    kubectl edit csm <object-name> -n <module-namespace>
+    ```
 
-  For example - If the object name is authorization then use the name as authorization
+    For example - If the object name is authorization then use the name as authorization and if the namespace is authorization, then run this command to edit the object
 
-  ```sh
-  # Replace object-name with the authorization
-  kubectl edit csm authorization -n <module-namespace>
+    ```sh
+    kubectl edit csm authorization -n authorization
+    ```
 
-- Modify the installation
+  2. Modify the installation
 
-  - Update the CSM Authorization Proxy Server configVersion  
-  - Update the images for proxyService, tenantService, roleService and storageService
+    - Update the CSM Authorization Proxy Server configVersion  
+    - Update the images for proxyService, tenantService, roleService and storageService
 
 
-- Upgrading CSI Driver , Authorization sidecar with Authorization module enabled
+## Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
 
-  Modifying the existing driver and module installation directly via `kubectl edit`
+  1. Modifying the existing driver and module installation directly via `kubectl edit`
 
-  ```sh
-  kubectl get <driver-object> -n <driver-namespace>
-  ```
+    ```sh
+    kubectl get <driver-object> -n <driver-namespace>
+    ```
 
-  For example - If the CSI PowerFlex driver is installed then run this command to get the object name
+    For example - If the CSI PowerFlex driver is installed in vxflexos namepace then run this command to get the object name
 
-  ```sh
-  # Replace driver-namespace with the namespace where the CSI PowerFlex driver is installed
-  $ kubectl get csm -n <driver-namespace>
-  ```
+    ```sh
+    kubectl get csm -n vxflexos
+    ```
 
-  use the object name in `kubectl edit` command.
+    use the object name in `kubectl edit` command.
 
-  ```sh
-  kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
-  ```
+    ```sh
+    kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
+    ```
 
-  For example - If the object name is vxflexos then use the name as vxflexos
+    For example - If the object name is vxflexos then use the name as vxflexos and if the driver is installed in vxflexos namespace, then run this command to edit the object
 
-  ```sh
-  # Replace object-name with the vxflexos
-  kubectl edit csm vxflexos -n <driver-namespace>
-  ```
+    ```sh
+    kubectl edit csm vxflexos -n vxflexos
+    ```
 
-- Modify the installation
+  2. Modify the installation
 
-  - Update the driver config version and image tag
-  - Update the Authorization config version and karavi-authorization-proxy image.
+    - Update the driver config version and image tag
+    - Update the Authorization config version and karavi-authorization-proxy image.
 
 >NOTE:
 

From 681b0a1f68b7e71f5eb39a2df48567e89d82f574 Mon Sep 17 00:00:00 2001
From: Kakde <kshitija_kakde@dell.com>
Date: Mon, 10 Jun 2024 14:49:36 +0530
Subject: [PATCH 6/7] sign commit

---
 config.toml                                   |  2 +-
 .../csm-versions/default-values.properties    |  2 +-
 .../csminstallationwizard/src/index.html      |  8 +-
 .../src/static/js/constants.js                |  6 +-
 .../src/static/js/tests/generate-yaml.test.js |  6 +-
 .../src/static/js/tests/ui-functions.test.js  | 10 +-
 .../src/static/js/tests/utility.test.js       |  6 +-
 .../src/static/js/ui-functions.js             | 16 +--
 .../templates/helm/csm-1.11.0-values.template | 76 +++++++--------
 .../operator/csm-isilon-1.11.0.template       | 20 ++--
 .../operator/csm-powermax-1.11.0.template     | 14 +--
 .../operator/csm-powerstore-1.11.0.template   |  6 +-
 content/docs/deployment/csmoperator/_index.md | 21 ++--
 .../csmoperator/modules/authorization.md      | 97 ++++++++++---------
 .../csmoperator/modules/observability.md      | 26 ++---
 15 files changed, 163 insertions(+), 153 deletions(-)

diff --git a/config.toml b/config.toml
index ad977d6d2a..919f68ed82 100644
--- a/config.toml
+++ b/config.toml
@@ -176,7 +176,7 @@ enable = false
   url = "https://dell.github.io/csm-docs/docs/"
 
 [[params.versions]]
-  version = "v1.10.0"
+  version = "v1.10.2"
   url = "https://dell.github.io/csm-docs/v1"
 
 [[params.versions]]
diff --git a/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties b/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties
index 61fd4afa52..7ec130a487 100644
--- a/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties
+++ b/content/docs/deployment/csminstallationwizard/src/csm-versions/default-values.properties
@@ -1,4 +1,4 @@
-csmVersion=1.10.1
+csmVersion=1.11.0
 imageRepository=dellemc
 controllerCount=1
 nodeSelectorLabel=node-role.kubernetes.io/control-plane:
diff --git a/content/docs/deployment/csminstallationwizard/src/index.html b/content/docs/deployment/csminstallationwizard/src/index.html
index 6cebdb07d0..df2597bfd4 100644
--- a/content/docs/deployment/csminstallationwizard/src/index.html
+++ b/content/docs/deployment/csminstallationwizard/src/index.html
@@ -90,10 +90,10 @@
                     <div class="col-sm-9"></div>
                     <div class="col-sm-3">
                       <select id="csm-version" class="form-select" onchange="onCSMVersionChange(); validateInput(validateForm, CONSTANTS)" required>
-                        <option value="1.7.0">CSM 1.7</option>
-                        <option value="1.8.0">CSM 1.8</option>                        
-                        <option value="1.9.3">CSM 1.9</option>
-                        <option value="1.10.1" selected>CSM 1.10.1</option>
+                        <option value="1.8.0">CSM 1.8</option>
+                        <option value="1.9.3">CSM 1.9</option>                        
+                        <option value="1.10.2">CSM 1.10</option>
+                        <option value="1.11.0" selected>CSM 1.11</option>
                       </select>
                     </div>
                   </div>
diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js
index b4975024fd..c11ae18901 100644
--- a/content/docs/deployment/csminstallationwizard/src/static/js/constants.js
+++ b/content/docs/deployment/csminstallationwizard/src/static/js/constants.js
@@ -40,10 +40,10 @@ const CONSTANTS = {
 	PROPERTIES: ".properties",
 	HELM: "helm",
 	OPERATOR: "operator",
-	CSM_HELM_V170: "1.0.0",
 	CSM_HELM_V180: "1.1.0",
-	CSM_HELM_V190: "1.2.1",
-	CSM_HELM_V1101: "1.3.1",
+	CSM_HELM_V190: "1.2.2",
+	CSM_HELM_V1102: "1.3.2",
+	CSM_HELM_V1110: "1.4.0",
 	HELM_TAINTS: `
      - key: "$KEY"
        operator: "Exists"
diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js b/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js
index d3f86ca24f..44164efc64 100644
--- a/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js
+++ b/content/docs/deployment/csminstallationwizard/src/static/js/tests/generate-yaml.test.js
@@ -42,10 +42,10 @@ const CONSTANTS = {
 	PROPERTIES: ".properties",
 	HELM: "helm",
 	OPERATOR: "operator",
-	CSM_HELM_V170: "1.0.0",
 	CSM_HELM_V180: "1.1.0",
-	CSM_HELM_V190: "1.2.0",
-	CSM_HELM_V1100: "1.3.0",
+	CSM_HELM_V190: "1.2.2",
+	CSM_HELM_V1102: "1.3.2",
+	CSM_HELM_V1110: "1.4.0",
 	HELM_TAINTS: `
     - key: "$KEY"
       operator: "Exists"
diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js b/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js
index eb6e90a452..d4096b888c 100644
--- a/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js
+++ b/content/docs/deployment/csminstallationwizard/src/static/js/tests/ui-functions.test.js
@@ -68,10 +68,10 @@ const CONSTANTS = {
 	PROPERTIES: ".properties",
 	HELM: "helm",
 	OPERATOR: "operator",
-	CSM_HELM_V170: "1.0.0",
 	CSM_HELM_V180: "1.1.0",
-	CSM_HELM_V190: "1.2.0",
-	CSM_HELM_V1100: "1.3.0",
+	CSM_HELM_V190: "1.2.2",
+	CSM_HELM_V1102: "1.3.2",
+	CSM_HELM_V1110: "1.4.0",
 };
 
 describe("GIVEN onAuthorizationChange function", () => {
@@ -718,7 +718,7 @@ describe("GIVEN displayCommands function", () => {
 			<input id="array" value="powerstore">
 			<input id="installation-type" value="helm">
 			<input type="text" id="driver-namespace" value="csi-powerstore">
-			<input type="text" id="csm-version" value="1.7.0">
+			<input type="text" id="csm-version" value="1.8.0">
             <div id="command-text-area" style="display:none">
                 <div id="command-title"></div>
                 <span id="command-note" style="display:none"></span>
@@ -733,7 +733,7 @@ describe("GIVEN displayCommands function", () => {
 		expect($("#command-title").text()).toEqual("Run the following commands to install");
 		expect($("#command-note").text()).toEqual("Ensure that the namespaces and secrets are created before installing the helm chart");
 		expect($("#command1").text()).toEqual("helm repo add dell https://dell.github.io/helm-charts");
-		expect($("#command2").text()).toEqual("helm install powerstore dell/container-storage-modules -n csi-powerstore --version 1.0.0 -f values.yaml");
+		expect($("#command2").text()).toEqual("helm install powerstore dell/container-storage-modules -n csi-powerstore --version 1.1.0 -f values.yaml");
 	});
 
 	test("SHOULD show expected commands: Installation Type: Operator", () => {
diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/tests/utility.test.js b/content/docs/deployment/csminstallationwizard/src/static/js/tests/utility.test.js
index ec53d7a6e2..3d068b187e 100644
--- a/content/docs/deployment/csminstallationwizard/src/static/js/tests/utility.test.js
+++ b/content/docs/deployment/csminstallationwizard/src/static/js/tests/utility.test.js
@@ -45,10 +45,10 @@ const CONSTANT_PARAM = {
 	PROPERTIES: ".properties",
 	HELM: "helm",
 	OPERATOR: "operator",
-	CSM_HELM_V170: "1.0.0",
 	CSM_HELM_V180: "1.1.0",
-	CSM_HELM_V190: "1.2.0",
-	CSM_HELM_V1100: "1.3.0",
+	CSM_HELM_V190: "1.2.2",
+	CSM_HELM_V1102: "1.3.2",
+	CSM_HELM_V1110: "1.4.0",
 	HELM_TAINTS: `
      - key: "$KEY"
        operator: "Exists"
diff --git a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js
index e6cc6af39b..f8dd87d6cb 100644
--- a/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js
+++ b/content/docs/deployment/csminstallationwizard/src/static/js/ui-functions.js
@@ -470,20 +470,20 @@ function displayCommands(releaseNameValue, commandTitleValue, commandNoteValue,
 	installationType = document.getElementById("installation-type").value
 	var helmChartVersion;
 	switch (csmVersion) {
-		case "1.7.0":
-			helmChartVersion = CONSTANTS.CSM_HELM_V170;
-			break;
 		case "1.8.0":
 			helmChartVersion = CONSTANTS.CSM_HELM_V180;
 			break;
-		case "1.9.3":
-			helmChartVersion = CONSTANTS.CSM_HELM_V193;
+		case "1.9.0":
+			helmChartVersion = CONSTANTS.CSM_HELM_V190;
+			break;
+		case "1.10.2":
+			helmChartVersion = CONSTANTS.CSM_HELM_V1102;
 			break;
-		case "1.10.1":
-			helmChartVersion = CONSTANTS.CSM_HELM_V1101;
+		case "1.11.0":
+			helmChartVersion = CONSTANTS.CSM_HELM_V1100;
 			break;
 		default:
-			helmChartVersion = CONSTANTS.CSM_HELM_V1101;
+			helmChartVersion = CONSTANTS.CSM_HELM_V1100;
 			break;
 	}
 	$("#command-text-area").show();
diff --git a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template
index b76d70d6eb..caa436626a 100644
--- a/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template
+++ b/content/docs/deployment/csminstallationwizard/src/templates/helm/csm-1.11.0-values.template
@@ -9,18 +9,18 @@ csi-powerstore:
     # "driver" defines the container image, used for the driver container.
     driver: dellemc/csi-powerstore:v2.11.0
     # CSI sidecars
-    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0
-    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0
-    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1
-    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0
-    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0
-    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0
+    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.6.0
+    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v5.0.0
+    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v8.0.0
+    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.11.0
+    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0
+    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.12.0
 
     # CSM sidecars
     replication: dellemc/dell-csi-replicator:v1.9.0
-    vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0
+    vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.6.0
     podmon: dellemc/podmon:v1.10.0
-    metadataretriever: dellemc/csi-metadata-retriever:v1.6.0
+    metadataretriever: dellemc/csi-metadata-retriever:v1.8.0
   ## Controller ATTRIBUTES
   controller:
     controllerCount: $CONTROLLER_COUNT
@@ -118,17 +118,17 @@ csi-powermax:
   images:
     # "driver" defines the container image, used for the driver container.
     driver: dellemc/csi-powermax:v2.11.0
-    csireverseproxy: dellemc/csipowermax-reverseproxy:v2.9.0
+    csireverseproxy: dellemc/csipowermax-reverseproxy:v2.10.0
     # CSI sidecars
-    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0
-    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0
-    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1
-    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0
-    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0
-    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0
+    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.6.0
+    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v5.0.0
+    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v8.0.0
+    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.11.0
+    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0
+    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.12.0
     # CSM sidecars
     replication: dellemc/dell-csi-replicator:v1.9.0
-    authorization: dellemc/csm-authorization-sidecar:v1.10.0
+    authorization: dellemc/csm-authorization-sidecar:v1.11.0
     migration: dellemc/dell-csi-migrator:v1.3.0
     noderescan: dellemc/dell-csi-node-rescanner:v1.2.0
   clusterPrefix: $POWERMAX_CLUSTER_PREFIX
@@ -223,17 +223,17 @@ csi-vxflexos:
     # "powerflexSdc" defines the SDC image for init container.
     powerflexSdc: dellemc/sdc:4.5
     # CSI sidecars
-    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0
-    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0
-    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1
-    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0
-    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0
-    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0
+    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.6.0
+    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v5.0.0
+    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v8.0.0
+    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.11.0
+    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0
+    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.12.0
     # CSM sidecars
     replication: dellemc/dell-csi-replicator:v1.9.0
-    vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.4.0
+    vgsnapshotter: dellemc/csi-volumegroup-snapshotter:v1.6.0
     podmon: dellemc/podmon:v1.10.0
-    authorization: dellemc/csm-authorization-sidecar:v1.10.0
+    authorization: dellemc/csm-authorization-sidecar:v1.11.0
   certSecretCount: $CERT_SECRET_COUNT
   controller:
     replication:
@@ -320,17 +320,17 @@ csi-isilon:
     # "driver" defines the container image, used for the driver container.
     driver: dellemc/csi-isilon:v2.11.0
     # CSI sidecars
-    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0
-    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0
-    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1
-    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0
-    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0
-    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0
+    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.6.0
+    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v5.0.0
+    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v8.0.0
+    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.11.0
+    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0
+    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.12.0
     # CSM sidecars
     replication: dellemc/dell-csi-replicator:v1.9.0
     podmon: dellemc/podmon:v1.10.0
-    authorization: dellemc/csm-authorization-sidecar:v1.10.0
-    metadataretriever: dellemc/csi-metadata-retriever:v1.4.0
+    authorization: dellemc/csm-authorization-sidecar:v1.11.0
+    metadataretriever: dellemc/csi-metadata-retriever:v1.8.0
     encryption: dellemc/csm-encryption:v0.3.0
 
   certSecretCount: $CERT_SECRET_COUNT
@@ -430,12 +430,12 @@ csi-unity:
     # "driver" defines the container image, used for the driver container.
     driver: dellemc/csi-unity:v2.11.0
     # CSI sidecars
-    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.5.0
-    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v4.0.0
-    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v7.0.1
-    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.10.0
-    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.10.0
-    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.11.0
+    attacher: registry.k8s.io/sig-storage/csi-attacher:v4.6.0
+    provisioner: registry.k8s.io/sig-storage/csi-provisioner:v5.0.0
+    snapshotter: registry.k8s.io/sig-storage/csi-snapshotter:v8.0.0
+    resizer: registry.k8s.io/sig-storage/csi-resizer:v1.11.0
+    registrar: registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.0
+    healthmonitor: registry.k8s.io/sig-storage/csi-external-health-monitor-controller:v0.12.0
     # CSM sidecars
     podmon: dellemc/podmon:v1.10.0
   certSecretCount: $CERT_SECRET_COUNT
diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template
index 1b2266edfb..5bc5d912c4 100644
--- a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template
+++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-isilon-1.11.0.template
@@ -165,11 +165,11 @@ spec:
       # Leave as blank to consider all nodes
       # Allowed values: map of key-value pairs
       # Default value: None
-      nodeSelector:$CONTROLLER_POD_NODE_SELECTOR
+      nodeSelector: $CONTROLLER_POD_NODE_SELECTOR
 
       # tolerations: Define tolerations for the controller deployment, if required.
       # Default value: None
-      tolerations:$CONTROLLER_TOLERATIONS
+      tolerations: $CONTROLLER_TOLERATIONS
 
     node:
       envs:
@@ -212,11 +212,11 @@ spec:
       # Leave as blank to consider all nodes
       # Allowed values: map of key-value pairs
       # Default value: None
-      nodeSelector:$NODE_POD_NODE_SELECTOR
+      nodeSelector: $NODE_POD_NODE_SELECTOR
 
       # tolerations: Define tolerations for the node daemonset, if required.
       # Default value: None
-      tolerations:$NODE_TOLERATIONS
+      tolerations: $NODE_TOLERATIONS
       # - key: "node.kubernetes.io/memory-pressure"
       #   operator: "Exists"
       #   effect: "NoExecute"
@@ -245,10 +245,10 @@ spec:
     - name: authorization
       # enable: Enable/Disable csm-authorization
       enabled: $AUTHORIZATION_ENABLED
-      configVersion: v1.10.0
+      configVersion: v1.11.0
       components:
       - name: karavi-authorization-proxy
-        image: dellemc/csm-authorization-sidecar:v1.10.0
+        image: dellemc/csm-authorization-sidecar:v1.11.0
         envs:
           # proxyHost: hostname of the csm-authorization server
           - name: "PROXY_HOST"
@@ -289,7 +289,7 @@ spec:
       - name: dell-replication-controller-manager
         # image: Defines controller image. This shouldn't be changed
         # Allowed values: string
-        image: dellemc/dell-replication-controller:v1.7.0
+        image: dellemc/dell-replication-controller:v1.9.0
         envs:
           # TARGET_CLUSTERS_IDS: comma separated list of cluster IDs of the targets clusters. DO NOT include the source(wherever CSM Operator is deployed) cluster ID
           # Set the value to "self" in case of stretched/single cluster configuration
@@ -321,14 +321,14 @@ spec:
     - name: observability
       # enabled: Enable/Disable observability
       enabled: $OBSERVABILITY_OPERATOR_ENABLED
-      configVersion: v1.7.0
+      configVersion: v1.9.0
       components:
         - name: topology
           # enabled: Enable/Disable topology
           enabled: $OBSERVABILITY_OPERATOR_TOPOLOGY
           # image: Defines karavi-topology image. This shouldn't be changed
           # Allowed values: string
-          image: dellemc/csm-topology:v1.7.0
+          image: dellemc/csm-topology:v1.9.0
           envs:
             # topology log level
             # Valid values: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, PANIC
@@ -362,7 +362,7 @@ spec:
           enabled: $OBSERVABILITY_OPERATOR_METRICS
           # image: Defines PowerScale metrics image. This shouldn't be changed
           # Allowed values: string
-          image: dellemc/csm-metrics-powerscale:v1.4.0
+          image: dellemc/csm-metrics-powerscale:v1.6.0
           envs:
             # POWERSCALE_MAX_CONCURRENT_QUERIES: set the default max concurrent queries to PowerScale
             # Allowed values: int
diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template
index 55264ee3af..ac38800db8 100644
--- a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template
+++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powermax-1.11.0.template
@@ -232,14 +232,14 @@ spec:
     - name: csireverseproxy
       # enabled: Always set to true
       enabled: true
-      configVersion: v2.9.0
+      configVersion: v2.10.0
       forceRemoveModule: true
       components:
       - name: csipowermax-reverseproxy
       # image: Define the container images used for the reverse proxy
       # Default value: None
-      # Example: "csipowermax-reverseproxy:v2.9.0"
-        image: dellemc/csipowermax-reverseproxy:v2.9.0
+      # Example: "csipowermax-reverseproxy:v2.10.0"
+        image: dellemc/csipowermax-reverseproxy:v2.10.0
         envs:
           # "tlsSecret" defines the TLS secret that is created with certificate
           # and its associated key
@@ -299,7 +299,7 @@ spec:
       - name: dell-replication-controller-manager
         # image: Defines controller image. This shouldn't be changed
         # Allowed values: string
-        image: dellemc/dell-replication-controller:v1.7.0
+        image: dellemc/dell-replication-controller:v1.9.0
         envs:
           # TARGET_CLUSTERS_IDS: comma separated list of cluster IDs of the targets clusters. DO NOT include the source(wherever CSM Operator is deployed) cluster ID
           # Set the value to "self" in case of stretched/single cluster configuration
@@ -330,14 +330,14 @@ spec:
     - name: observability
       # enabled: Enable/Disable observability
       enabled: $OBSERVABILITY_OPERATOR_ENABLED
-      configVersion: v1.7.0
+      configVersion: v1.9.0
       components:
       - name: topology
         # enabled: Enable/Disable topology
         enabled: $OBSERVABILITY_OPERATOR_TOPOLOGY
         # image: Defines karavi-topology image. This shouldn't be changed
         # Allowed values: string
-        image: dellemc/csm-topology:v1.7.0
+        image: dellemc/csm-topology:v1.9.0
         envs:
           # topology log level
           # Valid values: TRACE, DEBUG, INFO, WARN, ERROR, FATAL, PANIC
@@ -362,7 +362,7 @@ spec:
         # enabled: Enable/Disable PowerMax metrics
         enabled: $OBSERVABILITY_OPERATOR_METRICS
         # image: Defines PowerMax metrics image. This shouldn't be changed
-        image: dellemc/csm-metrics-powermax:v1.2.0
+        image: dellemc/csm-metrics-powermax:v1.4.0
         envs:
           # POWERMAX_MAX_CONCURRENT_QUERIES: set the default max concurrent queries to PowerMax
           # Allowed values: int
diff --git a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template
index 0a357fef38..3eeb1c1519 100644
--- a/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template
+++ b/content/docs/deployment/csminstallationwizard/src/templates/operator/csm-powerstore-1.11.0.template
@@ -114,7 +114,7 @@ spec:
       # tolerations: Define tolerations for the controllers, if required.
       # Leave as blank to install controller on worker nodes
       # Default value: None
-      tolerations:$CONTROLLER_TOLERATIONS
+      tolerations: $CONTROLLER_TOLERATIONS
 
     node:
       envs:
@@ -141,12 +141,12 @@ spec:
       # Leave as blank to consider all nodes
       # Allowed values: map of key-value pairs
       # Default value: None
-      nodeSelector:$NODE_POD_NODE_SELECTOR
+      nodeSelector: $NODE_POD_NODE_SELECTOR
 
       # tolerations: Define tolerations for the controllers, if required.
       # Leave as blank to install controller on worker nodes
       # Default value: None
-      tolerations:$NODE_TOLERATIONS
+      tolerations: $NODE_TOLERATIONS
   
   modules:
     - name: resiliency
diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md
index 12692bd810..08843758e9 100644
--- a/content/docs/deployment/csmoperator/_index.md
+++ b/content/docs/deployment/csmoperator/_index.md
@@ -337,21 +337,22 @@ git clone -b v1.5.0 https://github.com/dell/csm-operator.git
 The CSI Drivers installed by the Dell CSM Operator can be updated like any Kubernetes resource.
 * Modifying the installation directly via `kubectl edit`
     ```
-    $ kubectl get <driver-object> -n <driver-namespace>
+    $ kubectl get csm -n <driver-namespace>
     ```
-    For example - If the CSI PowerStore driver is installed then run this command to get the object name
+    For example - If the CSI PowerStore driver is installed in powerstore namespace, then run this command to get the object name
     ```
-    # Replace driver-namespace with the namespace where the CSI PowerStore driver is installed
-    $ kubectl get csm -n <driver-namespace>
+    
+    $ kubectl get csm -n powerstore
     ```
     use the object name in `kubectl edit` command.
     ```
-    $ kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
+    
+    $ kubectl edit csm <object-name> -n <driver-namespace>
     ```
-    For example - If the object name is powerstore then use the name as powerstore
+    For example - If the object name is powerstore and the driver is installed in powerstore namespace, then run this command to edit the object name
     ```
-    # Replace object-name with the powerstore
-    $ kubectl edit csm powerstore -n <driver-namespace>
+    
+    $ kubectl edit csm powerstore -n powerstore
     ```
     and modify the installation. The usual fields to edit are the version of drivers, sidecars and the environment variables.
 The following notes explain some of the general items to take care of.
@@ -365,9 +366,9 @@ The following notes explain some of the general items to take care of.
 
 ### Upgrade Modules using Dell CSM Operator
 
-* Refer [Upgrade Obsevability Module](./modules/observability/#upgrade-observability) to upgrade the Observability Module via Operator
+* Refer [Upgrade Obsevability Module](modules/observability/#upgrade-observability) to upgrade the Observability Module via Operator
 
-* Refer [Upgrade Authorization Module](./modules/authorization/#upgrade-csm-authorization) to upgrade the Authorization Module via Operator
+* Refer [Upgrade Authorization Module](modules/authorization/#upgrade-csm-authorization) to upgrade the Authorization Module via Operator
 
 ## Custom Resource Definitions
 As part of the Dell CSM Operator installation, a CRD representing configuration for the CSI Driver and CSM Modules is also installed.
diff --git a/content/docs/deployment/csmoperator/modules/authorization.md b/content/docs/deployment/csmoperator/modules/authorization.md
index c8b831286a..3e1bbc9614 100644
--- a/content/docs/deployment/csmoperator/modules/authorization.md
+++ b/content/docs/deployment/csmoperator/modules/authorization.md
@@ -145,76 +145,83 @@ Follow the instructions available in CSM Authorization for [Configuring the CSM
 
 Follow the instructions available in CSM Authorization for [Configuring a Dell CSI Driver with CSM for Authorization](../../../helm/modules/installation/authorization/#configuring-a-dell-csi-driver-with-csm-for-authorization).
 
-### Upgrade CSM Authorization
+## Upgrade CSM Authorization
 
 This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:
-1) Upgrading the Authorization proxy server
-2) Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
+1. Upgrading the Authorization proxy server
+2. Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
 
+### Upgrading the Authorization Proxy Server
 
-## Upgrading the Authorization Proxy Server
-
-  1. Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
+1. Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
   
-    ```sh
-    kubectl get csm -n <module-namespace>
-    ```
+   ```sh
 
-    For example - If the Authorization Proxy Server is installed in authorization namespace then run this command to get the object name
+   kubectl get csm -n <module-namespace>
+   ```
 
-    ```sh
-    $ kubectl get csm -n authorization
-    ```
+   For example - If the Authorization Proxy Server is installed in authorization namespace, then run this command to get the object name
 
-    use the object name in `kubectl edit` command.
+   ```sh
+    
+   kubectl get csm -n authorization
+   ```
 
-    ```sh
-    kubectl edit csm <object-name> -n <module-namespace>
-    ```
+   use the object name in `kubectl edit` command.
 
-    For example - If the object name is authorization then use the name as authorization and if the namespace is authorization, then run this command to edit the object
+   ```sh
 
-    ```sh
-    kubectl edit csm authorization -n authorization
-    ```
+   kubectl edit csm <object-name> -n <module-namespace>
+   ```
 
-  2. Modify the installation
+   If the object name is authorization and the proxy server is installed in authorization namespace, then run this command to edit the object
 
-    - Update the CSM Authorization Proxy Server configVersion  
-    - Update the images for proxyService, tenantService, roleService and storageService
+   ```sh
 
+   kubectl edit csm authorization -n authorization
+   ```
 
-## Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
+2. Modify the installation
 
-  1. Modifying the existing driver and module installation directly via `kubectl edit`
+   - Update the CSM Authorization Proxy Server configVersion  
+   - Update the images for proxyService, tenantService, roleService and storageService
 
-    ```sh
-    kubectl get <driver-object> -n <driver-namespace>
-    ```
 
-    For example - If the CSI PowerFlex driver is installed in vxflexos namepace then run this command to get the object name
+### Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
 
-    ```sh
-    kubectl get csm -n vxflexos
-    ```
+1. Modifying the existing driver and module installation directly via `kubectl edit`
 
-    use the object name in `kubectl edit` command.
+   ```sh
 
-    ```sh
-    kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
-    ```
+   kubectl get csm -n <driver-namespace>
+   ```
 
-    For example - If the object name is vxflexos then use the name as vxflexos and if the driver is installed in vxflexos namespace, then run this command to edit the object
+   For example - If the CSI PowerFlex driver is installed in vxflexos namepace, then run this command to get the object name
 
-    ```sh
-    kubectl edit csm vxflexos -n vxflexos
-    ```
+   ```sh
+
+   kubectl get csm -n vxflexos
+   ```
+
+   use the object name in `kubectl edit` command.
+
+   ```sh
+
+   kubectl edit csm <object-name> -n <driver-namespace>
+   ```
+
+   For example - If the object name is vxflexos and the driver is installed in vxflexos namespace, then run this command to edit the object
+
+   ```sh
+
+   kubectl edit csm vxflexos -n vxflexos
+   ```
 
-  2. Modify the installation
+2. Modify the installation
 
-    - Update the driver config version and image tag
-    - Update the Authorization config version and karavi-authorization-proxy image.
+   - Update the driver config version and image.
+   - Update the Authorization config version and karavi-authorization-proxy image.
 
 >NOTE:
 
-- In Authorization module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current observability version is `v1.8.x`, it can be upgraded to `1.9.x`.
+- In Authorization module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current authorization version is `v1.8.x`, it can be upgraded to `1.9.x`.
\ No newline at end of file
diff --git a/content/docs/deployment/csmoperator/modules/observability.md b/content/docs/deployment/csmoperator/modules/observability.md
index 2e03727bd0..715c9466e3 100644
--- a/content/docs/deployment/csmoperator/modules/observability.md
+++ b/content/docs/deployment/csmoperator/modules/observability.md
@@ -61,36 +61,38 @@ The CSM Observability module for supported Dell CSI Drivers can be installed via
 
 The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource.
 
-- Modifying the existing driver and module installation directly via `kubectl edit`
+1. Modifying the existing driver and module installation directly via `kubectl edit`
 
   ```sh
-  kubectl get <driver-object> -n <driver-namespace>
+  
+  kubectl get csm -n <driver-namespace>
   ```
 
-  For example - If the CSI PowerScale driver is installed then run this command to get the object name
+  For example - If the CSI PowerScale driver is installed in isilon namespace, then run this command to get the object name
 
   ```sh
-  # Replace driver-namespace with the namespace where the CSI PowerScale driver is installed
-  $ kubectl get csm -n <driver-namespace>
+
+  kubectl get csm -n isilon
   ```
 
   use the object name in `kubectl edit` command.
 
   ```sh
-  kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
+
+  kubectl edit csm <object-name> -n <driver-namespace>
   ```
 
-  For example - If the object name is isilon then use the name as isilon
+  For example - If the object name is isilon and the driver is installed in isilon namespace, then run this command to edit the object
 
   ```sh
-  # Replace object-name with the isilon
-  kubectl edit csm isilon -n <driver-namespace>
+  
+  kubectl edit csm isilon -n isilon
   ```
 
-- Modify the installation
+2. Modify the installation
 
-  - Update the driver config version and image tag
-  - Update the Observability config version, csm-topology image and the driver metrics images(e.g. for CSI PowerScale driver, the metrics driver image would be `csm-metrics-powerscale`)
+  - Update the driver config version and image.
+  - Update the Observability config version, csm-topology image and the driver metrics images(e.g. for CSI PowerScale driver, the metrics driver image would be `csm-metrics-powerscale`).
 
 >NOTE:
 

From aab286f701668bcbb6af8dc51d482c756c091390 Mon Sep 17 00:00:00 2001
From: Kakde <kshitija_kakde@dell.com>
Date: Mon, 10 Jun 2024 15:19:11 +0530
Subject: [PATCH 7/7] sign commit

---
 content/docs/deployment/csmoperator/_index.md | 21 ++--
 .../csmoperator/modules/authorization.md      | 97 +++++++++----------
 .../csmoperator/modules/observability.md      | 26 +++--
 3 files changed, 67 insertions(+), 77 deletions(-)

diff --git a/content/docs/deployment/csmoperator/_index.md b/content/docs/deployment/csmoperator/_index.md
index 08843758e9..12692bd810 100644
--- a/content/docs/deployment/csmoperator/_index.md
+++ b/content/docs/deployment/csmoperator/_index.md
@@ -337,22 +337,21 @@ git clone -b v1.5.0 https://github.com/dell/csm-operator.git
 The CSI Drivers installed by the Dell CSM Operator can be updated like any Kubernetes resource.
 * Modifying the installation directly via `kubectl edit`
     ```
-    $ kubectl get csm -n <driver-namespace>
+    $ kubectl get <driver-object> -n <driver-namespace>
     ```
-    For example - If the CSI PowerStore driver is installed in powerstore namespace, then run this command to get the object name
+    For example - If the CSI PowerStore driver is installed then run this command to get the object name
     ```
-    
-    $ kubectl get csm -n powerstore
+    # Replace driver-namespace with the namespace where the CSI PowerStore driver is installed
+    $ kubectl get csm -n <driver-namespace>
     ```
     use the object name in `kubectl edit` command.
     ```
-    
-    $ kubectl edit csm <object-name> -n <driver-namespace>
+    $ kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
     ```
-    For example - If the object name is powerstore and the driver is installed in powerstore namespace, then run this command to edit the object name
+    For example - If the object name is powerstore then use the name as powerstore
     ```
-    
-    $ kubectl edit csm powerstore -n powerstore
+    # Replace object-name with the powerstore
+    $ kubectl edit csm powerstore -n <driver-namespace>
     ```
     and modify the installation. The usual fields to edit are the version of drivers, sidecars and the environment variables.
 The following notes explain some of the general items to take care of.
@@ -366,9 +365,9 @@ The following notes explain some of the general items to take care of.
 
 ### Upgrade Modules using Dell CSM Operator
 
-* Refer [Upgrade Obsevability Module](modules/observability/#upgrade-observability) to upgrade the Observability Module via Operator
+* Refer [Upgrade Obsevability Module](./modules/observability/#upgrade-observability) to upgrade the Observability Module via Operator
 
-* Refer [Upgrade Authorization Module](modules/authorization/#upgrade-csm-authorization) to upgrade the Authorization Module via Operator
+* Refer [Upgrade Authorization Module](./modules/authorization/#upgrade-csm-authorization) to upgrade the Authorization Module via Operator
 
 ## Custom Resource Definitions
 As part of the Dell CSM Operator installation, a CRD representing configuration for the CSI Driver and CSM Modules is also installed.
diff --git a/content/docs/deployment/csmoperator/modules/authorization.md b/content/docs/deployment/csmoperator/modules/authorization.md
index 3e1bbc9614..c8b831286a 100644
--- a/content/docs/deployment/csmoperator/modules/authorization.md
+++ b/content/docs/deployment/csmoperator/modules/authorization.md
@@ -145,83 +145,76 @@ Follow the instructions available in CSM Authorization for [Configuring the CSM
 
 Follow the instructions available in CSM Authorization for [Configuring a Dell CSI Driver with CSM for Authorization](../../../helm/modules/installation/authorization/#configuring-a-dell-csi-driver-with-csm-for-authorization).
 
-## Upgrade CSM Authorization
+### Upgrade CSM Authorization
 
 This section outlines the upgrade steps for Container Storage Modules (CSM) for Authorization. The upgrade of CSM for Authorization is handled in 2 parts:
-1. Upgrading the Authorization proxy server
-2. Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
+1) Upgrading the Authorization proxy server
+2) Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
 
-### Upgrading the Authorization Proxy Server
 
-1. Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
-  
-   ```sh
-
-   kubectl get csm -n <module-namespace>
-   ```
-
-   For example - If the Authorization Proxy Server is installed in authorization namespace, then run this command to get the object name
-
-   ```sh
-    
-   kubectl get csm -n authorization
-   ```
+## Upgrading the Authorization Proxy Server
 
-   use the object name in `kubectl edit` command.
-
-   ```sh
-
-   kubectl edit csm <object-name> -n <module-namespace>
-   ```
-
-   If the object name is authorization and the proxy server is installed in authorization namespace, then run this command to edit the object
+  1. Modifying the existing Authorization Proxy Server installation directly via `kubectl edit`
+  
+    ```sh
+    kubectl get csm -n <module-namespace>
+    ```
 
-   ```sh
+    For example - If the Authorization Proxy Server is installed in authorization namespace then run this command to get the object name
 
-   kubectl edit csm authorization -n authorization
-   ```
+    ```sh
+    $ kubectl get csm -n authorization
+    ```
 
-2. Modify the installation
+    use the object name in `kubectl edit` command.
 
-   - Update the CSM Authorization Proxy Server configVersion  
-   - Update the images for proxyService, tenantService, roleService and storageService
+    ```sh
+    kubectl edit csm <object-name> -n <module-namespace>
+    ```
 
+    For example - If the object name is authorization then use the name as authorization and if the namespace is authorization, then run this command to edit the object
 
-### Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
+    ```sh
+    kubectl edit csm authorization -n authorization
+    ```
 
-1. Modifying the existing driver and module installation directly via `kubectl edit`
+  2. Modify the installation
 
-   ```sh
+    - Update the CSM Authorization Proxy Server configVersion  
+    - Update the images for proxyService, tenantService, roleService and storageService
 
-   kubectl get csm -n <driver-namespace>
-   ```
 
-   For example - If the CSI PowerFlex driver is installed in vxflexos namepace, then run this command to get the object name
+## Upgrading CSI Driver, Authorization sidecar with Authorization module enabled
 
-   ```sh
+  1. Modifying the existing driver and module installation directly via `kubectl edit`
 
-   kubectl get csm -n vxflexos
-   ```
+    ```sh
+    kubectl get <driver-object> -n <driver-namespace>
+    ```
 
-   use the object name in `kubectl edit` command.
+    For example - If the CSI PowerFlex driver is installed in vxflexos namepace then run this command to get the object name
 
-   ```sh
+    ```sh
+    kubectl get csm -n vxflexos
+    ```
 
-   kubectl edit csm <object-name> -n <driver-namespace>
-   ```
+    use the object name in `kubectl edit` command.
 
-   For example - If the object name is vxflexos and the driver is installed in vxflexos namespace, then run this command to edit the object
+    ```sh
+    kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
+    ```
 
-   ```sh
+    For example - If the object name is vxflexos then use the name as vxflexos and if the driver is installed in vxflexos namespace, then run this command to edit the object
 
-   kubectl edit csm vxflexos -n vxflexos
-   ```
+    ```sh
+    kubectl edit csm vxflexos -n vxflexos
+    ```
 
-2. Modify the installation
+  2. Modify the installation
 
-   - Update the driver config version and image.
-   - Update the Authorization config version and karavi-authorization-proxy image.
+    - Update the driver config version and image tag
+    - Update the Authorization config version and karavi-authorization-proxy image.
 
 >NOTE:
 
-- In Authorization module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current authorization version is `v1.8.x`, it can be upgraded to `1.9.x`.
\ No newline at end of file
+- In Authorization module upgrade, only `n-1` to `n` upgrade is supported, e.g. if the current observability version is `v1.8.x`, it can be upgraded to `1.9.x`.
diff --git a/content/docs/deployment/csmoperator/modules/observability.md b/content/docs/deployment/csmoperator/modules/observability.md
index 715c9466e3..2e03727bd0 100644
--- a/content/docs/deployment/csmoperator/modules/observability.md
+++ b/content/docs/deployment/csmoperator/modules/observability.md
@@ -61,38 +61,36 @@ The CSM Observability module for supported Dell CSI Drivers can be installed via
 
 The Observability module installed by the Dell CSM Operator can be updated like any Kubernetes resource.
 
-1. Modifying the existing driver and module installation directly via `kubectl edit`
+- Modifying the existing driver and module installation directly via `kubectl edit`
 
   ```sh
-  
-  kubectl get csm -n <driver-namespace>
+  kubectl get <driver-object> -n <driver-namespace>
   ```
 
-  For example - If the CSI PowerScale driver is installed in isilon namespace, then run this command to get the object name
+  For example - If the CSI PowerScale driver is installed then run this command to get the object name
 
   ```sh
-
-  kubectl get csm -n isilon
+  # Replace driver-namespace with the namespace where the CSI PowerScale driver is installed
+  $ kubectl get csm -n <driver-namespace>
   ```
 
   use the object name in `kubectl edit` command.
 
   ```sh
-
-  kubectl edit csm <object-name> -n <driver-namespace>
+  kubectl edit csm <driver-object>/<object-name> -n <driver-namespace>
   ```
 
-  For example - If the object name is isilon and the driver is installed in isilon namespace, then run this command to edit the object
+  For example - If the object name is isilon then use the name as isilon
 
   ```sh
-  
-  kubectl edit csm isilon -n isilon
+  # Replace object-name with the isilon
+  kubectl edit csm isilon -n <driver-namespace>
   ```
 
-2. Modify the installation
+- Modify the installation
 
-  - Update the driver config version and image.
-  - Update the Observability config version, csm-topology image and the driver metrics images(e.g. for CSI PowerScale driver, the metrics driver image would be `csm-metrics-powerscale`).
+  - Update the driver config version and image tag
+  - Update the Observability config version, csm-topology image and the driver metrics images(e.g. for CSI PowerScale driver, the metrics driver image would be `csm-metrics-powerscale`)
 
 >NOTE: