From 64ba31f8b970618a5f94a27bf1980e20fb485370 Mon Sep 17 00:00:00 2001
From: Samihan Deshmukh <120082727+samihan-dell@users.noreply.github.com>
Date: Thu, 30 Mar 2023 11:16:17 +0530
Subject: [PATCH 01/13] Fixing UI improvements (#549)

* fix: Removing images list for old csm version

* fix: Adding missing images

* fix: Modified installation wizard top navbar identical to csm-docs navbar

* fix: Sticking navbar to top

* fix: Added UI as cluster prefix should be 3 letters

* fix: fixing logo redirection to home page

* style: aligning logo position to csm-docs logo position

* fix: fixing logo redirection to home page

* style: Keeping footer of installation wizard at bottom

* style: Aligned social links and adjusted fonts

* fix: Fixed linting issue

* fix: Refactored styling spacing
---
 .../src/csm-versions/csm-1.4.0.properties     |  6 ---
 .../src/csm-versions/csm-1.5.0.properties     |  6 ---
 .../src/csm-versions/csm-1.6.0.properties     |  2 +
 .../csminstallationwizard/src/index.html      | 46 +++++++++++--------
 .../src/static/css/style.css                  | 43 ++++++++++++++++-
 .../src/static/images/logo.svg                |  1 +
 6 files changed, 73 insertions(+), 31 deletions(-)
 delete mode 100644 content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.4.0.properties
 delete mode 100644 content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.5.0.properties
 create mode 100644 content/docs/deployment/csminstallationwizard/src/static/images/logo.svg
diff --git a/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.4.0.properties b/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.4.0.properties
deleted file mode 100644
index 2e9afb6e8c..0000000000
--- a/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.4.0.properties
+++ /dev/null
@@ -1,6 +0,0 @@
-driverVersion=v2.4.0
-vgsnapshotImage=csi-volumegroup-snapshotter:v1.1.0
-replicationImage=dell-csi-replicator:v1.3.0
-authorizationImage=csm-authorization-sidecar:v1.4.0
-migrationImage=dell-csi-migrator:v1.0.0
-powermaxCSIReverseProxyImage=csipowermax-reverseproxy:v2.3.0
diff --git a/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.5.0.properties b/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.5.0.properties
deleted file mode 100644
index 3fad6a924e..0000000000
--- a/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.5.0.properties
+++ /dev/null
@@ -1,6 +0,0 @@
-driverVersion=v2.5.0
-vgsnapshotImage=csi-volumegroup-snapshotter:v1.1.0
-replicationImage=dell-csi-replicator:v1.3.0
-authorizationImage=csm-authorization-sidecar:v1.5.0
-migrationImage=dell-csi-migrator:v1.0.0
-powermaxCSIReverseProxyImage=csipowermax-reverseproxy:v2.4.0
\ No newline at end of file
diff --git a/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.6.0.properties b/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.6.0.properties
index d242f20dfd..4b0b591d85 100644
--- a/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.6.0.properties
+++ b/content/docs/deployment/csminstallationwizard/src/csm-versions/csm-1.6.0.properties
@@ -4,4 +4,6 @@ replicationImage=dell-csi-replicator:v1.4.0
 podmonImage=podmon:v1.5.0
 authorizationImage=csm-authorization-sidecar:v1.6.0
 migrationImage=dell-csi-migrator:v1.1.0
+migrationNodeRescanSidecarImage=dell-csi-node-rescanner:v1.0.0
 powermaxCSIReverseProxyImage=csipowermax-reverseproxy:v2.5.0
+appMobilityVeleroPluginImage=csm-application-mobility-velero-plugin:v0.3.0
\ No newline at end of file
diff --git a/content/docs/deployment/csminstallationwizard/src/index.html b/content/docs/deployment/csminstallationwizard/src/index.html
index fcbf85ed90..98f94f8105 100644
--- a/content/docs/deployment/csminstallationwizard/src/index.html
+++ b/content/docs/deployment/csminstallationwizard/src/index.html
@@ -11,22 +11,19 @@
     <script type="text/javascript" src="static/js/bootstrap.bundle.min.js"></script>
   </head>
   <body>
-    <div class="container-fluid">
-      <header>
-        <div class="container-fluid td-outer">
-          <nav class="js-navbar-scroll navbar-dark flex-column flex-md-row ">
-            <p class="navbar-brand">
-              <span class="navbar-logo">
-                <img src="static/images/dell_logo.jpg" class="img">
-              </span>
-            </p>
-          </nav>
-        </div>
-      </header>
-      <hr>
-      <main class="container mt-5 mb-5">
+    <header class="fixed-top">
+      <nav class="installation-wizard-navbar">
+        <a href="/csm-docs">
+          <span>
+            <img src="static/images/logo.svg" class="img" alt="Dell Technologies logo">
+          </span>
+        </a>
+      </nav>
+    </header>
+    <div class="container-fluid pt-5 page-container">
+      <main class="container mt-5">
         <div class="row">
-          <div class="col-8 pl-md-5">
+          <div class="col-12 pl-md-5">
             <span class="heading">Container Storage Modules (CSM) Installation Wizard </span>
           </div>
           <div class="col-4"></div>
@@ -279,7 +276,7 @@
                       <label for="cluster-prefix" class="col-sm-2 col-form-label" data-bs-toggle="tooltip" data-bs-placement="right" title="Prefix that is used during the creation of various masking-related entities (Storage Groups, Masking Views, Hosts, and Volume Identifiers) on the array." style="width: 120px;">Cluster Prefix</label>
                       <div class="col-sm-9"></div>
                       <div class="was-validated col-sm-3">
-                        <input class="form-control input-lg" type="text" id="cluster-prefix" placeholder="Example: XYZ" maxlength="3" oninput="validateInput(validateForm, CONSTANTS)" required>
+                        <input class="form-control input-lg" type="text" id="cluster-prefix" placeholder="Example: XYZ" title="Please provide 3 letter cluster prefix" maxlength="3" oninput="validateInput(validateForm, CONSTANTS)" required>
                       </div>
                     </div>
                   </div>
@@ -454,17 +451,30 @@
           </div>
         </div>
       </main>
-      <footer class="bg-secondary py-5 row d-print-none">
+      <footer class="py-5 row d-print-none">
         <div class="container-fluid mx-sm-5">
           <div class="row">
             <div class="col-6 col-sm-4 text-xs-center order-sm-2"></div>
-            <div class="col-6 col-sm-4 text-right text-xs-center order-sm-3"></div>
             <div class="col-12 col-sm-4 text-center py-2 order-sm-2">
               <small class="text-white">&copy; 2023 The Dell Technologies All Rights Reserved</small>
               <small class="ml-1">
                 <a href="https://www.dell.com/learn/us/en/uscorp1/policies-privacy" target="_blank">Privacy Policy</a>
               </small>
             </div>
+            <div class="col-6 col-sm-4 text-right text-xs-center order-sm-3 text-align-right">
+              <ul class="list-inline mb-0">
+                <li class="list-inline-item mx-2 h3" data-toggle="tooltip" data-placement="top" title="" aria-label="GitHub" data-original-title="GitHub">
+                  <a class="text-white" target="_blank" href="https://github.com/dell/csm">
+                    <svg viewBox="0 0 496 512" height="24"><path d="M165.9 397.4c0 2-2.3 3.6-5.2 3.6-3.3.3-5.6-1.3-5.6-3.6 0-2 2.3-3.6 5.2-3.6 3-.3 5.6 1.3 5.6 3.6zm-31.1-4.5c-.7 2 1.3 4.3 4.3 4.9 2.6 1 5.6 0 6.2-2s-1.3-4.3-4.3-5.2c-2.6-.7-5.5.3-6.2 2.3zm44.2-1.7c-2.9.7-4.9 2.6-4.6 4.9.3 2 2.9 3.3 5.9 2.6 2.9-.7 4.9-2.6 4.6-4.6-.3-1.9-3-3.2-5.9-2.9zM244.8 8C106.1 8 0 113.3 0 252c0 110.9 69.8 205.8 169.5 239.2 12.8 2.3 17.3-5.6 17.3-12.1 0-6.2-.3-40.4-.3-61.4 0 0-70 15-84.7-29.8 0 0-11.4-29.1-27.8-36.6 0 0-22.9-15.7 1.6-15.4 0 0 24.9 2 38.6 25.8 21.9 38.6 58.6 27.5 72.9 20.9 2.3-16 8.8-27.1 16-33.7-55.9-6.2-112.3-14.3-112.3-110.5 0-27.5 7.6-41.3 23.6-58.9-2.6-6.5-11.1-33.3 2.6-67.9 20.9-6.5 69 27 69 27 20-5.6 41.5-8.5 62.8-8.5s42.8 2.9 62.8 8.5c0 0 48.1-33.6 69-27 13.7 34.7 5.2 61.4 2.6 67.9 16 17.7 25.8 31.5 25.8 58.9 0 96.5-58.9 104.2-114.8 110.5 9.2 7.9 17 22.9 17 46.4 0 33.7-.3 75.4-.3 83.6 0 6.5 4.6 14.4 17.3 12.1C428.2 457.8 496 362.9 496 252 496 113.3 383.5 8 244.8 8zM97.2 352.9c-1.3 1-1 3.3.7 5.2 1.6 1.6 3.9 2.3 5.2 1 1.3-1 1-3.3-.7-5.2-1.6-1.6-3.9-2.3-5.2-1zm-10.8-8.1c-.7 1.3.3 2.9 2.3 3.9 1.6 1 3.6.7 4.3-.7.7-1.3-.3-2.9-2.3-3.9-2-.6-3.6-.3-4.3.7zm32.4 35.6c-1.6 1.3-1 4.3 1.3 6.2 2.3 2.3 5.2 2.6 6.5 1 1.3-1.3.7-4.3-1.3-6.2-2.2-2.3-5.2-2.6-6.5-1zm-11.4-14.7c-1.6 1-1.6 3.6 0 5.9 1.6 2.3 4.3 3.3 5.6 2.3 1.6-1.3 1.6-3.9 0-6.2-1.4-2.3-4-3.3-5.6-2z"  fill="#ffffff"/></svg>
+                  </a>
+                </li>
+                <li class="list-inline-item mx-2 h3" data-toggle="tooltip" data-placement="top" title="" aria-label="Slack" data-original-title="Slack">
+                  <a class="text-white" target="_blank" href="http://del.ly/Slack_request">
+                    <svg viewBox="0 0 448 512" height="24"><path d="M94.12 315.1c0 25.9-21.16 47.06-47.06 47.06S0 341 0 315.1c0-25.9 21.16-47.06 47.06-47.06h47.06v47.06zm23.72 0c0-25.9 21.16-47.06 47.06-47.06s47.06 21.16 47.06 47.06v117.84c0 25.9-21.16 47.06-47.06 47.06s-47.06-21.16-47.06-47.06V315.1zm47.06-188.98c-25.9 0-47.06-21.16-47.06-47.06S139 32 164.9 32s47.06 21.16 47.06 47.06v47.06H164.9zm0 23.72c25.9 0 47.06 21.16 47.06 47.06s-21.16 47.06-47.06 47.06H47.06C21.16 243.96 0 222.8 0 196.9s21.16-47.06 47.06-47.06H164.9zm188.98 47.06c0-25.9 21.16-47.06 47.06-47.06 25.9 0 47.06 21.16 47.06 47.06s-21.16 47.06-47.06 47.06h-47.06V196.9zm-23.72 0c0 25.9-21.16 47.06-47.06 47.06-25.9 0-47.06-21.16-47.06-47.06V79.06c0-25.9 21.16-47.06 47.06-47.06 25.9 0 47.06 21.16 47.06 47.06V196.9zM283.1 385.88c25.9 0 47.06 21.16 47.06 47.06 0 25.9-21.16 47.06-47.06 47.06-25.9 0-47.06-21.16-47.06-47.06v-47.06h47.06zm0-23.72c-25.9 0-47.06-21.16-47.06-47.06 0-25.9 21.16-47.06 47.06-47.06h117.84c25.9 0 47.06 21.16 47.06 47.06 0 25.9-21.16 47.06-47.06 47.06H283.1z" fill="#ffffff"/></svg>
+                  </a>
+                </li>
+              </ul>
+            </div>
           </div>
         </div>
       </footer>
diff --git a/content/docs/deployment/csminstallationwizard/src/static/css/style.css b/content/docs/deployment/csminstallationwizard/src/static/css/style.css
index 8d57c42ad9..1dc478e69b 100644
--- a/content/docs/deployment/csminstallationwizard/src/static/css/style.css
+++ b/content/docs/deployment/csminstallationwizard/src/static/css/style.css
@@ -17,7 +17,7 @@
  */ 
   .img {
 	display: inline-block;
-	margin-top: 20px;
+	margin-top: 18px;
 	margin-right: 0px;
 	margin-left: 1%;
 	height: 30px;
@@ -114,4 +114,45 @@
 
   .child-level-one {
 	margin-left: 1em;
+  }
+
+  .installation-wizard-navbar {
+    background: #30638e;
+    min-height: 4rem;
+    z-index: 32;
+    width: 100%;
+    padding-left: 12px;
+  }
+
+  .page-container {
+    position: relative;
+    min-height: 100vh;
+  }
+
+  .text-align-right {
+    text-align: right;
+    padding-right: 100px;
+  }
+
+  body {
+    margin: 0;
+    font-family: "Open Sans", -apple-system, BlinkMacSystemFont, "Segoe UI", Roboto, "Helvetica Neue", Arial, sans-serif, "Apple Color Emoji", "Segoe UI Emoji", "Segoe UI Symbol";
+    font-size: 1rem;
+    font-weight: 400;
+    line-height: 1.5;
+    color: #222;
+    text-align: left;
+    background-color: #fff;
+  }
+
+  main {
+    padding-bottom: 150px;
+  }
+
+  footer {
+    background-color: #403f4c;
+    position: absolute;
+    bottom: 0;
+    width: 100%;
+    min-height: 150px;
   }
\ No newline at end of file
diff --git a/content/docs/deployment/csminstallationwizard/src/static/images/logo.svg b/content/docs/deployment/csminstallationwizard/src/static/images/logo.svg
new file mode 100644
index 0000000000..7918fba9fa
--- /dev/null
+++ b/content/docs/deployment/csminstallationwizard/src/static/images/logo.svg
@@ -0,0 +1 @@
+<svg id="Layer_1" data-name="Layer 1" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 1017 132"><defs><style>.cls-1{fill:#fff;}</style></defs><title>DellTech_Logo_Prm_Wht_rgb</title><path class="cls-1" d="M1015,84.89c0-12.23-6.8-17.66-20.39-20.38s-21.73-4.08-21.73-13.58c0-6.8,5.44-10.87,15-10.87,12.22,0,16.3,5.43,16.3,12.22l1.36,1.36h5.43l1.37-1.36c0-13.58-10.88-19-24.46-19-15,0-23.1,8.15-23.1,17.67,0,10.86,8.15,16.3,21.73,19s20.38,4.08,20.38,15c0,6.79-4.07,12.23-17.66,12.23-12.22,0-17.66-6.8-17.66-15l-1.35-1.36h-5.44l-1.35,1.36c0,12.23,9.5,21.74,25.8,21.74,17.66,0,25.82-8.15,25.82-19M956.58,71.31l1.36-1.37V65.87c0-19-10.87-32.61-29.89-32.61s-29.89,13.59-29.89,32.61v2.72c0,19,9.51,35.32,31.25,35.32,19,0,25.81-12.23,27.17-20.38l-1.36-1.36h-5.43l-1.36,1.36c-2.72,8.15-8.16,13.59-19,13.59-17.66,0-23.1-16.31-23.1-24.46l1.36-1.35Zm-8.15-6.8H907.67l-1.36-1.36c0-9.51,5.44-23.09,21.74-23.09s21.74,13.58,21.74,23.09Zm-59.78,36.68V36l-1.36-1.35h-5.43L880.5,36v65.22l1.36,1.36h5.43Zm0-78.8V14.24l-1.36-1.36h-5.43l-1.36,1.36v8.15l1.36,1.36h5.43ZM837,97.12c-13.59,0-21.74-9.52-21.74-28.53S823.44,40.06,837,40.06s21.73,9.5,21.73,28.53S850.61,97.12,837,97.12M858.76,93c0,17.66-4.07,31.25-20.38,31.25-12.22,0-16.3-5.44-17.66-12.23l-1.35-1.36h-5.44l-1.36,1.36c1.36,10.87,9.51,19,25.81,19,17.67,0,28.53-10.87,28.53-38V36l-1.35-1.35h-4.08L860.12,36l-1.36,8.16H857.4c-2.71-5.43-9.5-10.87-21.74-10.87-19,0-28.53,15-28.53,35.33s9.52,35.32,28.53,35.32c12.24,0,19-5.43,21.74-10.87Zm-88.3-53c13.58,0,23.09,10.87,23.09,28.53S784,97.12,770.46,97.12s-23.1-10.87-23.1-28.53,9.51-28.53,23.1-28.53m0,63.85c17.66,0,31.25-12.23,31.25-35.32s-13.59-35.33-31.25-35.33-31.25,12.23-31.25,35.33,13.59,35.32,31.25,35.32m-40.76-2.72V8.81l-1.36-1.36h-5.43l-1.36,1.36v92.38l1.36,1.36h5.43ZM680.8,40.06c13.58,0,23.09,10.87,23.09,28.53s-9.51,28.53-23.09,28.53-23.1-10.87-23.1-28.53,9.51-28.53,23.1-28.53m0,63.85c17.66,0,31.25-12.23,31.25-35.32S698.46,33.26,680.8,33.26s-31.25,12.23-31.25,35.33,13.59,35.32,31.25,35.32m-39.4-2.72V60.43c0-17.66-9.51-27.17-24.45-27.17-9.52,0-17.67,4.08-21.74,10.87h-1.36L592.49,36l-1.36-1.35h-4.08L585.7,36v65.22l1.35,1.36h5.44l1.36-1.36V64.51c0-15,6.79-24.45,21.73-24.45,10.87,0,17.66,6.79,17.66,20.37v40.76l1.37,1.36H640Zm-69.29,0V60.43c0-17.66-9.51-27.17-24.45-27.17-9.52,0-17.66,4.08-21.74,10.87h-1.36V8.81L523.2,7.45h-5.43l-1.36,1.36v92.38l1.36,1.36h5.43l1.36-1.36V64.51c0-15,6.8-24.45,21.74-24.45,10.87,0,17.66,6.79,17.66,20.37v40.76l1.36,1.36h5.44ZM455.28,68.59c0-19,9.5-28.53,23.09-28.53s19,8.15,20.38,16.29l1.35,1.37h5.44l1.36-1.37c-1.36-13.58-12.23-23.09-28.53-23.09-17.66,0-31.24,10.87-31.24,35.33s13.58,35.32,31.24,35.32c16.3,0,27.17-9.51,28.53-23.1l-1.36-1.36H500.1l-1.35,1.36C497.39,89,492,97.12,478.37,97.12s-23.09-9.52-23.09-28.53m-14.95,2.72,1.36-1.37V65.87c0-19-10.87-32.61-29.9-32.61s-29.88,13.59-29.88,32.61v2.72c0,19,9.51,35.32,31.25,35.32,19,0,25.81-12.23,27.17-20.38L439,82.17h-5.43l-1.36,1.36c-2.72,8.15-8.15,13.59-19,13.59-17.66,0-23.1-16.31-23.1-24.46l1.36-1.35Zm-8.15-6.8H391.42l-1.36-1.36c0-9.51,5.44-23.09,21.73-23.09s21.75,13.58,21.75,23.09ZM395.57,12.88V8.81l-1.36-1.36H323.56L322.2,8.81v4.07l1.36,1.36h29.89l1.36,1.36v85.59l1.36,1.36h5.43l1.36-1.36V15.6l1.36-1.36h29.89Z"/><path class="cls-1" d="M322.2,83.65v18.9H260.85V7.45h21.6v76.2ZM38.55,102.55A47.57,47.57,0,0,0,84.58,67l53.8,42,53.77-42v35.56H253.5V83.65H213.75V7.45h-21.6V43L140.58,83.3l-11.54-9L153.73,55l26.89-21L165.27,22,113.69,62.3l-11.53-9L153.73,13,138.38,1,84.58,43a47.57,47.57,0,0,0-46-35.58H0v95.1ZM21.6,83.65V26.35H38.55c14.33,0,26,12.83,26,28.65S52.88,83.65,38.55,83.65Z"/></svg>
\ No newline at end of file

From 4806add6fdd92c050e31da11996638b6988d7e2f Mon Sep 17 00:00:00 2001
From: Akshay Saini <109056238+AkshaySainiDell@users.noreply.github.com>
Date: Fri, 31 Mar 2023 14:50:57 +0530
Subject: [PATCH 02/13] Update release notes & upgrade steps (#553)

---
 content/docs/csidriver/release/powerstore.md           |  9 ++++++---
 .../docs/csidriver/upgradation/drivers/powerstore.md   | 10 ++++++++++
 2 files changed, 16 insertions(+), 3 deletions(-)

diff --git a/content/docs/csidriver/release/powerstore.md b/content/docs/csidriver/release/powerstore.md
index 28ebee50b1..a43b0bb493 100644
--- a/content/docs/csidriver/release/powerstore.md
+++ b/content/docs/csidriver/release/powerstore.md
@@ -9,10 +9,14 @@ description: Release notes for PowerStore CSI driver
 
 - [Added support for Resiliency](https://github.com/dell/csm/issues/587)
 - [Added support for Kubernetes 1.26](https://github.com/dell/csm/issues/597)
+- [Added support for MKE 3.6.x](https://github.com/dell/csm/issues/672)
+- [Added support for RKE 1.4.1](https://github.com/dell/csm/issues/670)
 
 ### Fixed Issues
 
-- [Fixed issue where driver was not properly cleaning up resources when volumes were unmounted](https://github.com/dell/csm/issues/666)
+- [Multiple iSCSI network support](https://github.com/dell/csm/issues/668)
+- [Create volume successful but unable to map volumes to a hosts](https://github.com/dell/csm/issues/599)
+- [Can't find IP in X_CSI_POWERSTORE_EXTERNAL_ACCESS for NFS provisioning](https://github.com/dell/csm/issues/689)
 
 ### Known Issues
 
@@ -25,5 +29,4 @@ description: Release notes for PowerStore CSI driver
 
 ### Note:
 
-- Support for Kubernetes alpha features like Volume Health Monitoring and RWOP (ReadWriteOncePod) access mode will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters.
-- This release is only supported when driver is installed via helm.
\ No newline at end of file
+- Support for Kubernetes alpha features like Volume Health Monitoring and RWOP (ReadWriteOncePod) access mode will not be available in Openshift environment as Openshift doesn't support enabling of alpha features for Production Grade clusters.
\ No newline at end of file
diff --git a/content/docs/csidriver/upgradation/drivers/powerstore.md b/content/docs/csidriver/upgradation/drivers/powerstore.md
index f44e02d6ee..5e757c955b 100644
--- a/content/docs/csidriver/upgradation/drivers/powerstore.md
+++ b/content/docs/csidriver/upgradation/drivers/powerstore.md
@@ -32,3 +32,13 @@ Note: While upgrading the driver via helm, controllerCount variable in myvalues.
 4. Create the secret by running ```kubectl create secret generic powerstore-config -n csi-powerstore --from-file=config=secret.yaml```
 5. Copy the default values.yaml file `cd dell-csi-helm-installer && cp ../helm/csi-powerstore/values.yaml ./my-powerstore-settings.yaml` and update parameters as per the requirement.
 6. Run the `csi-install` script with the option _\-\-upgrade_ by running: `./csi-install.sh --namespace csi-powerstore --values ./my-powerstore-settings.yaml --upgrade`.
+
+## Upgrade using Dell CSI Operator:
+
+**Notes:**
+1. While upgrading the driver via operator, replicas count in sample CR yaml can be at most one less than the number of worker nodes.
+2. Upgrading the Operator does not upgrade the CSI Driver.
+
+
+1. Please upgrade the Dell CSI Operator by following [here](./../operator).
+2. Once the operator is upgraded, to upgrade the driver, refer [here](./../../../installation/operator/#update-csi-drivers).
\ No newline at end of file

From 86f9bae173e4d3275ab4af8467b2afb18632557a Mon Sep 17 00:00:00 2001
From: Prasanna M <35757638+prablr79@users.noreply.github.com>
Date: Tue, 4 Apr 2023 19:28:57 +0530
Subject: [PATCH 03/13] Security Policy (#556)

---
 content/docs/securitypolicy/_index.md | 14 ++++++++++++++
 1 file changed, 14 insertions(+)
 create mode 100644 content/docs/securitypolicy/_index.md

diff --git a/content/docs/securitypolicy/_index.md b/content/docs/securitypolicy/_index.md
new file mode 100644
index 0000000000..5d3b3fb6c5
--- /dev/null
+++ b/content/docs/securitypolicy/_index.md
@@ -0,0 +1,14 @@
+---
+title: "Security Policy"
+linkTitle: "Security Policy"
+weight: 13
+Description: >
+  Dell Container Storage Modules (CSM) Security Policy
+---
+
+
+The CSM services/repositories are inspected for security vulnerabilities via [gosec](https://github.com/securego/gosec), 
+Instructions for reporting a vulnerability can be found on the [Dell Vulnerability Policy](https://www.dell.com/support/contents/en-in/article/product-support/self-support-knowledgebase/security-antivirus/alerts-vulnerabilities/dell-vulnerability-response-policy#:~:text=To%20report%20a%20security%20vulnerability%20or%20issue%20in%20Dell.com,instructions%20to%20reproduce%20the%20issue)
+
+
+CSM recommends to stay on the [lastest release](https://github.com/dell/csm/releases/latest) of Dell Container Storage Modules to take advantage of new features, enhancements, bug fixes, and security fixes.

From b29de03c0b5dc4103daa8071102c9e9118dac914 Mon Sep 17 00:00:00 2001
From: Yamunadevi N Shanmugam <82038610+shanmydell@users.noreply.github.com>
Date: Mon, 10 Apr 2023 18:41:44 +0530
Subject: [PATCH 04/13] updated troubleshooting doc (#558)

---
 content/docs/csidriver/troubleshooting/powermax.md | 1 +
 1 file changed, 1 insertion(+)

diff --git a/content/docs/csidriver/troubleshooting/powermax.md b/content/docs/csidriver/troubleshooting/powermax.md
index 960491a02a..b2e9802ce5 100644
--- a/content/docs/csidriver/troubleshooting/powermax.md
+++ b/content/docs/csidriver/troubleshooting/powermax.md
@@ -17,3 +17,4 @@ description: Troubleshooting PowerMax Driver
 |`FailedPrecondition desc = no topology keys could be generate`| Make sure that FC or iSCSI connectivity to the arrays are proper |
 | CreateHost failed with error `initiator is already part of different host.` | Update modifyHostName to true in values.yaml Or Remove the initiator from existing host |
 | `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. | 

From ed64551c47269bbeefd903009ae97865a1ec52a2 Mon Sep 17 00:00:00 2001
From: HarishH-DELL <109663924+HarishH-DELL@users.noreply.github.com>
Date: Tue, 18 Apr 2023 11:30:28 +0530
Subject: [PATCH 05/13] Multi array support documentation improvements (#575)

* Multi array support documentation improvements

* renamed sc name
---
 .../csidriver/installation/helm/isilon.md     | 46 +++++++++++++++++++
 1 file changed, 46 insertions(+)

diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md
index b7888484fa..438360ea1e 100644
--- a/content/docs/csidriver/installation/helm/isilon.md
+++ b/content/docs/csidriver/installation/helm/isilon.md
@@ -296,6 +296,52 @@ Deleting a storage class has no impact on a running Pod with mounted PVCs. You c
 
 >Note: If you continue to use the old storage classes, you may not be able to take advantage of any new storage class parameter supported by the driver.
 
+**Steps to create secondary storage class:**
+
+There are samples storage class yaml files available under `samples/storageclass`.  These can be copied and modified as needed. 
+
+1. Copy the `storageclass.yaml` to `second_storageclass.yaml` ( This is just an example, you can rename to file you require. )
+2. Edit the  `second_storageclass.yaml` yaml file and update following parameters:
+- Update the `name` parameter to you require 
+    ````yaml
+    metadata:
+      name: isilon-new
+  ````
+- Cluster name of 2nd array looks like this in the secret file.( Under `/samples/secret/secret.yaml`)
+  ````yaml
+                  - clusterName: "cluster2"
+                    username: "user name"
+                    password: "Password"
+                    endpoint: "10.X.X.X"
+                    endpointPort: "8080
+                            
+- Use same clusterName &#8593; in the  `second_storageclass.yaml` 
+     ````yaml
+       # Optional: true
+       ClusterName: "cluster2"
+- *Note*: These are two essential parameters that you need to change in the "second_storageclass.yaml" file and other parameters that you change as required. 
+3. Save the  `second_storageclass.yaml` file 
+4. Create your 2nd storage class by using `kubectl`:
+  ````bash
+  kubectl create -f <path_to_second_storageclass_file>
+  ````
+5. Use newly created storage class `isilon-new` for volumes to spin up on `cluster2`
+
+    PVC example
+   ````yaml
+     apiVersion: v1
+     kind: PersistentVolumeClaim
+     metadata:
+       name: test-pvc
+     spec:
+      accessModes:
+      - ReadWriteOnce
+      resources:
+        requests:
+          storage: 5Gi
+      storageClassName: isilon-new
+     ````
+
 ## Volume Snapshot Class
 
 Starting CSI PowerScale v1.6, `dell-csi-helm-installer` will not create any Volume Snapshot Class during the driver installation. Sample volume snapshot class manifests are available at `samples/volumesnapshotclass/`. Use these sample manifests to create a volumesnapshotclass for creating volume snapshots; uncomment/ update the manifests as per the requirements.

From 32913219d435b784be764a9d7fd9c74271645580 Mon Sep 17 00:00:00 2001
From: Santhosh Lakshmanan <111809751+santhoshatdell@users.noreply.github.com>
Date: Wed, 19 Apr 2023 11:32:56 -0500
Subject: [PATCH 06/13] Added replication module known issue (#569)

---
 content/docs/replication/deployment/powerscale.md     | 4 ++--
 content/docs/replication/deployment/storageclasses.md | 2 +-
 content/docs/replication/release/_index.md            | 4 +++-
 content/v1/replication/deployment/powerscale.md       | 4 ++--
 content/v1/replication/deployment/storageclasses.md   | 2 +-
 content/v1/replication/release/_index.md              | 1 +
 content/v2/replication/deployment/storageclasses.md   | 2 +-
 content/v2/replication/release/_index.md              | 1 +
 content/v3/replication/deployment/storageclasses.md   | 2 +-
 content/v3/replication/release/_index.md              | 1 +
 10 files changed, 14 insertions(+), 9 deletions(-)

diff --git a/content/docs/replication/deployment/powerscale.md b/content/docs/replication/deployment/powerscale.md
index 86fe3ef03c..c93b8c8389 100644
--- a/content/docs/replication/deployment/powerscale.md
+++ b/content/docs/replication/deployment/powerscale.md
@@ -162,8 +162,8 @@ driver: "isilon"
 reclaimPolicy: "Delete"
 replicationPrefix: "replication.storage.dell.com"
 remoteRetentionPolicy:
-  RG: "Retain"
-  PV: "Retain"
+  RG: "Delete"
+  PV: "Delete"
 parameters:
   rpo: "Five_Minutes"
   ignoreNamespaces: "false"
diff --git a/content/docs/replication/deployment/storageclasses.md b/content/docs/replication/deployment/storageclasses.md
index 6421c01abe..6be1a87cd1 100644
--- a/content/docs/replication/deployment/storageclasses.md
+++ b/content/docs/replication/deployment/storageclasses.md
@@ -43,7 +43,7 @@ replication.storage.dell.com/remotePVRetentionPolicy: 'delete' | 'retain'
 
 If the remotePVRetentionPolicy is set to 'delete', the corresponding PV would be deleted.
 
-If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. 
+If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. This is not applicable for file system replication.
 
 By default, if the remotePVRetentionPolicy is not specified in the Storage Class, replicated PV resources are retained.
 
diff --git a/content/docs/replication/release/_index.md b/content/docs/replication/release/_index.md
index a27503d49a..d0eb2786f2 100644
--- a/content/docs/replication/release/_index.md
+++ b/content/docs/replication/release/_index.md
@@ -24,4 +24,6 @@ Description: >
 
 ### Known Issues
 
-There are no known issues at this time. 
+| Github ID                                     | Description                                                        |
+| --------------------------------------------- | ------------------------------------------------------------------ |
+| [753](https://github.com/dell/csm/issues/753) | **PowerScale:** When Persistent Volumes (PVs) are created with quota enabled on CSM versions 1.6.0 and before, an incorrect quota gets set for the target side read-only PVs/directories based on the consumed non-zero source size instead of the assigned quota of the source. This can create issues when the user performs failover and wants to write data to the failed over site. If lower quota limit is set, no new writes can be performed on the target side post failover. <br /> **Workaround** using PowerScale cluster CLI or UI: <br /> For each Persistent Volume on the source kubernetes cluster, <br /> 1. Get the quota assigned for the directory on the source PowerScale cluster. The path to the directory information can be obtained from the specification field of the Persistent Volume object. <br /> 2. Verify the quota of the target directory on the target PowerScale cluster. If incorrect quota is set, update the quota on the target directory with the same information as on the source. If no quota is set, create a quota for the target directory. |
diff --git a/content/v1/replication/deployment/powerscale.md b/content/v1/replication/deployment/powerscale.md
index 1d8c61c44f..2757829748 100644
--- a/content/v1/replication/deployment/powerscale.md
+++ b/content/v1/replication/deployment/powerscale.md
@@ -161,8 +161,8 @@ driver: "isilon"
 reclaimPolicy: "Delete"
 replicationPrefix: "replication.storage.dell.com"
 remoteRetentionPolicy:
-  RG: "Retain"
-  PV: "Retain"
+  RG: "Delete"
+  PV: "Delete"
 parameters:
   rpo: "Five_Minutes"
   ignoreNamespaces: "false"
diff --git a/content/v1/replication/deployment/storageclasses.md b/content/v1/replication/deployment/storageclasses.md
index 042d351d72..cee9765d5e 100644
--- a/content/v1/replication/deployment/storageclasses.md
+++ b/content/v1/replication/deployment/storageclasses.md
@@ -43,7 +43,7 @@ replication.storage.dell.com/remotePVRetentionPolicy: 'delete' | 'retain'
 
 If the remotePVRetentionPolicy is set to 'delete', the corresponding PV would be deleted.
 
-If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. 
+If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. This is not applicable for file system replication.
 
 By default, if the remotePVRetentionPolicy is not specified in the Storage Class, replicated PV resources are retained.
 
diff --git a/content/v1/replication/release/_index.md b/content/v1/replication/release/_index.md
index 33d56c7cf5..57c9559d09 100644
--- a/content/v1/replication/release/_index.md
+++ b/content/v1/replication/release/_index.md
@@ -19,3 +19,4 @@ There are no new features in this release.
 | Github ID                                     | Description                                                                             |
 | --------------------------------------------- | --------------------------------------------------------------------------------------- |
 | [523](https://github.com/dell/csm/issues/523) | **PowerScale:** Artifacts are not properly cleaned after deletion.                      |
+| [753](https://github.com/dell/csm/issues/753) | **PowerScale:** When Persistent Volumes (PVs) are created with quota enabled on CSM versions 1.6.0 and before, an incorrect quota gets set for the target side read-only PVs/directories based on the consumed non-zero source size instead of the assigned quota of the source. This can create issues when the user performs failover and wants to write data to the failed over site. If lower quota limit is set, no new writes can be performed on the target side post failover. <br /> **Workaround** using PowerScale cluster CLI or UI: <br /> For each Persistent Volume on the source kubernetes cluster, <br /> 1. Get the quota assigned for the directory on the source PowerScale cluster. The path to the directory information can be obtained from the specification field of the Persistent Volume object. <br /> 2. Verify the quota of the target directory on the target PowerScale cluster. If incorrect quota is set, update the quota on the target directory with the same information as on the source. If no quota is set, create a quota for the target directory. |
diff --git a/content/v2/replication/deployment/storageclasses.md b/content/v2/replication/deployment/storageclasses.md
index 042d351d72..cee9765d5e 100644
--- a/content/v2/replication/deployment/storageclasses.md
+++ b/content/v2/replication/deployment/storageclasses.md
@@ -43,7 +43,7 @@ replication.storage.dell.com/remotePVRetentionPolicy: 'delete' | 'retain'
 
 If the remotePVRetentionPolicy is set to 'delete', the corresponding PV would be deleted.
 
-If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. 
+If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. This is not applicable for file system replication.
 
 By default, if the remotePVRetentionPolicy is not specified in the Storage Class, replicated PV resources are retained.
 
diff --git a/content/v2/replication/release/_index.md b/content/v2/replication/release/_index.md
index d110de5734..a321b2ac25 100644
--- a/content/v2/replication/release/_index.md
+++ b/content/v2/replication/release/_index.md
@@ -28,3 +28,4 @@ Description: >
 | [514](https://github.com/dell/csm/issues/514) | **PowerScale:** When creating a replicated PV in PowerScale, the replicated PV's AzServiceIP property has the target PowerScale endpoint instead of the one defined in the target Storage class.                            |   
 | [515](https://github.com/dell/csm/issues/515) | **PowerScale:** If you failover with an application still running and the volume mounted on the target site, then we cannot mount the PVC due to : "mount.nfs: Stale file handle".                                     |   
 | [518](https://github.com/dell/csm/issues/518) | **PowerScale:** On CSM for Replication with PowerScale, after a repctl failover to a target cluster, the source directory has been removed from the PowerScale. The PersistentVolume Object is still present in Kubernetes. |   
+| [753](https://github.com/dell/csm/issues/753) | **PowerScale:** When Persistent Volumes (PVs) are created with quota enabled on CSM versions 1.6.0 and before, an incorrect quota gets set for the target side read-only PVs/directories based on the consumed non-zero source size instead of the assigned quota of the source. This can create issues when the user performs failover and wants to write data to the failed over site. If lower quota limit is set, no new writes can be performed on the target side post failover. <br /> **Workaround** using PowerScale cluster CLI or UI: <br /> For each Persistent Volume on the source kubernetes cluster, <br /> 1. Get the quota assigned for the directory on the source PowerScale cluster. The path to the directory information can be obtained from the specification field of the Persistent Volume object. <br /> 2. Verify the quota of the target directory on the target PowerScale cluster. If incorrect quota is set, update the quota on the target directory with the same information as on the source. If no quota is set, create a quota for the target directory. |
diff --git a/content/v3/replication/deployment/storageclasses.md b/content/v3/replication/deployment/storageclasses.md
index df85a44833..8869913551 100644
--- a/content/v3/replication/deployment/storageclasses.md
+++ b/content/v3/replication/deployment/storageclasses.md
@@ -43,7 +43,7 @@ replication.storage.dell.com/remotePVRetentionPolicy: 'delete' | 'retain'
 
 If the remotePVRetentionPolicy is set to 'delete', the corresponding PV would be deleted.
 
-If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. 
+If the remotePVRetentionPolicy is set to 'retain', the corresponding PV would be retained. This is not applicable for file system replication.
 
 By default, if the remotePVRetentionPolicy is not specified in the Storage Class, replicated PV resources are retained.
 
diff --git a/content/v3/replication/release/_index.md b/content/v3/replication/release/_index.md
index d110de5734..a321b2ac25 100644
--- a/content/v3/replication/release/_index.md
+++ b/content/v3/replication/release/_index.md
@@ -28,3 +28,4 @@ Description: >
 | [514](https://github.com/dell/csm/issues/514) | **PowerScale:** When creating a replicated PV in PowerScale, the replicated PV's AzServiceIP property has the target PowerScale endpoint instead of the one defined in the target Storage class.                            |   
 | [515](https://github.com/dell/csm/issues/515) | **PowerScale:** If you failover with an application still running and the volume mounted on the target site, then we cannot mount the PVC due to : "mount.nfs: Stale file handle".                                     |   
 | [518](https://github.com/dell/csm/issues/518) | **PowerScale:** On CSM for Replication with PowerScale, after a repctl failover to a target cluster, the source directory has been removed from the PowerScale. The PersistentVolume Object is still present in Kubernetes. |   
+| [753](https://github.com/dell/csm/issues/753) | **PowerScale:** When Persistent Volumes (PVs) are created with quota enabled on CSM versions 1.6.0 and before, an incorrect quota gets set for the target side read-only PVs/directories based on the consumed non-zero source size instead of the assigned quota of the source. This can create issues when the user performs failover and wants to write data to the failed over site. If lower quota limit is set, no new writes can be performed on the target side post failover. <br /> **Workaround** using PowerScale cluster CLI or UI: <br /> For each Persistent Volume on the source kubernetes cluster, <br /> 1. Get the quota assigned for the directory on the source PowerScale cluster. The path to the directory information can be obtained from the specification field of the Persistent Volume object. <br /> 2. Verify the quota of the target directory on the target PowerScale cluster. If incorrect quota is set, update the quota on the target directory with the same information as on the source. If no quota is set, create a quota for the target directory. |

From 05572bd9c54109ac85d7bd376b434cf81bdea508 Mon Sep 17 00:00:00 2001
From: Santhosh Lakshmanan <111809751+santhoshatdell@users.noreply.github.com>
Date: Wed, 19 Apr 2023 14:14:50 -0500
Subject: [PATCH 07/13] Updating main with changes from release-1.6.1 (#580)

---
 config.toml                                   |  2 +-
 content/docs/_index.md                        | 28 +++++++++----------
 content/docs/csidriver/_index.md              |  2 +-
 .../csidriver/installation/helm/isilon.md     |  2 +-
 content/docs/csidriver/release/powerscale.md  |  6 ++--
 .../csidriver/upgradation/drivers/isilon.md   |  4 +--
 6 files changed, 23 insertions(+), 21 deletions(-)

diff --git a/config.toml b/config.toml
index fac2f2b487..00355fa373 100644
--- a/config.toml
+++ b/config.toml
@@ -169,7 +169,7 @@ enable = false
 #	icon = "fa fa-envelope"
 #        desc = "Discuss development issues around the project"
 [[params.versions]]
-  version = "Current(v1.6)"
+  version = "Current(v1.6.1)"
   url = "https://dell.github.io/csm-docs/docs/"
 
 [[params.versions]]
diff --git a/content/docs/_index.md b/content/docs/_index.md
index 7fd3bae165..db96a512cf 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -64,23 +64,23 @@ CSM is made up of multiple components including modules (enterprise capabilities
 
 ## CSM Supported Modules and Dell CSI Drivers
 
-| Modules/Drivers                                                                              | CSM 1.6 | [CSM 1.5.1](../v1/) | [CSM 1.4](../v2/) | [CSM 1.3.1](../v3/) |
-| -------------------------------------------------------------------------------------------- | :-----: | :---------------: | :---------------: | :-----------------: |
-| [Authorization](https://hub.docker.com/r/dellemc/csm-authorization-sidecar)                  | v1.6.0  |      v1.5.1       |      v1.4.0       |       v1.3.0        |
-| [Observability](https://hub.docker.com/r/dellemc/csm-topology)                               | v1.5.0  |      v1.4.0       |      v1.3.0       |       v1.2.0        |
-| [Replication](https://hub.docker.com/r/dellemc/dell-replication-controller)                  | v1.4.0  |      v1.3.1       |      v1.3.0       |       v1.3.0        |
-| [Resiliency](https://hub.docker.com/r/dellemc/podmon)                                        | v1.5.0  |      v1.4.0       |      v1.3.0       |       v1.2.0        |
-| [Encryption](https://hub.docker.com/r/dellemc/csm-encryption)                                | v0.3.0  |      v0.2.0       |      v0.1.0       |         NA          |
-| [Application Mobility](https://hub.docker.com/r/dellemc/csm-application-mobility-controller) | v0.3.0  |      v0.2.0       |      v0.1.0       |         NA          |
-| [CSI Driver for PowerScale](https://hub.docker.com/r/dellemc/csi-isilon/tags)                | v2.6.0  |      v2.5.0       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for Unity XT](https://hub.docker.com/r/dellemc/csi-unity/tags)                   | v2.6.0  |      v2.5.0       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for PowerStore](https://hub.docker.com/r/dellemc/csi-powerstore/tags)            | v2.6.0  |      v2.5.1       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for PowerFlex](https://hub.docker.com/r/dellemc/csi-vxflexos/tags)               | v2.6.0  |      v2.5.0       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for PowerMax](https://hub.docker.com/r/dellemc/csi-powermax/tags)                | v2.6.0  |      v2.5.0       |      v2.4.0       |       v2.3.1        |
+| Modules/Drivers                                                                              | CSM 1.6.1 | [CSM 1.5.1](../v1/) | [CSM 1.4](../v2/) | [CSM 1.3.1](../v3/) |
+| -------------------------------------------------------------------------------------------- | :-------: | :---------------: | :---------------: | :-----------------: |
+| [Authorization](https://hub.docker.com/r/dellemc/csm-authorization-sidecar)                  |  v1.6.0   |      v1.5.1       |      v1.4.0       |       v1.3.0        |
+| [Observability](https://hub.docker.com/r/dellemc/csm-topology)                               |  v1.5.0   |      v1.4.0       |      v1.3.0       |       v1.2.0        |
+| [Replication](https://hub.docker.com/r/dellemc/dell-replication-controller)                  |  v1.4.0   |      v1.3.1       |      v1.3.0       |       v1.3.0        |
+| [Resiliency](https://hub.docker.com/r/dellemc/podmon)                                        |  v1.5.0   |      v1.4.0       |      v1.3.0       |       v1.2.0        |
+| [Encryption](https://hub.docker.com/r/dellemc/csm-encryption)                                |  v0.3.0   |      v0.2.0       |      v0.1.0       |         NA          |
+| [Application Mobility](https://hub.docker.com/r/dellemc/csm-application-mobility-controller) |  v0.3.0   |      v0.2.0       |      v0.1.0       |         NA          |
+| [CSI Driver for PowerScale](https://hub.docker.com/r/dellemc/csi-isilon/tags)                |  v2.6.1   |      v2.5.0       |      v2.4.0       |       v2.3.0        |
+| [CSI Driver for Unity XT](https://hub.docker.com/r/dellemc/csi-unity/tags)                   |  v2.6.0   |      v2.5.0       |      v2.4.0       |       v2.3.0        |
+| [CSI Driver for PowerStore](https://hub.docker.com/r/dellemc/csi-powerstore/tags)            |  v2.6.0   |      v2.5.1       |      v2.4.0       |       v2.3.0        |
+| [CSI Driver for PowerFlex](https://hub.docker.com/r/dellemc/csi-vxflexos/tags)               |  v2.6.0   |      v2.5.0       |      v2.4.0       |       v2.3.0        |
+| [CSI Driver for PowerMax](https://hub.docker.com/r/dellemc/csi-powermax/tags)                |  v2.6.0   |      v2.5.0       |      v2.4.0       |       v2.3.1        |
 
 ## CSM Modules Support Matrix for Dell CSI Drivers 
 
-| CSM Module                                                  | CSI PowerFlex v2.6.0 | CSI PowerScale v2.6.0 | CSI PowerStore v2.6.0 | CSI PowerMax v2.6.0 | CSI Unity XT v2.6.0 |
+| CSM Module                                                  | CSI PowerFlex v2.6.0 | CSI PowerScale v2.6.1 | CSI PowerStore v2.6.0 | CSI PowerMax v2.6.0 | CSI Unity XT v2.6.0 |
 | ----------------------------------------------------------- | -------------------- | --------------------- | --------------------- | ------------------- | ------------------- |
 | [**Authorization**](authorization/) v1.6.0                  | ✔️                    | ✔️                     | ❌                     | ✔️                   | ❌                   |
 | [**Observability**](observability/) v1.5.0                  | ✔️                    | ✔️                     | ✔️                     | ✔️                   | ❌                   |
diff --git a/content/docs/csidriver/_index.md b/content/docs/csidriver/_index.md
index 8be8c5c1bb..95ea1c8ac8 100644
--- a/content/docs/csidriver/_index.md
+++ b/content/docs/csidriver/_index.md
@@ -33,7 +33,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 XT  | PowerScale | PowerStore |
 |--------------------------|:--------:|:---------:|:---------:|:----------:|:----------:|
-| CSI Driver version       | 2.6.0    | 2.6.0     | 2.6.0     | 2.6.0      | 2.6.0      |
+| CSI Driver version       | 2.6.0    | 2.6.0     | 2.6.0     | 2.6.1      | 2.6.0      |
 | Static Provisioning      | yes      | yes       | yes       | yes        | yes        |
 | Dynamic Provisioning     | yes      | yes       | yes       | yes        | yes        |
 | Expand Persistent Volume | yes      | yes       | yes       | yes        | yes        |
diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md
index 438360ea1e..23658d78fe 100644
--- a/content/docs/csidriver/installation/helm/isilon.md
+++ b/content/docs/csidriver/installation/helm/isilon.md
@@ -125,7 +125,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
 ## Install the Driver
 
 **Steps**
-1. Run `git clone -b v2.6.0 https://github.com/dell/csi-powerscale.git` to clone the git repository.
+1. Run `git clone -b v2.6.1 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.
diff --git a/content/docs/csidriver/release/powerscale.md b/content/docs/csidriver/release/powerscale.md
index 3403f542ea..ad06ebc1e2 100644
--- a/content/docs/csidriver/release/powerscale.md
+++ b/content/docs/csidriver/release/powerscale.md
@@ -3,7 +3,7 @@ title: PowerScale
 description: Release notes for PowerScale CSI driver
 ---
 
-## Release Notes - CSI Driver for PowerScale v2.6.0
+## Release Notes - CSI Driver for PowerScale v2.6.1
 
 ### New Features/Changes
 
@@ -14,7 +14,9 @@ description: Release notes for PowerScale CSI driver
 
 ### Fixed Issues
 
-There are no fixed issues in this release.
+| Github ID                                     | Description                                                                            |
+| --------------------------------------------- | -------------------------------------------------------------------------------------- |
+| [753](https://github.com/dell/csm/issues/753) | **Replication:** Incorrect quota set on the target PV/directory when Quota is enabled. |
 
 ### Known Issues
 | Issue                                                                                                                                                                                                                               | Resolution or workaround, if known                                                                                                                                                                                                                                                                                                                                                                                                                                                                             |
diff --git a/content/docs/csidriver/upgradation/drivers/isilon.md b/content/docs/csidriver/upgradation/drivers/isilon.md
index 7e45e79755..27552077f4 100644
--- a/content/docs/csidriver/upgradation/drivers/isilon.md
+++ b/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.5.0 to 2.6.0 using Helm
+## Upgrade Driver from version 2.5.0 to 2.6.1 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.6.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.6.1 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:
 

From 35c8f7a7bcd08e82bb480e4ff10849f6efc87c97 Mon Sep 17 00:00:00 2001
From: Yamunadevi N Shanmugam <82038610+shanmydell@users.noreply.github.com>
Date: Mon, 24 Apr 2023 13:26:59 +0530
Subject: [PATCH 08/13] Update _index.md (#584)

---
 content/docs/csidriver/_index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/docs/csidriver/_index.md b/content/docs/csidriver/_index.md
index 95ea1c8ac8..cd26a6a20a 100644
--- a/content/docs/csidriver/_index.md
+++ b/content/docs/csidriver/_index.md
@@ -40,7 +40,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 | Create VolumeSnapshot    | yes      | yes       | yes       | yes        | yes        |
 | Create Volume from Snapshot | yes   | yes       | yes       | yes        | yes        |
 | Delete Snapshot          | yes      | yes       | yes       | yes        | yes        |
-| [Access Mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes)| **FC/iSCSI/NVMe:** <br>RWO/<br>RWOP<br> **Raw block:** <br>RWO/<br>RWX/<br>ROX/<br>RWOP | RWO/ROX/RWOP<br><br>RWX (Raw block only) | RWO/ROX/RWOP<br><br>RWX (Raw block & NFS only) | RWO/RWX/ROX/<br>RWOP | RWO/RWOP<br>(FC/iSCSI)<br>RWO/<br>RWX/<br>ROX/<br>RWOP<br>(RawBlock, NFS) |
+| [Access Mode](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes)| **FC/iSCSI:** <br>RWO/<br>RWOP<br> **Raw block:** <br>RWO/<br>RWX/<br>ROX/<br>RWOP | RWO/ROX/RWOP<br><br>RWX (Raw block only) | RWO/ROX/RWOP<br><br>RWX (Raw block & NFS only) | RWO/RWX/ROX/<br>RWOP | RWO/RWOP<br>(FC/iSCSI)<br>RWO/<br>RWX/<br>ROX/<br>RWOP<br>(RawBlock, NFS) |
 | CSI Volume Cloning       | yes      | yes       | yes       | yes        | yes        |
 | CSI Raw Block Volume     | yes      | yes       | yes       | no         | yes        |
 | CSI Ephemeral Volume     | no       | yes       | yes       | yes        | yes        |

From 415f026ac4d39d16752282ccf4bf60844920f7ab Mon Sep 17 00:00:00 2001
From: Don Khan <don.khan@dell.com>
Date: Mon, 8 May 2023 08:02:16 -0400
Subject: [PATCH 09/13] Fix inconsistency in isilon namespace (#597)

---
 .../csidriver/installation/operator/isilon.md | 24 +++++++++----------
 .../csmoperator/drivers/powerscale.md         | 18 +++++++-------
 2 files changed, 21 insertions(+), 21 deletions(-)

diff --git a/content/docs/csidriver/installation/operator/isilon.md b/content/docs/csidriver/installation/operator/isilon.md
index a0d9eead69..e1361b2a2b 100644
--- a/content/docs/csidriver/installation/operator/isilon.md
+++ b/content/docs/csidriver/installation/operator/isilon.md
@@ -23,10 +23,10 @@ User can query for CSI-PowerScale driver using the following command:
 ### Install Driver
 
 1. Create namespace.
-     
-   Execute `kubectl create namespace test-isilon` to create the test-isilon namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is 'test-isilon'.
+
+   Execute `kubectl create namespace isilon` to create the isilon namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is 'isilon'.
 2. Create *isilon-creds* secret by using secret.yaml file format only.
-  
+
    2.1   Create a yaml file called secret.yaml with the following content:
      ```
       isilonClusters:
@@ -81,7 +81,7 @@ User can query for CSI-PowerScale driver using the following command:
          endpointPort: "8080"
       ```
 
-   Replace the values for the given keys as per your environment. After creating the secret.yaml, the following command can be used to create the secret,  
+   Replace the values for the given keys as per your environment. After creating the secret.yaml, the following command can be used to create the secret,
    `kubectl create secret generic isilon-creds -n isilon --from-file=config=secret.yaml`
 
    Use the following command to replace or update the secret
@@ -90,7 +90,7 @@ User can query for CSI-PowerScale driver using the following command:
 
    **Note**: The user needs to validate the YAML syntax and array related key/values while replacing the isilon-creds secret.
    The driver will continue to use previous values in case of an error found in the YAML file.
-           
+
 3. Create isilon-certs-n secret.
       Please refer [this section](../../helm/isilon/#certificate-validation-for-onefs-rest-api-calls) for creating cert-secrets.
 
@@ -108,7 +108,7 @@ User can query for CSI-PowerScale driver using the following command:
       ```
       Execute command: ```kubectl create -f empty-secret.yaml```
 
-4. Create a CR (Custom Resource) for PowerScale using the sample files provided 
+4. Create a CR (Custom Resource) for PowerScale using the sample files provided
    [here](https://github.com/dell/dell-csi-operator/tree/master/samples).
 5. Users should configure the parameters in CR. The following table lists the primary configurable parameters of the PowerScale driver and their default values:
 
@@ -129,7 +129,7 @@ User can query for CSI-PowerScale driver using the following command:
    | ***Controller parameters*** |
    | X_CSI_MODE   | Driver starting mode  | No | controller |
    | X_CSI_ISI_ACCESS_ZONE | Name of the access zone a volume can be created in | No | System |
-   | X_CSI_ISI_QUOTA_ENABLED | To enable SmartQuotas | Yes | | 
+   | X_CSI_ISI_QUOTA_ENABLED | To enable SmartQuotas | Yes | |
    | nodeSelector | Define node selection constraints for pods of controller deployment | No | |
    | X_CSI_HEALTH_MONITOR_ENABLED | Enable/Disable health monitor of CSI volumes from Controller plugin. Provides details of volume status and volume condition. As a prerequisite, external-health-monitor sidecar section should be uncommented in samples which would install the sidecar | No | false |
    | ***Node parameters*** |
@@ -139,16 +139,16 @@ User can query for CSI-PowerScale driver using the following command:
    | ***Side car parameters*** |
    | leader-election-lease-duration | Duration, that non-leader candidates will wait to force acquire leadership | No | 20s |
    | leader-election-renew-deadline   | Duration, that the acting leader will retry refreshing leadership before giving up  | No | 15s |
-   | leader-election-retry-period   | Duration, the LeaderElector clients should wait between tries of actions  | No | 5s |   
+   | leader-election-retry-period   | Duration, the LeaderElector clients should wait between tries of actions  | No | 5s |
 
 6.  Execute the following command to create PowerScale custom resource:
     ```kubectl create -f <input_sample_file.yaml>``` .
     This command will deploy the CSI-PowerScale driver in the namespace specified in the input YAML file.
-    
-**Note** : 
+
+**Note** :
    1. From CSI-PowerScale v1.6.0 and higher, Storage class and VolumeSnapshotClass will **not** be created as part of driver deployment. The user has to create Storageclass and Volume Snapshot Class.
    2. "Kubelet config dir path" is not yet configurable in case of Operator based driver installation.
-   3. Also, snapshotter and resizer sidecars are not optional to choose, it comes default with Driver installation. 
+   3. Also, snapshotter and resizer sidecars are not optional to choose, it comes default with Driver installation.
 
 ## Volume Health Monitoring
 This feature is introduced in CSI Driver for PowerScale version 2.1.0.
@@ -163,7 +163,7 @@ To enable this feature, add the below block to the driver manifest before instal
       # Also set the env variable controller.envs.X_CSI_HEALTH_MONITOR_ENABLED  to "true".
       # - name: external-health-monitor
       #   args: ["--monitor-interval=60s"]
-      
+
     # Install the 'external-health-monitor' sidecar accordingly.
     # Allowed values:
     #   true: enable checking of health condition of CSI volumes
diff --git a/content/docs/deployment/csmoperator/drivers/powerscale.md b/content/docs/deployment/csmoperator/drivers/powerscale.md
index 7a336a6994..a831f577f7 100644
--- a/content/docs/deployment/csmoperator/drivers/powerscale.md
+++ b/content/docs/deployment/csmoperator/drivers/powerscale.md
@@ -22,7 +22,7 @@ User can query for all Dell CSI drivers using the following command:
 ### Prerequisite
 
 1. Create namespace.
-   Execute `kubectl create namespace test-isilon` to create the test-isilon namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is 'test-isilon'.
+   Execute `kubectl create namespace isilon` to create the isilon namespace (if not already present). Note that the namespace can be any user-defined name, in this example, we assume that the namespace is 'isilon'.
 
 2. Create *isilon-creds* secret by creating a yaml file called secret.yaml with the following content:
      ```
@@ -78,7 +78,7 @@ User can query for all Dell CSI drivers using the following command:
          endpointPort: "8080"
       ```
 
-   Replace the values for the given keys as per your environment. After creating the secret.yaml, the following command can be used to create the secret,  
+   Replace the values for the given keys as per your environment. After creating the secret.yaml, the following command can be used to create the secret,
    `kubectl create secret generic isilon-creds -n isilon --from-file=config=secret.yaml`
 
    Use the following command to replace or update the secret
@@ -87,7 +87,7 @@ User can query for all Dell CSI drivers using the following command:
 
    **Note**: The user needs to validate the YAML syntax and array related key/values while replacing the isilon-creds secret.
    The driver will continue to use previous values in case of an error found in the YAML file.
-           
+
 3. Create isilon-certs-n secret.
       Please refer [this section](../../../../csidriver/installation/helm/isilon/#certificate-validation-for-onefs-rest-api-calls) for creating cert-secrets.
 
@@ -108,8 +108,8 @@ User can query for all Dell CSI drivers using the following command:
 ### Install Driver
 
 1. Follow all the [prerequisites](#prerequisite) above
-   
-2. Create a CR (Custom Resource) for PowerScale using the sample files provided 
+
+2. Create a CR (Custom Resource) for PowerScale using the sample files provided
    [here](https://github.com/dell/csm-operator/tree/master/samples). This file can be modified to use custom parameters if needed.
 
 3. Users should configure the parameters in CR. The following table lists the primary configurable parameters of the PowerScale driver and their default values:
@@ -131,14 +131,14 @@ User can query for all Dell CSI drivers using the following command:
    | X_CSI_ISI_QUOTA_ENABLED | To enable SmartQuotas | Yes | |
    | ***Node parameters*** |
    | X_CSI_MAX_VOLUMES_PER_NODE | Specify the default value for the maximum number of volumes that the controller can publish to the node | Yes | 0 |
-   | X_CSI_MODE   | Driver starting mode  | No | node | 
+   | X_CSI_MODE   | Driver starting mode  | No | node |
 
 4.  Execute the following command to create PowerScale custom resource:
     ```kubectl create -f <input_sample_file.yaml>``` .
     This command will deploy the CSI-PowerScale driver in the namespace specified in the input YAML file.
 
 5.  [Verify the CSI Driver installation](../#verifying-the-driver-installation)
-    
-**Note** : 
+
+**Note** :
    1. "Kubelet config dir path" is not yet configurable in case of Operator based driver installation.
-   2. Also, snapshotter and resizer sidecars are not optional to choose, it comes default with Driver installation. 
\ No newline at end of file
+   2. Also, snapshotter and resizer sidecars are not optional to choose, it comes default with Driver installation.
\ No newline at end of file

From b910d668511b6ee3f293cb5018de7a676320fb3b Mon Sep 17 00:00:00 2001
From: boyamurthy <92081029+boyamurthy@users.noreply.github.com>
Date: Mon, 8 May 2023 19:58:14 +0530
Subject: [PATCH 10/13] Adding troubleshooting section for mount issue on
 powermax (#603)

---
 content/docs/csidriver/troubleshooting/powermax.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/content/docs/csidriver/troubleshooting/powermax.md b/content/docs/csidriver/troubleshooting/powermax.md
index b2e9802ce5..8f8c177e79 100644
--- a/content/docs/csidriver/troubleshooting/powermax.md
+++ b/content/docs/csidriver/troubleshooting/powermax.md
@@ -17,4 +17,5 @@ description: Troubleshooting PowerMax Driver
 |`FailedPrecondition desc = no topology keys could be generate`| Make sure that FC or iSCSI connectivity to the arrays are proper |
 | CreateHost failed with error `initiator is already part of different host.` | Update modifyHostName to true in values.yaml Or Remove the initiator from existing host |
 | `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. | 
+| 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 |  

From 1ce686172e124bd212e52dbdca9b60c6d0383af9 Mon Sep 17 00:00:00 2001
From: mgandharva <124261698+mgandharva@users.noreply.github.com>
Date: Thu, 11 May 2023 14:56:20 +0530
Subject: [PATCH 11/13] bug_update_support_matrix (#606)

---
 content/docs/_index.md | 16 ----------------
 1 file changed, 16 deletions(-)

diff --git a/content/docs/_index.md b/content/docs/_index.md
index db96a512cf..20234bb9bd 100644
--- a/content/docs/_index.md
+++ b/content/docs/_index.md
@@ -62,22 +62,6 @@ CSM is made up of multiple components including modules (enterprise capabilities
   {{< /card >}}
 {{< /cardpane >}}
 
-## CSM Supported Modules and Dell CSI Drivers
-
-| Modules/Drivers                                                                              | CSM 1.6.1 | [CSM 1.5.1](../v1/) | [CSM 1.4](../v2/) | [CSM 1.3.1](../v3/) |
-| -------------------------------------------------------------------------------------------- | :-------: | :---------------: | :---------------: | :-----------------: |
-| [Authorization](https://hub.docker.com/r/dellemc/csm-authorization-sidecar)                  |  v1.6.0   |      v1.5.1       |      v1.4.0       |       v1.3.0        |
-| [Observability](https://hub.docker.com/r/dellemc/csm-topology)                               |  v1.5.0   |      v1.4.0       |      v1.3.0       |       v1.2.0        |
-| [Replication](https://hub.docker.com/r/dellemc/dell-replication-controller)                  |  v1.4.0   |      v1.3.1       |      v1.3.0       |       v1.3.0        |
-| [Resiliency](https://hub.docker.com/r/dellemc/podmon)                                        |  v1.5.0   |      v1.4.0       |      v1.3.0       |       v1.2.0        |
-| [Encryption](https://hub.docker.com/r/dellemc/csm-encryption)                                |  v0.3.0   |      v0.2.0       |      v0.1.0       |         NA          |
-| [Application Mobility](https://hub.docker.com/r/dellemc/csm-application-mobility-controller) |  v0.3.0   |      v0.2.0       |      v0.1.0       |         NA          |
-| [CSI Driver for PowerScale](https://hub.docker.com/r/dellemc/csi-isilon/tags)                |  v2.6.1   |      v2.5.0       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for Unity XT](https://hub.docker.com/r/dellemc/csi-unity/tags)                   |  v2.6.0   |      v2.5.0       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for PowerStore](https://hub.docker.com/r/dellemc/csi-powerstore/tags)            |  v2.6.0   |      v2.5.1       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for PowerFlex](https://hub.docker.com/r/dellemc/csi-vxflexos/tags)               |  v2.6.0   |      v2.5.0       |      v2.4.0       |       v2.3.0        |
-| [CSI Driver for PowerMax](https://hub.docker.com/r/dellemc/csi-powermax/tags)                |  v2.6.0   |      v2.5.0       |      v2.4.0       |       v2.3.1        |
-
 ## CSM Modules Support Matrix for Dell CSI Drivers 
 
 | CSM Module                                                  | CSI PowerFlex v2.6.0 | CSI PowerScale v2.6.1 | CSI PowerStore v2.6.0 | CSI PowerMax v2.6.0 | CSI Unity XT v2.6.0 |

From aa957a6cc785abc33729e3359170c3fc5ff04fe1 Mon Sep 17 00:00:00 2001
From: Chiman Jain <chimanjain15@gmail.com>
Date: Fri, 12 May 2023 14:43:52 +0530
Subject: [PATCH 12/13] added docs for storage capacity tracking support in
 powerscale

---
 README.md                                     |  3 +-
 content/docs/csidriver/_index.md              |  8 +-
 content/docs/csidriver/features/powerscale.md | 73 ++++++++++++-------
 .../csidriver/installation/helm/isilon.md     | 49 ++++++++-----
 .../csidriver/installation/operator/isilon.md | 10 ++-
 5 files changed, 93 insertions(+), 50 deletions(-)

diff --git a/README.md b/README.md
index d0673d7148..ab6e815d24 100644
--- a/README.md
+++ b/README.md
@@ -27,6 +27,7 @@ Dell Technologies (Dell) Container Storage Modules (CSM) is an open-source suite
 * [About](#about)
 
 ## Container Storage Modules - Components
+
 * [Dell Technologies (Dell) Container Storage Modules (CSM) for Authorization](https://github.com/dell/karavi-authorization)
 * [Dell Technologies (Dell) Container Storage Modules (CSM) for Observability](https://github.com/dell/karavi-observability)
 * [Dell Technologies (Dell) Container Storage Modules (CSM) for Replication](https://github.com/dell/csm-replication)
@@ -42,4 +43,4 @@ Dell Technologies (Dell) Container Storage Modules (CSM) is an open-source suite
 
 Dell Technologies (Dell) Container Storage Modules (CSM) is 100% open source and community-driven. All components are available
 under [Apache 2 License](https://www.apache.org/licenses/LICENSE-2.0.html) on
-GitHub.
\ No newline at end of file
+GitHub.
diff --git a/content/docs/csidriver/_index.md b/content/docs/csidriver/_index.md
index cd26a6a20a..4ee8196bad 100644
--- a/content/docs/csidriver/_index.md
+++ b/content/docs/csidriver/_index.md
@@ -13,6 +13,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 ## Features and capabilities
 
 ### Supported Operating Systems/Container Orchestrator Platforms
+
 {{<table "table table-striped table-bordered table-sm">}}
 |               | PowerMax         | PowerFlex           | Unity XT         | PowerScale        | PowerStore       |
 |---------------|:----------------:|:-------------------:|:----------------:|:-----------------:|:----------------:|
@@ -30,6 +31,7 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 {{</table>}}
 
 ### CSI Driver Capabilities
+
 {{<table "table table-striped table-bordered table-sm">}}
 | Features                 | PowerMax | PowerFlex | Unity XT  | PowerScale | PowerStore |
 |--------------------------|:--------:|:---------:|:---------:|:----------:|:----------:|
@@ -47,15 +49,19 @@ The CSI Drivers by Dell implement an interface between [CSI](https://kubernetes-
 | Topology                 | yes      | yes       | yes       | yes        | yes        |
 | Multi-array              | yes      | yes       | yes       | yes        | yes        |
 | Volume Health Monitoring | yes      | yes       | yes       | yes        | yes        |
-| Storage Capacity Tracking | no      | no        | no        | no         | yes        |
+| Storage Capacity Tracking | no      | no        | no        | yes        | yes        |
 {{</table>}}
+
 ### Supported Storage Platforms
+
 {{<table "table table-striped table-bordered table-sm">}}
 |               | PowerMax                                                | PowerFlex        | Unity XT                   | PowerScale                         |    PowerStore    |
 |---------------|:-------------------------------------------------------:|:----------------:|:--------------------------:|:----------------------------------:|:----------------:|
 | Storage Array |PowerMax 2000/8000 <br> PowerMax 2500/8500 <br> 5978.479.479, 5978.711.711, 6079.xxx.xxx<br>Unisphere 10.0 |    3.5.x, 3.6.x, 4.0  | 5.0.x, 5.1.x, 5.2.x | OneFS 8.1, 8.2, 9.0, 9.1, 9.2, 9.3, 9.4 | 1.0.x, 2.0.x, 2.1.x, 3.0, 3.2     |
 {{</table>}}
+
 ### Backend Storage Details
+
 {{<table "table table-striped table-bordered table-sm">}}
 | Features      | PowerMax         | PowerFlex          | Unity XT         | PowerScale       | PowerStore       |
 |---------------|:----------------:|:------------------:|:----------------:|:----------------:|:----------------:|
diff --git a/content/docs/csidriver/features/powerscale.md b/content/docs/csidriver/features/powerscale.md
index 085ee57ffd..ed49f0204d 100644
--- a/content/docs/csidriver/features/powerscale.md
+++ b/content/docs/csidriver/features/powerscale.md
@@ -130,9 +130,9 @@ During the installation of CSI PowerScale driver version 2.0 and higher, no defa
 
 Following are the manifests for the Volume Snapshot Class:
 
-1. VolumeSnapshotClass 
-```yaml
+1. VolumeSnapshotClass
 
+```yaml
 apiVersion: snapshot.storage.k8s.io/v1
 kind: VolumeSnapshotClass
 metadata:
@@ -242,7 +242,6 @@ spec:
 
 >The Kubernetes Volume Expansion feature can only be used to increase the size of a volume. It cannot be used to shrink a volume.
 
-
 ## Volume Cloning Feature
 
 The CSI PowerScale driver version 1.3 and later supports volume cloning. This allows specifying existing PVCs in the _dataSource_ field to indicate a user would like to clone a Volume.
@@ -295,16 +294,19 @@ In case of a failure, one of the standby pods becomes active and takes the posit
 Additionally by leveraging `pod anti-affinity`, no two-controller pods are ever scheduled on the same node.
 
 To increase or decrease the number of controller pods, edit the following value in `myvalues.yaml` file:
-```
+
+```yaml
 controllerCount: 2
 ```
 
 >**NOTE:** The default value for controllerCount is 2. It is recommended to not change this unless really required. Also, if the controller count is greater than the number of available nodes (where the pods can be scheduled), some controller pods will remain in a Pending state.
 
 If you are using the `dell-csi-operator`, adjust the following value in your Custom Resource manifest
-```
+
+```yaml
 replicas: 2  
 ```
+
 For more details about configuring Controller HA using the Dell CSI Operator, refer to the [Dell CSI Operator documentation](../../installation/operator/#custom-resource-specification).
 
 ## Ephemeral Inline Volume
@@ -312,9 +314,9 @@ For more details about configuring Controller HA using the Dell CSI Operator, re
 The CSI PowerScale driver version 1.4.0 and later supports CSI ephemeral inline volumes.
 
 This feature serves as use cases for data volumes whose content and lifecycle are tied to a pod. For example, a driver might populate a volume with dynamically created secrets that are specific to the application running in the pod. Such volumes need to be created together with a pod and can be deleted as part of pod termination (ephemeral). They get defined as part of the pod spec (inline).
- 
+
 At runtime, nested inline volumes follow the lifecycle of their associated pods where the driver handles all phases of volume operations as pods are created and destroyed.
- 
+
 The following is a sample manifest for creating CSI ephemeral Inline Volume in pod manifest with CSI PowerScale driver.
 
 ```yaml
@@ -342,13 +344,14 @@ spec:
 This manifest creates a pod in a given cluster and attaches a newly created ephemeral inline CSI volume to it.
 
 ## Topology
+
 ### Topology Support
 
-The CSI PowerScale driver version 1.4.0 and later supports Topology by default which forces volumes to be placed on worker nodes that have connectivity to the backend storage, as a result of which the nodes which have access to PowerScale Array are appropriately labeled. The driver leverages these labels to ensure that the driver components (controller, node) are spawned only on nodes wherein these labels exist. 
+The CSI PowerScale driver version 1.4.0 and later supports Topology by default which forces volumes to be placed on worker nodes that have connectivity to the backend storage, as a result of which the nodes which have access to PowerScale Array are appropriately labeled. The driver leverages these labels to ensure that the driver components (controller, node) are spawned only on nodes wherein these labels exist.
   
 This covers use cases where:
- 
-The CSI PowerScale driver may not be installed or running on some nodes where Users have chosen to restrict the nodes on accessing the PowerScale storage array. 
+
+The CSI PowerScale driver may not be installed or running on some nodes where Users have chosen to restrict the nodes on accessing the PowerScale storage array.
 
 We support CustomTopology which enables users to apply labels for nodes - "csi-isilon.dellemc.com/XX.XX.XX.XX=csi-isilon.dellemc.com" and expect the labels to be honored by the driver.
   
@@ -356,15 +359,14 @@ When “enableCustomTopology” is set to “true”, the CSI driver fetches cus
 
 **Note:** Only a single cluster can be configured as part of secret.yaml for custom topology.
 
-
 ### Topology Usage
-   
-To utilize the Topology feature, create a custom `StorageClass` with `volumeBindingMode` set to `WaitForFirstConsumer` and specify the desired topology labels within `allowedTopologies` field of this custom storage class. This ensures that the Pod schedule takes advantage of the topology and the selected node has access to provisioned volumes. 
+
+To utilize the Topology feature, create a custom `StorageClass` with `volumeBindingMode` set to `WaitForFirstConsumer` and specify the desired topology labels within `allowedTopologies` field of this custom storage class. This ensures that the Pod schedule takes advantage of the topology and the selected node has access to provisioned volumes.
 
 **Note:** Whenever a new storage cluster is being added in secret, even though it is dynamic, the new storage cluster IP address-related label is not added to worker nodes dynamically. The user has to spin off (bounce) driver-related pods (controller and node pods) in order to apply newly added information to be reflected in worker nodes.
   
 **Storage Class Example with Topology Support:**
- 
+
 ```yaml
 # This is a sample manifest for utilizing the topology feature and mount options.
 # PVCs created using this storage class will be scheduled 
@@ -412,6 +414,7 @@ allowedTopologies:
 # To mount volume with NFSv4, specify mount option vers=4. Make sure NFSv4 is enabled on the Isilon Cluster.
 mountOptions: ["<mountOption1>", "<mountOption2>", ..., "<mountOptionN>"]
 ```
+
 For additional information, see the [Kubernetes Topology documentation](https://kubernetes-csi.github.io/docs/topology.html).
 
 ## Support custom networks for NFS I/O traffic
@@ -421,14 +424,14 @@ has workloads scheduled, there is a possibility that it might lead to backward c
 
 Also, the previous workload will still be using the default network and not custom networks. For previous workloads to use custom networks, the recreation of pods is required.
 
-When csi-powerscale driver creates an NFS export, the traffic flows through the client specified in the export. By default, the client is the network interface for Kubernetes 
+When csi-powerscale driver creates an NFS export, the traffic flows through the client specified in the export. By default, the client is the network interface for Kubernetes
 communication (same IP/fqdn as k8s node) by default.
 
 For a cluster with multiple network interfaces and if a user wants to segregate k8s traffic from NFS traffic; you can use the `allowedNetworks` option.
 `allowedNetworks` takes CIDR addresses as a parameter to match the IPs to be picked up by the driver to allow and route NFS traffic.
 
-
 ## Volume Limit
+
 The CSI Driver for Dell PowerScale allows users to specify the maximum number of PowerScale volumes that can be used in a node.
 
 The user can set the volume limit for a node by creating a node label `max-isilon-volumes-per-node` and specifying the volume limit for that node.
@@ -440,7 +443,7 @@ The user can also set the volume limit for all the nodes in the cluster by speci
 
 ## Node selector in helm template
 
-Now user can define in which worker node, the CSI node pod daemonset can run (just like any other pod in Kubernetes world.)For more information, refer to https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector 
+Now user can define in which worker node, the CSI node pod daemonset can run (just like any other pod in Kubernetes world.)For more information, refer to https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector
   
 Similarly, users can define the tolerations based on various conditions like memory pressure, disk pressure and network availability. Refer to https://kubernetes.io/docs/concepts/workloads/controllers/daemonset/#taints-and-tolerations for more information.  
 
@@ -468,30 +471,32 @@ Let us assume the user creates a PVC with 3 Gi of storage and 'SmartQuotas' have
     - Driver allows the user to enter more data irrespective of the initial PVC size (since no quota is set against this PVC)
     - The user can expand the volume from an initial size of 3Gi to 4Gi or more. The driver allows it.
 
-
 ## Dynamic Logging Configuration
 
 This feature is introduced in CSI Driver for PowerScale version 1.6.0 and updated in version 2.0.0
 
 ### Helm based installation
-As part of driver installation, a ConfigMap with the name `isilon-config-params` is created, which contains an attribute `CSI_LOG_LEVEL` which specifies the current log level of CSI driver. 
+
+As part of driver installation, a ConfigMap with the name `isilon-config-params` is created, which contains an attribute `CSI_LOG_LEVEL` which specifies the current log level of CSI driver.
 
 Users can set the default log level by specifying log level to `logLevel` attribute in values.yaml during driver installation.
 
 To change the log level dynamically to a different value user can edit the same values.yaml, and run the following command
-```
+
+```bash
 cd dell-csi-helm-installer
 ./csi-install.sh --namespace isilon --values ./my-isilon-settings.yaml --upgrade
 ```
 
 Note: here my-isilon-settings.yaml is a values.yaml file which user has used for driver installation.  
 
-
 ### Operator based installation
+
 As part of driver installation, a ConfigMap with the name `isilon-config-params` is created using the manifest located in the sample file. This ConfigMap contains an attribute `CSI_LOG_LEVEL` which specifies the current log level of the CSI driver. To set the default/initial log level user can set this field during driver installation.
 
 To update the log level dynamically user has to edit the ConfigMap `isilon-config-params` and update `CSI_LOG_LEVEL` to the desired log level.
-```
+
+```bash
 kubectl edit configmap -n isilon isilon-config-params
 ```  
 
@@ -506,13 +511,14 @@ CSI Driver for Dell PowerScale is supported in the NAT environment.
 This feature is introduced in CSI Driver for PowerScale version 2.0.0
 
 ### Helm based installation
+
 The permissions for volume directory can now be configured in 3 ways:
 
 1. Through values.yaml
 2. Through secrets
 3. Through storage class
 
-```
+```yaml
   # isiVolumePathPermissions: The permissions for isi volume directory path
   # This value acts as a default value for isiVolumePathPermissions, if not specified for a cluster config in secret
   # Allowed values: valid octal mode number
@@ -533,14 +539,14 @@ In the case of operator-based installation, default permission for powerscale di
 
 Other ways of configuring powerscale volume permissions remain the same as helm-based installation.
 
-
 ## PV/PVC Metrics
 
-CSI Driver for Dell PowerScale 2.1.0 and above supports volume health monitoring. This allows Kubernetes to report on the condition, status and usage of the underlying volumes. 
+CSI Driver for Dell PowerScale 2.1.0 and above supports volume health monitoring. This allows Kubernetes to report on the condition, status and usage of the underlying volumes.
 For example, if a volume were to be deleted from the array, or unmounted outside of Kubernetes, Kubernetes will now report these abnormal conditions as events.
 
 ### This feature can be enabled
-1. For controller plugin, by setting attribute `controller.healthMonitor.enabled` to `true` in `values.yaml` file. Also health monitoring interval can be changed through attribute `controller.healthMonitor.interval` in `values.yaml` file.   
+
+1. For controller plugin, by setting attribute `controller.healthMonitor.enabled` to `true` in `values.yaml` file. Also health monitoring interval can be changed through attribute `controller.healthMonitor.interval` in `values.yaml` file.
 2. For node plugin, by setting attribute `node.healthMonitor.enabled` to `true` in `values.yaml` file and by enabling the alpha feature gate `CSIVolumeHealth`.
 
 ## Single Pod Access Mode for PersistentVolumes- ReadWriteOncePod (ALPHA FEATURE)
@@ -551,6 +557,7 @@ To use this feature, enable the ReadWriteOncePod feature gate for kube-apiserver
 `--feature-gates="...,ReadWriteOncePod=true"`
 
 ### Creating a PersistentVolumeClaim
+
 ```yaml
 kind: PersistentVolumeClaim
 apiVersion: v1
@@ -568,3 +575,17 @@ When this feature is enabled, the existing `ReadWriteOnce(RWO)` access mode rest
 
 To migrate existing PersistentVolumes to use `ReadWriteOncePod`, please follow the instruction from [here](https://kubernetes.io/blog/2021/09/13/read-write-once-pod-access-mode-alpha/#migrating-existing-persistentvolumes).
 
+## Storage Capacity Tracking
+
+CSI PowerScale driver version 2.7.0 and above supports Storage Capacity Tracking.
+
+This feature helps the scheduler to make more informed choices about where to start pods which depend on unbound volumes with late binding (aka "WaitForFirstConsumer"). Pods will be scheduled on a node (satisfying the topology constraints) only if the requested capacity is available on the storage array.
+If such a node is not available, the pods stay in Pending state. This means they are not scheduled.
+
+Without storage capacity tracking, pods get scheduled on a node satisfying the topology constraints. If the required capacity is not available, volume attachment to the pods fails, and pods remain in ContainerCreating state. Storage capacity tracking eliminates unnecessary scheduling of pods when there is insufficient capacity.
+
+The attribute `storageCapacity.enabled` in `my-powerscale-settings.yaml` can be used to enabled/disabled the feature during driver installation.
+To configure how often driver checks for changed capacity set `storageCapacity.pollInterval` attribute. In case of driver installed via operator, this interval can be configured in the sample files provided [here](https://github.com/dell/dell-csi-operator/tree/master/samples) by editing the `capacity-poll-interval` argument present in the `provisioner` sidecar.
+
+**Note:**
+>This feature requires kubernetes v1.24 and above and will be automatically disabled in lower version of kubernetes.
diff --git a/content/docs/csidriver/installation/helm/isilon.md b/content/docs/csidriver/installation/helm/isilon.md
index 23658d78fe..ccf512e64d 100644
--- a/content/docs/csidriver/installation/helm/isilon.md
+++ b/content/docs/csidriver/installation/helm/isilon.md
@@ -48,9 +48,11 @@ controller:
 ```
 
 #### Volume Snapshot CRD's
+
 The Kubernetes Volume Snapshot CRDs can be obtained and installed from the external-snapshotter project on Github. Manifests are available here:[v6.2.1](https://github.com/kubernetes-csi/external-snapshotter/tree/v6.2.1/client/config/crd)
 
 #### Volume Snapshot Controller
+
 The CSI external-snapshotter sidecar is split into two controllers:
 - A common snapshot controller
 - A CSI external-snapshotter sidecar
@@ -62,8 +64,8 @@ The common snapshot controller must be installed only once in the cluster irresp
    - [quay.io/k8scsi/csi-snapshotter:v4.0.x](https://quay.io/repository/k8scsi/csi-snapshotter?tag=v4.0.0&tab=tags)
 - The CSI external-snapshotter sidecar is still installed along with the driver and does not involve any extra configuration.
 
-
 #### Installation example
+
 You can install CRDs and the default snapshot controller by running these commands:
 ```bash
 git clone https://github.com/kubernetes-csi/external-snapshotter/
@@ -77,6 +79,7 @@ kubectl -n kube-system kustomize deploy/kubernetes/snapshot-controller | kubectl
 - It is recommended to use 6.2.x version of snapshotter/snapshot-controller.
 
 ### (Optional) Volume Health Monitoring
+
 Volume Health Monitoring feature is optional and by default this feature is disabled for drivers when installed via helm.
 
 If enabled capacity metrics (used & free capacity, used & free inodes) for PowerScale PV will be expose in Kubernetes metrics API.
@@ -84,6 +87,7 @@ If enabled capacity metrics (used & free capacity, used & free inodes) for Power
 To enable this feature, add the below block to the driver manifest before installing the driver. This ensures to install external
 health monitor sidecar. To get the volume health state value under controller should be set to true as seen below. To get the
 volume stats value under node should be set to true.
+
 ```yaml
 controller:
   healthMonitor:
@@ -109,6 +113,7 @@ node:
 ```
 
 ### (Optional) Replication feature Requirements
+
 Applicable only if you decided to enable the Replication feature in `values.yaml`
 
 ```yaml
@@ -145,6 +150,8 @@ CRDs should be configured during replication prepare stage with repctl as descri
    | kubeletConfigDir | Specify kubelet config dir path | Yes | "/var/lib/kubelet" |
    | enableCustomTopology | Indicates PowerScale FQDN/IP which will be fetched from node label and the same will be used by controller and node pod to establish a connection to Array. This requires enableCustomTopology to be enabled. | No | false |
    | fsGroupPolicy | Defines which FS Group policy mode to be used, Supported modes `None, File and ReadWriteOnceWithFSType` | No | "ReadWriteOnceWithFSType" |
+   | storageCapacity.enabled | Enable/Disable storage capacity tracking | No | true |
+   | storageCapacity.pollInterval | Configure how often the driver checks for changed capacity | No | 5m |
    | podmonAPIPort | Defines the port which csi-driver will use within the cluster to support podmon | No | 8083 |
    | maxPathLen | Defines the maximum length of path for a volume | No | 192 |
    | ***controller*** | Configure controller pod specific parameters | | |
@@ -186,17 +193,17 @@ CRDs should be configured during replication prepare stage with repctl as descri
    | **encryption** | [Encryption](../../../../secure/encryption/deployment) is an optional feature to apply encryption to CSI volumes. | - | - |
    | enabled        | A boolean that enables/disables Encryption feature. | No | false |
    | image | Encryption driver image name. | No | "dellemc/csm-encryption:v0.3.0" |
-   
+
    *NOTE:* 
 
    - ControllerCount parameter value must not exceed the number of nodes in the Kubernetes cluster. Otherwise, some of the controller pods remain in a "Pending" state till new nodes are available for scheduling. The installer exits with a WARNING on the same.
    - Whenever the *certSecretCount* parameter changes in *my-isilon-setting.yaml* user needs to reinstall the driver.
    - In order to enable authorization, there should be an authorization proxy server already installed.
    - If you are using a custom image, check the *version* and *driverRepository* fields in *my-isilon-setting.yaml* to make sure that they are pointing to the correct image repository and driver version. These two fields are spliced together to form the image name, as shown here: <driverRepository>/csi-isilon:v<version>
-   
-    
+
+
 6. Edit following parameters in samples/secret/secret.yaml file and update/add connection/authentication information for one or more PowerScale clusters.
-   
+
    | Parameter | Description | Required | Default |
    | --------- | ----------- | -------- |-------- |
    | clusterName | Logical name of PoweScale cluster against which volume CRUD operations are performed through this secret. | Yes | - |
@@ -212,6 +219,7 @@ CRDs should be configured during replication prepare stage with repctl as descri
    | mountEndpoint | Endpoint of the PowerScale OneFS API server, for example, 10.0.0.1. This must be specified if [CSM-Authorization](https://github.com/dell/karavi-authorization) is enabled. | No | - |
 
 ### User privileges
+
    The username specified in *secret.yaml* must be from the authentication providers of PowerScale. The user must have enough privileges to perform the actions. The suggested privileges are as follows:
 
    | Privilege              | Type       |
@@ -227,27 +235,29 @@ CRDs should be configured during replication prepare stage with repctl as descri
 
 Create isilon-creds secret using the following command:
   <br/> `kubectl create secret generic isilon-creds -n isilon --from-file=config=secret.yaml`
-   
+
    *NOTE:* 
    - If any key/value is present in all *my-isilon-settings.yaml*, *secret*, and storageClass, then the values provided in storageClass parameters take precedence.
    - The user has to validate the yaml syntax and array-related key/values while replacing or appending the isilon-creds secret. The driver will continue to use previous values in case of an error found in the yaml file.
    - For the key isiIP/endpoint, the user can give either IP address or FQDN. Also, the user can prefix 'https' (For example, https://192.168.1.1) with the value.
    - The *isilon-creds* secret has a *mountEndpoint* parameter which should only be updated and used when [Authorization](../../../../authorization) is enabled.
-   
+
 7. Install OneFS CA certificates by following the instructions from the next section, if you want to validate OneFS API server's certificates. If not, create an empty secret using the following command and an empty secret must be created for the successful installation of CSI Driver for Dell PowerScale.
-    ```
+
+    ```bash
     kubectl create -f empty-secret.yaml
     ```
+
    This command will create a new secret called `isilon-certs-0` in isilon namespace.
-   
-8.  Install the driver using `csi-install.sh` bash script by running `cd ../dell-csi-helm-installer && ./csi-install.sh --namespace isilon --values ../helm/my-isilon-settings.yaml` (assuming that the current working directory is 'helm' and my-isilon-settings.yaml is also present under 'helm' directory)
 
-## Certificate validation for OneFS REST API calls 
+8. Install the driver using `csi-install.sh` bash script by running `cd ../dell-csi-helm-installer && ./csi-install.sh --namespace isilon --values ../helm/my-isilon-settings.yaml` (assuming that the current working directory is 'helm' and my-isilon-settings.yaml is also present under 'helm' directory)
+
+## Certificate validation for OneFS REST API calls
 
 The CSI driver exposes an install parameter 'skipCertificateValidation' which determines if the driver
 performs client-side verification of the OneFS certificates. The 'skipCertificateValidation' parameter is set to true by default and the driver does not verify the OneFS certificates.
 
-If the 'skipCertificateValidation' is set to false, then the secret isilon-certs must contain the CA certificate for OneFS. 
+If the 'skipCertificateValidation' is set to false, then the secret isilon-certs must contain the CA certificate for OneFS.
 If this secret is an empty secret, then the validation of the certificate fails, and the driver fails to start.
 
 If the 'skipCertificateValidation' parameter is set to false and a previous installation attempt to create the empty secret, then this secret must be deleted and re-created using the CA certs. If the OneFS certificate is self-signed, then perform the following steps:
@@ -259,6 +269,7 @@ If the 'skipCertificateValidation' parameter is set to false and a previous inst
 3. Use the following command to replace the secret <br/> `kubectl create secret generic isilon-certs-0 -n isilon --from-file=cert-0=ca_cert_0.pem -o yaml --dry-run | kubectl replace -f -`
 
 **NOTES:**
+
 1. The OneFS IP can be with or without a port, depends upon the configuration of OneFS API server.
 2. The commands are based on the namespace 'isilon'
 3. It is highly recommended that ca_cert.pem file(s) having the naming convention as ca_cert_number.pem (example: ca_cert_0, ca_cert_1), where this number starts from 0 and grows as the number of OneFS arrays grows.
@@ -270,13 +281,11 @@ CSI Driver for Dell PowerScale now provides supports for Multi cluster. Now user
 
 `kubectl create secret generic isilon-creds -n isilon --from-file=config=secret.yaml -o yaml --dry-run=client | kubectl replace -f -`
 
-
 **Note**: Updating isilon-certs-x secrets is a manual process, unlike isilon-creds. Users have to re-install the driver in case of updating/adding the SSL certificates or changing the certSecretCount parameter.
 
-
 ## Storage Classes
 
-The CSI driver for Dell PowerScale version 1.5 and later, `dell-csi-helm-installer` does not create any storage classes as part of the driver installation. A sample storage class manifest is available at `samples/storageclass/isilon.yaml`. Use this sample manifest to create a storageclass to provision storage; uncomment/ update the manifest as per the requirements.    
+The CSI driver for Dell PowerScale version 1.5 and later, `dell-csi-helm-installer` does not create any storage classes as part of the driver installation. A sample storage class manifest is available at `samples/storageclass/isilon.yaml`. Use this sample manifest to create a storageclass to provision storage; uncomment/ update the manifest as per the requirements.
 
 ### What happens to my existing storage classes?
 
@@ -287,7 +296,7 @@ The storage classes created as part of the installation have an annotation - "he
 - At least one storage class is required for one array.
 - If you uninstall the driver and reinstall it, you can still face errors if any update in the `values.yaml` file leads to an update of the storage class(es):
 
-```
+```bash
     Error: cannot patch "<sc-name>" with kind StorageClass: StorageClass.storage.k8s.io "<sc-name>" is invalid: parameters: Forbidden: updates to parameters are forbidden
 ```
 
@@ -298,11 +307,11 @@ Deleting a storage class has no impact on a running Pod with mounted PVCs. You c
 
 **Steps to create secondary storage class:**
 
-There are samples storage class yaml files available under `samples/storageclass`.  These can be copied and modified as needed. 
+There are samples storage class yaml files available under `samples/storageclass`.  These can be copied and modified as needed.
 
 1. Copy the `storageclass.yaml` to `second_storageclass.yaml` ( This is just an example, you can rename to file you require. )
 2. Edit the  `second_storageclass.yaml` yaml file and update following parameters:
-- Update the `name` parameter to you require 
+- Update the `name` parameter to you require
     ````yaml
     metadata:
       name: isilon-new
@@ -347,6 +356,7 @@ There are samples storage class yaml files available under `samples/storageclass
 Starting CSI PowerScale v1.6, `dell-csi-helm-installer` will not create any Volume Snapshot Class during the driver installation. Sample volume snapshot class manifests are available at `samples/volumesnapshotclass/`. Use these sample manifests to create a volumesnapshotclass for creating volume snapshots; uncomment/ update the manifests as per the requirements.
 
 ## Silent Mount Re-tries (v2.6.0)
+
 There are race conditions, when completing the ControllerPublish call to populate the client to volumes export list takes longer time than usual due to background NFS refresh process on OneFS wouldn't have completed at same time, resulted in error:"mount failed" with initial attempts and might log success after few re-tries. This unnecessarily logs false positive "mount failed" error logs and to overcome this scenario Driver does silent mount re-tries attempts after every two sec. (five attempts max) for every NodePublish Call and allows successful mount within five re-tries without logging any mount error messages.
 "mount failed" will be logged once these five mount retrial attempts are exhausted and still client is not populated to export list.
 
@@ -355,9 +365,8 @@ Mount Re-tries handles below scenarios:
 - No such file or directory (NFSv4)
 
 *Sample*:
-```
+```bash
 level=error clusterName=powerscale runid=10 msg="mount failed: exit status 32
 mounting arguments: -t nfs -o rw XX.XX.XX.XX:/ifs/data/csi/k8s-ac7b91962d /var/lib/kubelet/pods/9f72096a-a7dc-4517-906c-20697f9d7375/volumes/kubernetes.io~csi/k8s-ac7b91962d/mount
 output: mount.nfs: access denied by server while mounting XX.XX.XX.XX:/ifs/data/csi/k8s-ac7b91962d
 ```
-
diff --git a/content/docs/csidriver/installation/operator/isilon.md b/content/docs/csidriver/installation/operator/isilon.md
index e1361b2a2b..71a93e58a0 100644
--- a/content/docs/csidriver/installation/operator/isilon.md
+++ b/content/docs/csidriver/installation/operator/isilon.md
@@ -17,6 +17,7 @@ Kubernetes Operators make it easy to deploy and manage the entire lifecycle of c
 **Note**: MKE (Mirantis Kubernetes Engine) does not support the installation of CSI-PowerScale via Operator.
 
 ### Listing installed drivers with the CSI Isilon CRD
+
 User can query for CSI-PowerScale driver using the following command:
 `kubectl get csiisilon --all-namespaces`
 
@@ -28,7 +29,8 @@ User can query for CSI-PowerScale driver using the following command:
 2. Create *isilon-creds* secret by using secret.yaml file format only.
 
    2.1   Create a yaml file called secret.yaml with the following content:
-     ```
+
+     ```yaml
       isilonClusters:
          # logical name of PowerScale Cluster
        - clusterName: "cluster1"
@@ -106,6 +108,7 @@ User can query for CSI-PowerScale driver using the following command:
       data:
          cert-0: ""
       ```
+
       Execute command: ```kubectl create -f empty-secret.yaml```
 
 4. Create a CR (Custom Resource) for PowerScale using the sample files provided
@@ -116,6 +119,7 @@ User can query for CSI-PowerScale driver using the following command:
    | --------- | ----------- | -------- |-------- |
    | dnsPolicy | Determines the DNS Policy of the Node service | Yes | ClusterFirstWithHostNet |
    | fsGroupPolicy | Defines which FS Group policy mode to be used, Supported modes `None, File and ReadWriteOnceWithFSType` | No | "ReadWriteOnceWithFSType" |
+   | storageCapacity | Enable/Disable storage capacity tracking feature | No | true |
    | X_CSI_MAX_PATH_LIMIT | Defines the maximum length of path for a volume | No | 192 |
    | ***Common parameters for node and controller*** |
    | CSI_ENDPOINT | The UNIX socket address for handling gRPC calls | No | /var/run/csi/csi.sock |
@@ -141,16 +145,18 @@ User can query for CSI-PowerScale driver using the following command:
    | leader-election-renew-deadline   | Duration, that the acting leader will retry refreshing leadership before giving up  | No | 15s |
    | leader-election-retry-period   | Duration, the LeaderElector clients should wait between tries of actions  | No | 5s |
 
-6.  Execute the following command to create PowerScale custom resource:
+6. Execute the following command to create PowerScale custom resource:
     ```kubectl create -f <input_sample_file.yaml>``` .
     This command will deploy the CSI-PowerScale driver in the namespace specified in the input YAML file.
 
 **Note** :
+
    1. From CSI-PowerScale v1.6.0 and higher, Storage class and VolumeSnapshotClass will **not** be created as part of driver deployment. The user has to create Storageclass and Volume Snapshot Class.
    2. "Kubelet config dir path" is not yet configurable in case of Operator based driver installation.
    3. Also, snapshotter and resizer sidecars are not optional to choose, it comes default with Driver installation.
 
 ## Volume Health Monitoring
+
 This feature is introduced in CSI Driver for PowerScale version 2.1.0.
 
 ### Operator based installation

From 25efcaa5707c3f2a8fe49b47cefff29885af3582 Mon Sep 17 00:00:00 2001
From: Chiman Jain <chimanjain15@gmail.com>
Date: Fri, 12 May 2023 15:18:36 +0530
Subject: [PATCH 13/13] Update codeowner

---
 .github/CODEOWNERS | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
index 00d21dd76f..82cf246a59 100644
--- a/.github/CODEOWNERS
+++ b/.github/CODEOWNERS
@@ -7,6 +7,7 @@
 # order is alphabetical for easier maintenance.
 #
 # Bharath Sreekanth (bharathsreekanth)
+# Chiman Jain (chimanjain)
 # Deepak Ghivari (Deepak-Ghivari)
 # Matt Schmaelzle (mjsdell)
 # Mukesh Gandharva (mgandharva)
@@ -17,4 +18,4 @@
 # Sean Gallacher (gallacher)
 # Yamunadevi Shanmugam (shanmydell)
 
-* @bharathsreekanth @Deepak-Ghivari @gallacher @mgandharva @mjsdell @prablr79 @rajendraindukuri @rajkumar-palani @rsedlock1958 @shanmydell
+* @bharathsreekanth @chimanjain @Deepak-Ghivari @gallacher @mgandharva @mjsdell @prablr79 @rajendraindukuri @rajkumar-palani @rsedlock1958 @shanmydell
