diff --git a/v2.7.1/404.html b/v2.7.1/404.html
index cf774a2..fca89c9 100644
--- a/v2.7.1/404.html
+++ b/v2.7.1/404.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -288,7 +288,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="/docs/v2.7.1/how-to/upgrade/" class="md-tabs__link">
+        <a href="/docs/v2.7.1/upgrade/" class="md-tabs__link">
           
   
     
@@ -1307,8 +1307,6 @@
       
         
       
-        
-      
     
     
       
@@ -1326,7 +1324,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="/docs/v2.7.1/how-to/upgrade/" class="md-nav__link ">
+            <a href="/docs/v2.7.1/upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1356,31 +1354,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="/docs/v2.7.1/how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1402,35 +1383,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="/docs/v2.7.1/upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="/docs/v2.7.1/how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="/docs/v2.7.1/upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1451,7 +1442,7 @@
   
   
     <li class="md-nav__item">
-      <a href="/docs/v2.7.1/how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="/docs/v2.7.1/upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1472,7 +1463,7 @@
   
   
     <li class="md-nav__item">
-      <a href="/docs/v2.7.1/how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="/docs/v2.7.1/upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1493,7 +1484,7 @@
   
   
     <li class="md-nav__item">
-      <a href="/docs/v2.7.1/how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="/docs/v2.7.1/upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
diff --git a/v2.7.1/CHANGELOG/index.html b/v2.7.1/CHANGELOG/index.html
index 6c6e1ec..3c41163 100644
--- a/v2.7.1/CHANGELOG/index.html
+++ b/v2.7.1/CHANGELOG/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -61,7 +61,7 @@
       
         <meta  property="og:title"  content="Changelog - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/CHANGELOG.png" >
       
@@ -77,7 +77,7 @@
       
         <meta  name="twitter:title"  content="Changelog - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/CHANGELOG.png" >
       
@@ -323,7 +323,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../how-to/upgrade/" class="md-tabs__link">
+        <a href="../upgrade/" class="md-tabs__link">
           
   
     
@@ -1344,8 +1344,6 @@
       
         
       
-        
-      
     
     
       
@@ -1363,7 +1361,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../how-to/upgrade/" class="md-nav__link ">
+            <a href="../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1393,31 +1391,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1439,35 +1420,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1488,7 +1479,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1509,7 +1500,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1530,7 +1521,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -3259,11 +3250,11 @@
         <li class="md-nav__item">
   <a href="#v013-2020-02-24" class="md-nav__link">
     <span class="md-ellipsis">
-      [v0.1.3] - 2020-02-24
+      v0.1.3 - 2020-02-24
     </span>
   </a>
   
-    <nav class="md-nav" aria-label="[v0.1.3] - 2020-02-24">
+    <nav class="md-nav" aria-label="v0.1.3 - 2020-02-24">
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
@@ -3283,11 +3274,11 @@
         <li class="md-nav__item">
   <a href="#v0121-2020-02-21" class="md-nav__link">
     <span class="md-ellipsis">
-      [v0.1.2.1] - 2020-02-21
+      v0.1.2.1 - 2020-02-21
     </span>
   </a>
   
-    <nav class="md-nav" aria-label="[v0.1.2.1] - 2020-02-21">
+    <nav class="md-nav" aria-label="v0.1.2.1 - 2020-02-21">
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
@@ -3316,11 +3307,11 @@
         <li class="md-nav__item">
   <a href="#v010-2020-01-27" class="md-nav__link">
     <span class="md-ellipsis">
-      [v0.1.0] - 2020-01-27
+      v0.1.0 - 2020-01-27
     </span>
   </a>
   
-    <nav class="md-nav" aria-label="[v0.1.0] - 2020-01-27">
+    <nav class="md-nav" aria-label="v0.1.0 - 2020-01-27">
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
@@ -4820,11 +4811,11 @@
         <li class="md-nav__item">
   <a href="#v013-2020-02-24" class="md-nav__link">
     <span class="md-ellipsis">
-      [v0.1.3] - 2020-02-24
+      v0.1.3 - 2020-02-24
     </span>
   </a>
   
-    <nav class="md-nav" aria-label="[v0.1.3] - 2020-02-24">
+    <nav class="md-nav" aria-label="v0.1.3 - 2020-02-24">
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
@@ -4844,11 +4835,11 @@
         <li class="md-nav__item">
   <a href="#v0121-2020-02-21" class="md-nav__link">
     <span class="md-ellipsis">
-      [v0.1.2.1] - 2020-02-21
+      v0.1.2.1 - 2020-02-21
     </span>
   </a>
   
-    <nav class="md-nav" aria-label="[v0.1.2.1] - 2020-02-21">
+    <nav class="md-nav" aria-label="v0.1.2.1 - 2020-02-21">
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
@@ -4877,11 +4868,11 @@
         <li class="md-nav__item">
   <a href="#v010-2020-01-27" class="md-nav__link">
     <span class="md-ellipsis">
-      [v0.1.0] - 2020-01-27
+      v0.1.0 - 2020-01-27
     </span>
   </a>
   
-    <nav class="md-nav" aria-label="[v0.1.0] - 2020-01-27">
+    <nav class="md-nav" aria-label="v0.1.0 - 2020-01-27">
       <ul class="md-nav__list">
         
           <li class="md-nav__item">
@@ -4958,13 +4949,13 @@
   
 
 
-<h1 id="changelog">Changelog</h1>
+<h1 id="changelog">Changelog<a class="headerlink" href="#changelog" title="Permanent link">&para;</a></h1>
 <p>All notable changes to this project will be documented in this file.</p>
 <p>The format is based on <a href="https://keepachangelog.com/en/1.0.0/">Keep a Changelog</a>,
 and this project adheres to <a href="https://semver.org/spec/v2.0.0.html">Semantic Versioning</a>.</p>
-<h2 id="unreleased"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.7.1...HEAD">Unreleased</a></h2>
-<h2 id="v271-2024-11-25"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.7.0...v2.7.1">v2.7.1</a> - 2024-11-25</h2>
-<h3 id="changed">Changed</h3>
+<h2 id="unreleased"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.7.1...HEAD">Unreleased</a><a class="headerlink" href="#unreleased" title="Permanent link">&para;</a></h2>
+<h2 id="v271-2024-11-25"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.7.0...v2.7.1">v2.7.1</a> - 2024-11-25<a class="headerlink" href="#v271-2024-11-25" title="Permanent link">&para;</a></h2>
+<h3 id="changed">Changed<a class="headerlink" href="#changed" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Updated images:<ul>
 <li>DRBD 9.2.12</li>
@@ -4972,12 +4963,12 @@ <h3 id="changed">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v270-2024-11-11"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.6.0...v2.7.0">v2.7.0</a> - 2024-11-11</h2>
-<h3 id="added">Added</h3>
+<h2 id="v270-2024-11-11"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.6.0...v2.7.0">v2.7.0</a> - 2024-11-11<a class="headerlink" href="#v270-2024-11-11" title="Permanent link">&para;</a></h2>
+<h3 id="added">Added<a class="headerlink" href="#added" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Option to select IP Family to use for LINSTOR control traffic.</li>
 </ul>
-<h3 id="changed_1">Changed</h3>
+<h3 id="changed_1">Changed<a class="headerlink" href="#changed_1" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Reconciliation of a Satellites network interfaces now also deletes unneeded interfaces.</li>
 <li>Satellites try to detect the LVM configuration on the host, reusing locks and udev rules if available.</li>
@@ -4989,12 +4980,12 @@ <h3 id="changed_1">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v260-2024-09-04"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.5.2...v2.6.0">v2.6.0</a> - 2024-09-04</h2>
-<h3 id="added_1">Added</h3>
+<h2 id="v260-2024-09-04"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.5.2...v2.6.0">v2.6.0</a> - 2024-09-04<a class="headerlink" href="#v260-2024-09-04" title="Permanent link">&para;</a></h2>
+<h3 id="added_1">Added<a class="headerlink" href="#added_1" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Support wildcard patterns when referencing property values from node labels and annotations.</li>
 </ul>
-<h3 id="changed_2">Changed</h3>
+<h3 id="changed_2">Changed<a class="headerlink" href="#changed_2" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Updated images:<ul>
 <li>LINSTOR 1.29.0</li>
@@ -5003,13 +4994,13 @@ <h3 id="changed_2">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v252-2024-07-17"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.5.1...v2.5.2">v2.5.2</a> - 2024-07-17</h2>
-<h3 id="added_2">Added</h3>
+<h2 id="v252-2024-07-17"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.5.1...v2.5.2">v2.5.2</a> - 2024-07-17<a class="headerlink" href="#v252-2024-07-17" title="Permanent link">&para;</a></h2>
+<h3 id="added_2">Added<a class="headerlink" href="#added_2" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Option to specify custom CA certificate resources for TLS configuration.</li>
 <li>Ensure all Certificate resources have <code>dnsNames</code> set.</li>
 </ul>
-<h3 id="changed_3">Changed</h3>
+<h3 id="changed_3">Changed<a class="headerlink" href="#changed_3" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Updated images:<ul>
 <li>LINSTOR 1.28.0</li>
@@ -5021,16 +5012,16 @@ <h3 id="changed_3">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="fixed">Fixed</h3>
+<h3 id="fixed">Fixed<a class="headerlink" href="#fixed" title="Permanent link">&para;</a></h3>
 <ul>
 <li>The operator will no longer restart reconciliation on every change to <code>ServiceAccount</code> resources.</li>
 </ul>
-<h2 id="v251-2024-05-02"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.5.0...v2.5.1">v2.5.1</a> - 2024-05-02</h2>
-<h3 id="added_3">Added</h3>
+<h2 id="v251-2024-05-02"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.5.0...v2.5.1">v2.5.1</a> - 2024-05-02<a class="headerlink" href="#v251-2024-05-02" title="Permanent link">&para;</a></h2>
+<h3 id="added_3">Added<a class="headerlink" href="#added_3" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Default PriorityClasses for all components</li>
 </ul>
-<h3 id="changed_4">Changed</h3>
+<h3 id="changed_4">Changed<a class="headerlink" href="#changed_4" title="Permanent link">&para;</a></h3>
 <ul>
 <li>New DRBD loader detection for:<ul>
 <li>Ubuntu Noble Numbat (24.04)</li>
@@ -5043,12 +5034,12 @@ <h3 id="changed_4">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v250-2024-04-03"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.4.1...v2.5.0">v2.5.0</a> - 2024-04-03</h2>
-<h3 id="added_4">Added</h3>
+<h2 id="v250-2024-04-03"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.4.1...v2.5.0">v2.5.0</a> - 2024-04-03<a class="headerlink" href="#v250-2024-04-03" title="Permanent link">&para;</a></h2>
+<h3 id="added_4">Added<a class="headerlink" href="#added_4" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Support for managing ZFS Storage Pools using <code>LinstorSatelliteConfiguration</code>.</li>
 </ul>
-<h3 id="changed_5">Changed</h3>
+<h3 id="changed_5">Changed<a class="headerlink" href="#changed_5" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Updated images:<ul>
 <li>LINSTOR 1.27.0</li>
@@ -5058,8 +5049,8 @@ <h3 id="changed_5">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v241-2024-03-06"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.4.0...v2.4.1">v2.4.1</a> - 2024-03-06</h2>
-<h3 id="added_5">Added</h3>
+<h2 id="v241-2024-03-06"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.4.0...v2.4.1">v2.4.1</a> - 2024-03-06<a class="headerlink" href="#v241-2024-03-06" title="Permanent link">&para;</a></h2>
+<h3 id="added_5">Added<a class="headerlink" href="#added_5" title="Permanent link">&para;</a></h3>
 <ul>
 <li>New DRBD loader detection for:<ul>
 <li>Debian 12 (Bookworm)</li>
@@ -5070,7 +5061,7 @@ <h3 id="added_5">Added</h3>
   relabelling enabled.</li>
 <li>Alerts for offline LINSTOR Controller and Satellites.</li>
 </ul>
-<h3 id="changed_6">Changed</h3>
+<h3 id="changed_6">Changed<a class="headerlink" href="#changed_6" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Use node label instead of pod name for Prometheus alerting descriptions.</li>
 <li>Updated images:<ul>
@@ -5079,18 +5070,18 @@ <h3 id="changed_6">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v240-2024-01-30"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.3.0...v2.4.0">v2.4.0</a> - 2024-01-30</h2>
-<h3 id="added_6">Added</h3>
+<h2 id="v240-2024-01-30"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.3.0...v2.4.0">v2.4.0</a> - 2024-01-30<a class="headerlink" href="#v240-2024-01-30" title="Permanent link">&para;</a></h2>
+<h3 id="added_6">Added<a class="headerlink" href="#added_6" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Validating Webhook for Piraeus StorageClasses.</li>
 </ul>
-<h3 id="breaking">Breaking</h3>
+<h3 id="breaking">Breaking<a class="headerlink" href="#breaking" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Use DaemonSet to manage Satellite resources instead of bare Pods. This enables better integration with
   common administrative tasks such as node draining. This change should be transparent for users, any patches
   applied on the satellite Pods are internally converted to work on the new DaemonSet instead.</li>
 </ul>
-<h3 id="changed_7">Changed</h3>
+<h3 id="changed_7">Changed<a class="headerlink" href="#changed_7" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Change default monitoring address for DRBD Reactor to support systems with IPv6 completely disabled.</li>
 <li>Updated images:<ul>
@@ -5102,8 +5093,8 @@ <h3 id="changed_7">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v230-2023-12-05"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.2.0...v2.3.0">v2.3.0</a> - 2023-12-05</h2>
-<h3 id="added_7">Added</h3>
+<h2 id="v230-2023-12-05"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.2.0...v2.3.0">v2.3.0</a> - 2023-12-05<a class="headerlink" href="#v230-2023-12-05" title="Permanent link">&para;</a></h2>
+<h3 id="added_7">Added<a class="headerlink" href="#added_7" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Add a new option <code>.spec.internalTLS.tlsHandshakeDaemon</code> to enable deployment of <code>tlshd</code> alongside the LINSTOR
   Satellite.</li>
@@ -5118,7 +5109,7 @@ <h3 id="added_7">Added</h3>
 <li>Shortcut to modify the pod of a satellite by adding a <code>LinstorSatelliteConfiguration.spec.podTemplate</code>, which is
   a shortcut for creating a <code>.spec.patches</code> patch.</li>
 </ul>
-<h3 id="changed_8">Changed</h3>
+<h3 id="changed_8">Changed<a class="headerlink" href="#changed_8" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Fixed service resources relying on default protocol version.</li>
 <li>Moved NetworkPolicy for DRBD out of default deployed resources.</li>
@@ -5131,8 +5122,8 @@ <h3 id="changed_8">Changed</h3>
 </li>
 <li>Add a default toleration for the HA Controller taints to the operator.</li>
 </ul>
-<h2 id="v220-2023-08-31"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.1.1...v2.2.0">v2.2.0</a> - 2023-08-31</h2>
-<h3 id="added_8">Added</h3>
+<h2 id="v220-2023-08-31"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.1.1...v2.2.0">v2.2.0</a> - 2023-08-31<a class="headerlink" href="#v220-2023-08-31" title="Permanent link">&para;</a></h2>
+<h3 id="added_8">Added<a class="headerlink" href="#added_8" title="Permanent link">&para;</a></h3>
 <ul>
 <li>A new <code>LinstorNodeConnection</code> resource, used to configure the LINSTOR Node Connection feature in a Kubernetes way.</li>
 <li>Allow image configuration to be customized by adding additional items to the config map. Items using a "greater" key
@@ -5142,7 +5133,7 @@ <h3 id="added_8">Added</h3>
 <li>Automatically set SELinux labels when loading kernel modules.</li>
 <li>Allow more complex node selection by adding <code>LinstorCluster.spec.nodeAffinity</code>.</li>
 </ul>
-<h3 id="changed_9">Changed</h3>
+<h3 id="changed_9">Changed<a class="headerlink" href="#changed_9" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Upgrade to operator-sdk 1.29</li>
 <li>Upgrade to kubebuilder v4 layout</li>
@@ -5153,24 +5144,24 @@ <h3 id="changed_9">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="removed">Removed</h3>
+<h3 id="removed">Removed<a class="headerlink" href="#removed" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Disable operator metrics by default. This removes a dependency on an external container.</li>
 <li>Dependency on cert-manager for initial deployment.</li>
 </ul>
-<h3 id="fixed_1">Fixed</h3>
+<h3 id="fixed_1">Fixed<a class="headerlink" href="#fixed_1" title="Permanent link">&para;</a></h3>
 <ul>
 <li>A crash caused by insufficient permissions on the LINSTOR Controller.</li>
 <li>Satellite will now restart if the Pods terminated for unexpected reasons.</li>
 </ul>
-<h2 id="v211-2023-05-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.1.0...v2.1.1">v2.1.1</a> - 2023-05-24</h2>
-<h3 id="added_9">Added</h3>
+<h2 id="v211-2023-05-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.1.0...v2.1.1">v2.1.1</a> - 2023-05-24<a class="headerlink" href="#v211-2023-05-24" title="Permanent link">&para;</a></h2>
+<h3 id="added_9">Added<a class="headerlink" href="#added_9" title="Permanent link">&para;</a></h3>
 <ul>
 <li>LINSTOR Controller deployment now runs DB migrations as a separate init container, creating
   a backup of current DB state if needed.</li>
 <li>Apply global rate limit to LINSTOR API, defaulting to 100 qps.</li>
 </ul>
-<h3 id="changed_10">Changed</h3>
+<h3 id="changed_10">Changed<a class="headerlink" href="#changed_10" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Store LINSTOR Satellite logs on the host.</li>
 <li>Updated images:<ul>
@@ -5182,19 +5173,19 @@ <h3 id="changed_10">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="fixed_2">Fixed</h3>
+<h3 id="fixed_2">Fixed<a class="headerlink" href="#fixed_2" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Fixed a bug where <code>LinstorSatellite</code> resources would be not be cleaned up when the satellite is already gone.</li>
 <li>Fixed a bug where the LINSTOR Controller would never report readiness when TLS is enabled.</li>
 <li>Fixed order in which patches are applied. Always apply user patches last.</li>
 </ul>
-<h2 id="v210-2023-04-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.0.1...v2.1.0">v2.1.0</a> - 2023-04-24</h2>
-<h3 id="added_10">Added</h3>
+<h2 id="v210-2023-04-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.0.1...v2.1.0">v2.1.0</a> - 2023-04-24<a class="headerlink" href="#v210-2023-04-24" title="Permanent link">&para;</a></h2>
+<h3 id="added_10">Added<a class="headerlink" href="#added_10" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Ability to skip deploying the LINSTOR Controller by setting <code>LinstorCluster.spec.externalController</code>.</li>
 <li>Automatically reconcile changed image configuration.</li>
 </ul>
-<h3 id="changed_11">Changed</h3>
+<h3 id="changed_11">Changed<a class="headerlink" href="#changed_11" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Fix an issue where the CSI node driver would use the CSI socket not through the expected path in the container.</li>
 <li>Updated images:<ul>
@@ -5207,30 +5198,30 @@ <h3 id="changed_11">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v201-2023-03-08"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.0.0...v2.0.1">v2.0.1</a> - 2023-03-08</h2>
-<h3 id="added_11">Added</h3>
+<h2 id="v201-2023-03-08"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v2.0.0...v2.0.1">v2.0.1</a> - 2023-03-08<a class="headerlink" href="#v201-2023-03-08" title="Permanent link">&para;</a></h2>
+<h3 id="added_11">Added<a class="headerlink" href="#added_11" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>drbd-shutdown-guard</code> init-container, installing a systemd unit that runs on shutdown.
   It's purpose is to run <code>drbdsetup secondary --force</code> during shutdown, so that systemd can unmount all volumes, even
   with <code>suspend-io</code>.</li>
 </ul>
-<h3 id="changed_12">Changed</h3>
+<h3 id="changed_12">Changed<a class="headerlink" href="#changed_12" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Updated LINSTOR CSI to 1.0.0, mounting the <code>/run/mount</code> directory from the host to enable the <code>_netdev</code> mount option.</li>
 </ul>
-<h3 id="fixed_3">Fixed</h3>
+<h3 id="fixed_3">Fixed<a class="headerlink" href="#fixed_3" title="Permanent link">&para;</a></h3>
 <ul>
 <li>HA Controller deployment requires additional rules to run on OpenShift.</li>
 </ul>
-<h2 id="v200-2023-02-23"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.10.0...v2.0.0">v2.0.0</a> - 2023-02-23</h2>
-<h3 id="breaking_1">Breaking</h3>
+<h2 id="v200-2023-02-23"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.10.0...v2.0.0">v2.0.0</a> - 2023-02-23<a class="headerlink" href="#v200-2023-02-23" title="Permanent link">&para;</a></h2>
+<h3 id="breaking_1">Breaking<a class="headerlink" href="#breaking_1" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Removed existing CRD <code>LinstorController</code>, <code>LinstorSatelliteSet</code> and <code>LinstorCSIDriver</code>.</li>
 <li>Helm chart deprecated in favor of new <code>kustomize</code> deployment.</li>
 <li>Helm chart changed to only deploy the Operator. The LinstorCluster resource to create the storage cluster needs to be
   created separately.</li>
 </ul>
-<h3 id="added_12">Added</h3>
+<h3 id="added_12">Added<a class="headerlink" href="#added_12" title="Permanent link">&para;</a></h3>
 <ul>
 <li>New CRDs to control storage cluster: <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code>.</li>
 <li><a href="../tutorial/">Tutorials</a> on how to get started.</li>
@@ -5241,13 +5232,13 @@ <h3 id="added_12">Added</h3>
 <li>Default deployment for HA Controller. Since we switch to defaulting to <code>suspend-io</code> for lost quorum, we should include
   a way for Pods to get unstuck.</li>
 </ul>
-<h2 id="v1100-2022-10-18"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.9.1...v1.10.0">v1.10.0</a> - 2022-10-18</h2>
-<h3 id="added_13">Added</h3>
+<h2 id="v1100-2022-10-18"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.9.1...v1.10.0">v1.10.0</a> - 2022-10-18<a class="headerlink" href="#v1100-2022-10-18" title="Permanent link">&para;</a></h2>
+<h3 id="added_13">Added<a class="headerlink" href="#added_13" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Can set the variable <code>mountDrbdResourceDirectoriesFromHost</code> in the Helm chart to create hostPath Volumes for DRBD and
   LINSTOR configuration directories for the satellite set.</li>
 </ul>
-<h3 id="changed_13">Changed</h3>
+<h3 id="changed_13">Changed<a class="headerlink" href="#changed_13" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Change default bind address for satellite monitoring to use IPv6 anylocal <code>[::]</code>. This will still to work on IPv4
   only systems with IPv6 disabled via sysctl.</li>
@@ -5259,23 +5250,23 @@ <h3 id="changed_13">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="fixed_4">Fixed</h3>
+<h3 id="fixed_4">Fixed<a class="headerlink" href="#fixed_4" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Comparing IP addresses for registered components uses golang's built-in net.IP type.</li>
 <li>Restoring satellites after eviction only happens if the node is ready.</li>
 </ul>
-<h2 id="v191-2022-07-27"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.9.0...v1.9.1">v1.9.1</a> - 2022-07-27</h2>
-<h3 id="fixed_5">Fixed</h3>
+<h2 id="v191-2022-07-27"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.9.0...v1.9.1">v1.9.1</a> - 2022-07-27<a class="headerlink" href="#v191-2022-07-27" title="Permanent link">&para;</a></h2>
+<h3 id="fixed_5">Fixed<a class="headerlink" href="#fixed_5" title="Permanent link">&para;</a></h3>
 <ul>
 <li>ServiceMonitor resources can't be patched, instead we recreate them.</li>
 </ul>
-<h2 id="v190-2022-07-20"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.8.2...v1.9.0">v1.9.0</a> - 2022-07-20</h2>
-<h3 id="added_14">Added</h3>
+<h2 id="v190-2022-07-20"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.8.2...v1.9.0">v1.9.0</a> - 2022-07-20<a class="headerlink" href="#v190-2022-07-20" title="Permanent link">&para;</a></h2>
+<h3 id="added_14">Added<a class="headerlink" href="#added_14" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Support for custom labels and annotations with added options to <code>values.yaml</code>.</li>
 <li>Instructions for deploying the affinity controller.</li>
 </ul>
-<h3 id="changed_14">Changed</h3>
+<h3 id="changed_14">Changed<a class="headerlink" href="#changed_14" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Satellite operator now reports basic satellite status even if controller is not reachable</li>
 <li>Query single satellite devices to receive errors when the satellite is offline instead of assuming
@@ -5291,12 +5282,12 @@ <h3 id="changed_14">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="fixed_6">Fixed</h3>
+<h3 id="fixed_6">Fixed<a class="headerlink" href="#fixed_6" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>last-applied-configuration</code>annotation was never updated, so updating of some fields was not performed correctly.</li>
 </ul>
-<h2 id="v182-2022-05-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.8.1...v1.8.2">v1.8.2</a> - 2022-05-24</h2>
-<h3 id="added_15">Added</h3>
+<h2 id="v182-2022-05-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.8.1...v1.8.2">v1.8.2</a> - 2022-05-24<a class="headerlink" href="#v182-2022-05-24" title="Permanent link">&para;</a></h2>
+<h3 id="added_15">Added<a class="headerlink" href="#added_15" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Option to disable creating monitoring resources (Services and ServiceMonitors)</li>
 <li>Add options <code>csi.controllerSidecars</code>, <code>csi.controllerExtraVolumes</code>, <code>csi.nodeSidecars</code>, <code>csi.nodeExtraVolumes</code>,
@@ -5306,7 +5297,7 @@ <h3 id="added_15">Added</h3>
   <code>operator.satelliteSet.monitoringBindAddress</code> to allow specifying bind address.</li>
 <li>Add example values and doc reference to run piraeus-operator with rbac-proxy.</li>
 </ul>
-<h3 id="changed_15">Changed</h3>
+<h3 id="changed_15">Changed<a class="headerlink" href="#changed_15" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Default images:<ul>
 <li>LINSTOR 1.18.2</li>
@@ -5315,12 +5306,12 @@ <h3 id="changed_15">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="removed_1">Removed</h3>
+<h3 id="removed_1">Removed<a class="headerlink" href="#removed_1" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Get rid of operator-sdk binary, use native controller-gen instead</li>
 </ul>
-<h2 id="v181-2022-05-12"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.8.0...v1.8.1">v1.8.1</a> - 2022-05-12</h2>
-<h3 id="changed_16">Changed</h3>
+<h2 id="v181-2022-05-12"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.8.0...v1.8.1">v1.8.1</a> - 2022-05-12<a class="headerlink" href="#v181-2022-05-12" title="Permanent link">&para;</a></h2>
+<h3 id="changed_16">Changed<a class="headerlink" href="#changed_16" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Default images:<ul>
 <li>LINSTOR 1.18.1</li>
@@ -5330,13 +5321,13 @@ <h3 id="changed_16">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="added_16">Added</h3>
+<h3 id="added_16">Added<a class="headerlink" href="#added_16" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Upgrades involving k8s databases no long require manually confirming a backup exists using
   <code>--set IHaveBackedUpAllMyLinstorResources=true</code>.</li>
 </ul>
-<h2 id="v180-2022-03-15"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.7.1...v1.8.0">v1.8.0</a> - 2022-03-15</h2>
-<h3 id="added_17">Added</h3>
+<h2 id="v180-2022-03-15"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.7.1...v1.8.0">v1.8.0</a> - 2022-03-15<a class="headerlink" href="#v180-2022-03-15" title="Permanent link">&para;</a></h2>
+<h3 id="added_17">Added<a class="headerlink" href="#added_17" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Allow setting the number of parallel requests created by the CSI sidecars. This limits the load on the LINSTOR
   backend, which could easily overload when creating many volumes at once.</li>
@@ -5344,7 +5335,7 @@ <h3 id="added_17">Added</h3>
 <li>Automatic certificates generation using Helm or Cert-manager</li>
 <li>HA Controller and CSI components now wait for the LINSTOR API to be initialized using InitContainers.</li>
 </ul>
-<h3 id="changed_17">Changed</h3>
+<h3 id="changed_17">Changed<a class="headerlink" href="#changed_17" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Create backups of LINSTOR resource if the "k8s" database backend is used <em>and</em> an image change is detected. Backups
   are stored in Secret resources as a <code>tar.gz</code>. If the secret would get too big, the backup can be downloaded from
@@ -5370,13 +5361,13 @@ <h3 id="changed_17">Changed</h3>
 <li>Use cached storage pool response to avoid causing excessive load on LINSTOR satellites.</li>
 <li>Protect LINSTOR passphrase from accidental deletion by using a finalizer.</li>
 </ul>
-<h3 id="breaking_2">Breaking</h3>
+<h3 id="breaking_2">Breaking<a class="headerlink" href="#breaking_2" title="Permanent link">&para;</a></h3>
 <ul>
 <li>If you have SSL configured, then the certificates must be regenerated in PEM format.
-  Learn more in the <a href="../how-to/upgrade/UPGRADE/#upgrade-from-v10-to-v11">upgrade guide</a>.</li>
+  Learn more in the <a href="../upgrade/#upgrade-from-v10-to-v11">upgrade guide</a>.</li>
 </ul>
-<h2 id="v171-2022-01-18"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.7.0...v1.7.1">v1.7.1</a> - 2022-01-18</h2>
-<h3 id="added_18">Added</h3>
+<h2 id="v171-2022-01-18"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.7.0...v1.7.1">v1.7.1</a> - 2022-01-18<a class="headerlink" href="#v171-2022-01-18" title="Permanent link">&para;</a></h2>
+<h3 id="added_18">Added<a class="headerlink" href="#added_18" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Allow the external-provisioner and external-snapshotter access to secrets. This is required to support StorageClass
   and SnapshotClass <a href="https://kubernetes-csi.github.io/docs/secrets-and-credentials-storage-class.html">secrets</a>.</li>
@@ -5389,13 +5380,13 @@ <h3 id="added_18">Added</h3>
   <code>operator.satelliteSet.kernelModuleInjectionAdditionalSourceDirectory</code></a></li>
 <li>etcd-chart: add option to set priorityClassName.</li>
 </ul>
-<h3 id="fixed_7">Fixed</h3>
+<h3 id="fixed_7">Fixed<a class="headerlink" href="#fixed_7" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Use correct secret name when setting up TLS for satellites</li>
 <li>Correctly configure ServiceMonitor resource if TLS is enabled for LINSTOR Controller.</li>
 </ul>
-<h2 id="v170-2021-12-14"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.6.0...v1.7.0">v1.7.0</a> - 2021-12-14</h2>
-<h3 id="added_19">Added</h3>
+<h2 id="v170-2021-12-14"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.6.0...v1.7.0">v1.7.0</a> - 2021-12-14<a class="headerlink" href="#v170-2021-12-14" title="Permanent link">&para;</a></h2>
+<h3 id="added_19">Added<a class="headerlink" href="#added_19" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>pv-hostpath</code>: automatically determine on which nodes PVs should be created if no override is given.</li>
 <li>Automatically add labels on Kubernetes Nodes to LINSTOR satellites as Auxiliary Properties. This enables using
@@ -5404,7 +5395,7 @@ <h3 id="added_19">Added</h3>
 <li>Automatically create a LINSTOR passphrase when none is configured.</li>
 <li>Automatic eviction and deletion of offline satellites if the Kubernetes node object was also deleted.</li>
 </ul>
-<h3 id="changed_18">Changed</h3>
+<h3 id="changed_18">Changed<a class="headerlink" href="#changed_18" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Default images:<ul>
 <li><code>quay.io/piraeusdatastore/piraeus-server:v1.17.0</code></li>
@@ -5418,15 +5409,15 @@ <h3 id="changed_18">Changed</h3>
 <li>Enable CSI topology by default, allowing better volume scheduling with <code>volumeBindingMode: WaitForFirstConsumer</code>.</li>
 <li>Disable STORK by default. Instead, we recommend using <code>volumeBindingMode: WaitForFirstConsumer</code> in storage classes.</li>
 </ul>
-<h2 id="v160-2021-09-02"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.5.1...v1.6.0">v1.6.0</a> - 2021-09-02</h2>
-<h3 id="added_20">Added</h3>
+<h2 id="v160-2021-09-02"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.5.1...v1.6.0">v1.6.0</a> - 2021-09-02<a class="headerlink" href="#v160-2021-09-02" title="Permanent link">&para;</a></h2>
+<h3 id="added_20">Added<a class="headerlink" href="#added_20" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Allow CSI to work with distributions that use a kubelet working directory other than <code>/var/lib/kubelet</code>. See
   the <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v1.6.0/doc/helm-values.adoc#csikubeletpath"><code>csi.kubeletPath</code></a> option.</li>
 <li>Enable <a href="https://github.com/kubernetes/enhancements/tree/master/keps/sig-storage/1472-storage-capacity-tracking">Storage Capacity Tacking</a>. This enables Kubernetes to base Pod scheduling decisions on remaining storage
   capacity. The feature is in beta and enabled by default starting with Kubernetes 1.21.</li>
 </ul>
-<h3 id="changed_19">Changed</h3>
+<h3 id="changed_19">Changed<a class="headerlink" href="#changed_19" title="Permanent link">&para;</a></h3>
 <ul>
 <li>
 <p>Disable Stork Health Monitoring by default. Stork cannot distinguish between control plane and data plane issues,
@@ -5447,7 +5438,7 @@ <h3 id="changed_19">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="removed_2">Removed</h3>
+<h3 id="removed_2">Removed<a class="headerlink" href="#removed_2" title="Permanent link">&para;</a></h3>
 <ul>
 <li>The cluster-wide snapshot controller is no longer deployed as a dependency of the piraeus-operator chart.
   Instead, separate charts are available on <a href="https://artifacthub.io/packages/search?repo=piraeus-charts">artifacthub.io</a>
@@ -5456,8 +5447,8 @@ <h3 id="removed_2">Removed</h3>
 <p>The subchart was removed, as it unnecessarily tied updates of the snapshot controller to piraeus and vice versa. With
   the tightened validation starting with snapshot CRDs <code>v1</code>, moving the snapshot controller to a proper chart seems
   like a good solution.</p>
-<h2 id="v151-2021-06-21"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.5.0...v1.5.1">v1.5.1</a> - 2021-06-21</h2>
-<h3 id="changed_20">Changed</h3>
+<h2 id="v151-2021-06-21"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.5.0...v1.5.1">v1.5.1</a> - 2021-06-21<a class="headerlink" href="#v151-2021-06-21" title="Permanent link">&para;</a></h2>
+<h3 id="changed_20">Changed<a class="headerlink" href="#changed_20" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Default images:<ul>
 <li>Piraeus Server v1.13.0</li>
@@ -5466,8 +5457,8 @@ <h3 id="changed_20">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v150-2021-05-12"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.4.0...v1.5.0">v1.5.0</a> - 2021-05-12</h2>
-<h3 id="added_21">Added</h3>
+<h2 id="v150-2021-05-12"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.4.0...v1.5.0">v1.5.0</a> - 2021-05-12<a class="headerlink" href="#v150-2021-05-12" title="Permanent link">&para;</a></h2>
+<h3 id="added_21">Added<a class="headerlink" href="#added_21" title="Permanent link">&para;</a></h3>
 <ul>
 <li>All operator-managed workloads apply recommended labels. This requires the recreation of Deployments and DaemonSets
   on upgrade. This is automatically handled by the operator, however any customizations applied to the deployments
@@ -5475,7 +5466,7 @@ <h3 id="added_21">Added</h3>
 <li>Use <a href="https://github.com/LINBIT/drbd-reactor/"><code>drbd-reactor</code></a> to expose Prometheus endpoints on each satellite.</li>
 <li>Configure <code>ServiceMonitor</code> resources if they are supported by the cluster (i.e. prometheus operator is configured)</li>
 </ul>
-<h3 id="changed_21">Changed</h3>
+<h3 id="changed_21">Changed<a class="headerlink" href="#changed_21" title="Permanent link">&para;</a></h3>
 <ul>
 <li>CSI Nodes no longer use <code>hostNetwork: true</code>. The pods already got the correct hostname via the downwardAPI and do not
   talk to DRBD's netlink interface directly.</li>
@@ -5488,24 +5479,24 @@ <h3 id="changed_21">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v140-2021-04-07"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.3.1...v1.4.0">v1.4.0</a> - 2021-04-07</h2>
-<h3 id="added_22">Added</h3>
+<h2 id="v140-2021-04-07"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.3.1...v1.4.0">v1.4.0</a> - 2021-04-07<a class="headerlink" href="#v140-2021-04-07" title="Permanent link">&para;</a></h2>
+<h3 id="added_22">Added<a class="headerlink" href="#added_22" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Additional environment variables and Linstor properties can now be set in the <code>LinstorController</code> CRD.</li>
 <li>Set node name variable for Controller Pods, enabling <a href="https://github.com/LINBIT/k8s-await-election/commit/60748fcec722e4c32b8881c4c84957cc50543db2">k8s-await-election</a> to correctly set up the endpoint for
   hairpin mode.</li>
 </ul>
-<h3 id="fixed_8">Fixed</h3>
+<h3 id="fixed_8">Fixed<a class="headerlink" href="#fixed_8" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Update the network address of controller pods if they diverged between Linstor and kubernetes. This can happen after
   a node restart, where a pod is recreated with the same name but different IP address.</li>
 </ul>
-<h2 id="v131-2021-01-14"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.3.0...v1.3.1">v1.3.1</a> - 2021-01-14</h2>
-<h3 id="added_23">Added</h3>
+<h2 id="v131-2021-01-14"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.3.0...v1.3.1">v1.3.1</a> - 2021-01-14<a class="headerlink" href="#v131-2021-01-14" title="Permanent link">&para;</a></h2>
+<h3 id="added_23">Added<a class="headerlink" href="#added_23" title="Permanent link">&para;</a></h3>
 <ul>
 <li>New guide on host preparation <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v1.3.1/doc/host-setup.md">here.</a></li>
 </ul>
-<h3 id="changed_22">Changed</h3>
+<h3 id="changed_22">Changed<a class="headerlink" href="#changed_22" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Default image updated:<ul>
 <li><code>operator.satelliteSet.kernelModuleInjectionImage</code>: <code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.27</code></li>
@@ -5516,8 +5507,8 @@ <h3 id="changed_22">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v130-2020-12-21"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.2.0...v1.3.0">v1.3.0</a> - 2020-12-21</h2>
-<h3 id="added_24">Added</h3>
+<h2 id="v130-2020-12-21"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.2.0...v1.3.0">v1.3.0</a> - 2020-12-21<a class="headerlink" href="#v130-2020-12-21" title="Permanent link">&para;</a></h2>
+<h3 id="added_24">Added<a class="headerlink" href="#added_24" title="Permanent link">&para;</a></h3>
 <ul>
 <li>New component: <code>haController</code> will deploy the <a href="https://github.com/piraeusdatastore/piraeus-ha-controller">Piraeus High Availability Controller</a>.
   More information is available in
@@ -5525,7 +5516,7 @@ <h3 id="added_24">Added</h3>
 <li>Enable strict checking of DRBD parameter to disable usermode helper in container environments.</li>
 <li>Override the image used in "chown" jobs in the <code>pv-hostpath</code> chart by using <code>--set chownerImage=&lt;my-image&gt;</code>.</li>
 </ul>
-<h3 id="changed_23">Changed</h3>
+<h3 id="changed_23">Changed<a class="headerlink" href="#changed_23" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Updated <code>operator-sdk</code> to v0.19.4</li>
 <li>Set CSI component timeout to 1 minute to reduce the number of retries in the CSI driver</li>
@@ -5537,13 +5528,13 @@ <h3 id="changed_23">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="fixed_9">Fixed</h3>
+<h3 id="fixed_9">Fixed<a class="headerlink" href="#fixed_9" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Fixed Helm warnings when setting "csi.controllerAffinity", "operator.controller.affinity" and
   "operator.satelliteSet.storagePools".</li>
 </ul>
-<h2 id="v120-2020-11-18"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.1.0...v1.2.0">v1.2.0</a> - 2020-11-18</h2>
-<h3 id="added_25">Added</h3>
+<h2 id="v120-2020-11-18"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.1.0...v1.2.0">v1.2.0</a> - 2020-11-18<a class="headerlink" href="#v120-2020-11-18" title="Permanent link">&para;</a></h2>
+<h3 id="added_25">Added<a class="headerlink" href="#added_25" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>storagePools</code> can now also set up devices similar to <code>automaticStorageType</code>, but with more fine grained control.
   See the <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v1.2.0/doc/storage.md#preparing-physical-devices">updated storage guide</a></li>
@@ -5560,7 +5551,7 @@ <h3 id="added_25">Added</h3>
 <li>Example settings for openshift</li>
 <li>LINSTOR controller runs with additional GID 1000, to ensure write access to log directory</li>
 </ul>
-<h3 id="changed_24">Changed</h3>
+<h3 id="changed_24">Changed<a class="headerlink" href="#changed_24" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Fixed a bug in <code>pv-hostpath</code> where permissions on the created directory are not applied on all nodes.</li>
 <li>Volumes created by <code>pv-hostpath</code> are now group writable. This makes them easier to integrate with <code>fsGroup</code> settings.</li>
@@ -5575,18 +5566,18 @@ <h3 id="changed_24">Changed</h3>
 </ul>
 </li>
 </ul>
-<h3 id="deprecation">Deprecation</h3>
+<h3 id="deprecation">Deprecation<a class="headerlink" href="#deprecation" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Using <code>automaticStorageType</code> is deprecated. Use the <code>storagePools</code> values instead.</li>
 </ul>
-<h2 id="v110-2020-10-13"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.0.0...v1.1.0">v1.1.0</a> - 2020-10-13</h2>
-<h3 id="breaking_3">Breaking</h3>
+<h2 id="v110-2020-10-13"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v1.0.0...v1.1.0">v1.1.0</a> - 2020-10-13<a class="headerlink" href="#v110-2020-10-13" title="Permanent link">&para;</a></h2>
+<h3 id="breaking_3">Breaking<a class="headerlink" href="#breaking_3" title="Permanent link">&para;</a></h3>
 <ul>
 <li>The LINSTOR controller image given in <code>operator.controller.controllerImage</code> has to have
   its entrypoint set to <a href="https://github.com/LINBIT/k8s-await-election/"><code>k8s-await-election v0.2.0</code></a>
-  or newer. Learn more in the <a href="../how-to/upgrade/UPGRADE/#upgrade-from-v10-to-v11">upgrade guide</a>.</li>
+  or newer. Learn more in the <a href="../upgrade/#upgrade-from-v10-to-v11">upgrade guide</a>.</li>
 </ul>
-<h3 id="added_26">Added</h3>
+<h3 id="added_26">Added<a class="headerlink" href="#added_26" title="Permanent link">&para;</a></h3>
 <ul>
 <li>LINSTOR controller can be started with multiple replicas. See <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v1.1.0/doc/helm-values.adoc#operatorcontrollerreplicas">
   <code>operator.controller.replicas</code></a>.
@@ -5600,7 +5591,7 @@ <h3 id="added_26">Added</h3>
 <li>The new <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v1.1.0/doc/helm-values.adoc#psp">helm section <code>psp.*</code></a> can automatically configure the ServiceAccount
   of all components to use the appropriate <a href="https://kubernetes.io/docs/concepts/policy/pod-security-policy/">PSP</a> roles.</li>
 </ul>
-<h3 id="changed_25">Changed</h3>
+<h3 id="changed_25">Changed<a class="headerlink" href="#changed_25" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Default values:<ul>
 <li><code>operator.controller.controllerImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.9.0</code></li>
@@ -5611,14 +5602,14 @@ <h3 id="changed_25">Changed</h3>
 </li>
 <li>linstor-controller no longer starts in a privileged container.</li>
 </ul>
-<h3 id="removed_3">Removed</h3>
+<h3 id="removed_3">Removed<a class="headerlink" href="#removed_3" title="Permanent link">&para;</a></h3>
 <ul>
 <li>legacy CRDs (LinstorControllerSet, LinstorNodeSet) have been removed.</li>
 <li><code>v1alpha</code> CRD versions have been removed.</li>
 <li>default pull secret <code>drbdiocred</code> removed. To keep using it, use <code>--set drbdRepoCred=drbdiocred</code>.</li>
 </ul>
-<h2 id="v100-2020-08-06"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.5.0...v1.0.0">v1.0.0</a> - 2020-08-06</h2>
-<h3 id="added_27">Added</h3>
+<h2 id="v100-2020-08-06"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.5.0...v1.0.0">v1.0.0</a> - 2020-08-06<a class="headerlink" href="#v100-2020-08-06" title="Permanent link">&para;</a></h2>
+<h3 id="added_27">Added<a class="headerlink" href="#added_27" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>v1</code> of all CRDs</li>
 <li>Central value for controller image pull policy of all pods. Use <code>--set global.imagePullPolicy=&lt;value&gt;</code> on
@@ -5654,7 +5645,7 @@ <h3 id="added_27">Added</h3>
 <li><code>stork.schedulerTag</code> can override the automatically chosen tag for the <code>kube-scheduler</code> image.
   Previously, the tag always matched the kubernetes release.</li>
 </ul>
-<h3 id="changed_26">Changed</h3>
+<h3 id="changed_26">Changed<a class="headerlink" href="#changed_26" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Renamed <code>LinstorNodeSet</code> to <code>LinstorSatelliteSet</code>. This brings the operator in line with other LINSTOR resources.
   Existing <code>LinstorNodeSet</code> resources will automatically be migrated to <code>LinstorSatelliteSet</code>.</li>
@@ -5695,8 +5686,8 @@ <h3 id="changed_26">Changed</h3>
 <li>Renamed <code>kernelModImage</code> to <code>kernelModuleInjectionImage</code></li>
 <li>Renamed <code>drbdKernelModuleInjectionMode</code> to <code>KernelModuleInjectionMode</code></li>
 </ul>
-<h2 id="v050-2020-06-29"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.4.1...v0.5.0">v0.5.0</a> - 2020-06-29</h2>
-<h3 id="added_28">Added</h3>
+<h2 id="v050-2020-06-29"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.4.1...v0.5.0">v0.5.0</a> - 2020-06-29<a class="headerlink" href="#v050-2020-06-29" title="Permanent link">&para;</a></h2>
+<h3 id="added_28">Added<a class="headerlink" href="#added_28" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Support volume resizing with newer CSI versions.</li>
 <li>A new Helm chart <code>csi-snapshotter</code> that deploys extra components needed for volume snapshots.</li>
@@ -5707,8 +5698,8 @@ <h3 id="added_28">Added</h3>
 <p>Automatic deployment of <a href="https://github.com/libopenstorage/stork">Stork</a> scheduler configured for LINSTOR.</p>
 </li>
 </ul>
-<h3 id="removed_4">Removed</h3>
-<h3 id="changed_27">Changed</h3>
+<h3 id="removed_4">Removed<a class="headerlink" href="#removed_4" title="Permanent link">&para;</a></h3>
+<h3 id="changed_27">Changed<a class="headerlink" href="#changed_27" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Replaced <code>bitnami/etcd</code> dependency with vendored custom version
   Some important keys for the <code>etcd</code> helm chart have changed:<ul>
@@ -5728,19 +5719,19 @@ <h3 id="changed_27">Changed</h3>
 </ul>
 </li>
 </ul>
-<h2 id="v041-2020-06-10"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.4.0...v0.4.1">v0.4.1</a> - 2020-06-10</h2>
-<h3 id="added_29">Added</h3>
+<h2 id="v041-2020-06-10"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.4.0...v0.4.1">v0.4.1</a> - 2020-06-10<a class="headerlink" href="#v041-2020-06-10" title="Permanent link">&para;</a></h2>
+<h3 id="added_29">Added<a class="headerlink" href="#added_29" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Automatic storage pool creation via <code>automaticStorageType</code> on <code>LinstorNodeSet</code>. If this option is set, LINSTOR
   will create a storage pool based on all available devices on a node.</li>
 </ul>
-<h3 id="changed_28">Changed</h3>
+<h3 id="changed_28">Changed<a class="headerlink" href="#changed_28" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Moved storage documentation to the <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v0.4.1/doc/storage.md">storage guide</a></li>
 <li>Helm: update default images</li>
 </ul>
-<h2 id="v040-2020-06-05"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.3.0...v0.4.0">v0.4.0</a> - 2020-06-05</h2>
-<h3 id="added_30">Added</h3>
+<h2 id="v040-2020-06-05"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.3.0...v0.4.0">v0.4.0</a> - 2020-06-05<a class="headerlink" href="#v040-2020-06-05" title="Permanent link">&para;</a></h2>
+<h3 id="added_30">Added<a class="headerlink" href="#added_30" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Secured database connection for Linstor: When using the <code>etcd</code> connector, you can specify a secret containing a CA
   certificate to switch from HTTP to HTTPS communication.</li>
@@ -5754,11 +5745,11 @@ <h3 id="added_30">Added</h3>
 <li>Linstor controller endpoint can now be customized for all resources. If not specified, the old default values will be
   filled in.</li>
 </ul>
-<h3 id="removed_5">Removed</h3>
+<h3 id="removed_5">Removed<a class="headerlink" href="#removed_5" title="Permanent link">&para;</a></h3>
 <ul>
 <li>NodeSet service (<code>piraeus-op-ns</code>) was replaced by the ControllerSet service (<code>piraeus-op-cs</code>) everywhere</li>
 </ul>
-<h3 id="changed_29">Changed</h3>
+<h3 id="changed_29">Changed<a class="headerlink" href="#changed_29" title="Permanent link">&para;</a></h3>
 <ul>
 <li>CSI storage driver setup: move setup from helm to go operator. This is mostly an internal change.
   These changes may be of note if you used a non-default CSI configuration:<ul>
@@ -5775,8 +5766,8 @@ <h3 id="changed_29">Changed</h3>
   If no ServiceAccounts are named, the implicitly created accounts from previous deployments will be used.</li>
 <li>Helm: update default images</li>
 </ul>
-<h2 id="v030-2020-05-08"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.2.2...v0.3.0">v0.3.0</a> - 2020-05-08</h2>
-<h3 id="changed_30">Changed</h3>
+<h2 id="v030-2020-05-08"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.2.2...v0.3.0">v0.3.0</a> - 2020-05-08<a class="headerlink" href="#v030-2020-05-08" title="Permanent link">&para;</a></h2>
+<h3 id="changed_30">Changed<a class="headerlink" href="#changed_30" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Use single values for images in CRDs instead of specifying the version
   separately</li>
@@ -5787,23 +5778,23 @@ <h3 id="changed_30">Changed</h3>
 <li>Helm: Replace <code>operator.nodeSet.spec</code> and <code>operator.controllerSet.spec</code> by
   just <code>operator.nodeSet</code> and <code>operator.controllerSet</code>.</li>
 </ul>
-<h2 id="v022-2020-04-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.2.1...v0.2.2">v0.2.2</a> - 2020-04-24</h2>
-<h3 id="changed_31">Changed</h3>
+<h2 id="v022-2020-04-24"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.2.1...v0.2.2">v0.2.2</a> - 2020-04-24<a class="headerlink" href="#v022-2020-04-24" title="Permanent link">&para;</a></h2>
+<h3 id="changed_31">Changed<a class="headerlink" href="#changed_31" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Fix reporting of errors in LinstorControllerSet status</li>
 </ul>
-<h2 id="v021-2020-04-14"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.2.0...v0.2.1">v0.2.1</a> - 2020-04-14</h2>
-<h3 id="changed_32">Changed</h3>
+<h2 id="v021-2020-04-14"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.2.0...v0.2.1">v0.2.1</a> - 2020-04-14<a class="headerlink" href="#v021-2020-04-14" title="Permanent link">&para;</a></h2>
+<h3 id="changed_32">Changed<a class="headerlink" href="#changed_32" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Helm: Update LINSTOR server dependencies to fix startup problems</li>
 </ul>
-<h2 id="v020-2020-04-10"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.1.4...v0.2.0">v0.2.0</a> - 2020-04-10</h2>
-<h3 id="added_31">Added</h3>
+<h2 id="v020-2020-04-10"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.1.4...v0.2.0">v0.2.0</a> - 2020-04-10<a class="headerlink" href="#v020-2020-04-10" title="Permanent link">&para;</a></h2>
+<h3 id="added_31">Added<a class="headerlink" href="#added_31" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Helm: Allow an existing database to be used instead of always setting up
   a dedicated etcd instance</li>
 </ul>
-<h3 id="changed_33">Changed</h3>
+<h3 id="changed_33">Changed<a class="headerlink" href="#changed_33" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Rename <code>etcdURL</code> parameter of LinstorControllerSet to <code>dbConnectionURL</code> to
   reflect the fact that it can be used for any database type</li>
@@ -5811,16 +5802,16 @@ <h3 id="changed_33">Changed</h3>
 <li>Helm: Create multiple volumes with a single <code>pv-hostchart</code> installation</li>
 <li>Helm: Update dependencies</li>
 </ul>
-<h2 id="v014-2020-03-05"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.0.1...v0.1.4">v0.1.4</a> - 2020-03-05</h2>
-<h3 id="added_32">Added</h3>
+<h2 id="v014-2020-03-05"><a href="https://github.com/piraeusdatastore/piraeus-operator/compare/v0.0.1...v0.1.4">v0.1.4</a> - 2020-03-05<a class="headerlink" href="#v014-2020-03-05" title="Permanent link">&para;</a></h2>
+<h3 id="added_32">Added<a class="headerlink" href="#added_32" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Helm: Add support for <code>hostPath</code> <code>PersistentVolume</code> persistence of etcd</li>
 </ul>
-<h3 id="removed_6">Removed</h3>
+<h3 id="removed_6">Removed<a class="headerlink" href="#removed_6" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Helm: Remove vendored etcd chart from repository</li>
 </ul>
-<h3 id="changed_34">Changed</h3>
+<h3 id="changed_34">Changed<a class="headerlink" href="#changed_34" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Rename CRDs from Piraeus<em> to Linstor</em></li>
 <li>Make priority classes configurable</li>
@@ -5831,18 +5822,18 @@ <h3 id="changed_34">Changed</h3>
 <li>Helm: Update dependent image versions</li>
 <li>Docker: Change base image to Debian Buster</li>
 </ul>
-<h2 id="v013-2020-02-24">[v0.1.3] - 2020-02-24</h2>
-<h3 id="added_33">Added</h3>
+<h2 id="v013-2020-02-24">v0.1.3 - 2020-02-24<a class="headerlink" href="#v013-2020-02-24" title="Permanent link">&para;</a></h2>
+<h3 id="added_33">Added<a class="headerlink" href="#added_33" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Support for kernel module injection based on shipped modules - necessary for
   CoreOS support.</li>
 </ul>
-<h2 id="v0121-2020-02-21">[v0.1.2.1] - 2020-02-21</h2>
-<h3 id="added_34">Added</h3>
+<h2 id="v0121-2020-02-21">v0.1.2.1 - 2020-02-21<a class="headerlink" href="#v0121-2020-02-21" title="Permanent link">&para;</a></h2>
+<h3 id="added_34">Added<a class="headerlink" href="#added_34" title="Permanent link">&para;</a></h3>
 <ul>
 <li>/charts contains Helm v3 chart for this operator</li>
 </ul>
-<h3 id="changed_35">Changed</h3>
+<h3 id="changed_35">Changed<a class="headerlink" href="#changed_35" title="Permanent link">&para;</a></h3>
 <ul>
 <li>CRDs contain additional Spec parameters that allow customizing image repo and
   tag/version of the image.</li>
@@ -5852,8 +5843,8 @@ <h3 id="changed_35">Changed</h3>
   Satellite images as it was previously the case. Hence, the readiness probe
   is changed to use <code>curl</code> instead of <code>linstor</code> client command.</li>
 </ul>
-<h2 id="v010-2020-01-27">[v0.1.0] - 2020-01-27</h2>
-<h3 id="added_35">Added</h3>
+<h2 id="v010-2020-01-27">v0.1.0 - 2020-01-27<a class="headerlink" href="#v010-2020-01-27" title="Permanent link">&para;</a></h2>
+<h3 id="added_35">Added<a class="headerlink" href="#added_35" title="Permanent link">&para;</a></h3>
 <ul>
 <li>examples/operator-intra.yaml file to bundle all the rbac, crds, etc to run the
   operator</li>
@@ -5863,11 +5854,11 @@ <h3 id="added_35">Added</h3>
 <li>NodeSet service for the Satellite pods that also point to the Controller
   service for LINSTOR discovery</li>
 </ul>
-<h3 id="removed_7">Removed</h3>
+<h3 id="removed_7">Removed<a class="headerlink" href="#removed_7" title="Permanent link">&para;</a></h3>
 <ul>
 <li><code>ControllerEndpoint</code> and <code>DefaultController</code> from the PiraeusNodeSet spec</li>
 </ul>
-<h3 id="changed_36">Changed</h3>
+<h3 id="changed_36">Changed<a class="headerlink" href="#changed_36" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Controller persistence is now handled by etcd. There must be a reachable and
   operable etcd cluster for this operator to work.</li>
@@ -5882,8 +5873,8 @@ <h3 id="changed_36">Changed</h3>
 <li>API Versions on PriorityClass, DaemonSet, StatefulSet, and CRD kinds to reflect
   K8s 1.16.0 release</li>
 </ul>
-<h2 id="v001-2019-07-19"><a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v0.0.1">v0.0.1</a> - 2019-07-19</h2>
-<h3 id="added_36">Added</h3>
+<h2 id="v001-2019-07-19"><a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v0.0.1">v0.0.1</a> - 2019-07-19<a class="headerlink" href="#v001-2019-07-19" title="Permanent link">&para;</a></h2>
+<h3 id="added_36">Added<a class="headerlink" href="#added_36" title="Permanent link">&para;</a></h3>
 <ul>
 <li>Initial public version with docs</li>
 </ul>
diff --git a/v2.7.1/assets/images/social/CHANGELOG.png b/v2.7.1/assets/images/social/CHANGELOG.png
index d770165..6ae03ea 100644
Binary files a/v2.7.1/assets/images/social/CHANGELOG.png and b/v2.7.1/assets/images/social/CHANGELOG.png differ
diff --git a/v2.7.1/assets/images/social/README.png b/v2.7.1/assets/images/social/README.png
index 76ba55f..cf90311 100644
Binary files a/v2.7.1/assets/images/social/README.png and b/v2.7.1/assets/images/social/README.png differ
diff --git a/v2.7.1/assets/images/social/explanation/README.png b/v2.7.1/assets/images/social/explanation/README.png
index 4dfc354..b03a22d 100644
Binary files a/v2.7.1/assets/images/social/explanation/README.png and b/v2.7.1/assets/images/social/explanation/README.png differ
diff --git a/v2.7.1/assets/images/social/explanation/components.png b/v2.7.1/assets/images/social/explanation/components.png
index a151bde..077fccd 100644
Binary files a/v2.7.1/assets/images/social/explanation/components.png and b/v2.7.1/assets/images/social/explanation/components.png differ
diff --git a/v2.7.1/assets/images/social/how-to/README.png b/v2.7.1/assets/images/social/how-to/README.png
index 2ab3368..0719364 100644
Binary files a/v2.7.1/assets/images/social/how-to/README.png and b/v2.7.1/assets/images/social/how-to/README.png differ
diff --git a/v2.7.1/assets/images/social/how-to/api-tls.png b/v2.7.1/assets/images/social/how-to/api-tls.png
index e63e756..3cfe943 100644
Binary files a/v2.7.1/assets/images/social/how-to/api-tls.png and b/v2.7.1/assets/images/social/how-to/api-tls.png differ
diff --git a/v2.7.1/assets/images/social/how-to/drbd-host-networking.png b/v2.7.1/assets/images/social/how-to/drbd-host-networking.png
index ef0e358..11cb615 100644
Binary files a/v2.7.1/assets/images/social/how-to/drbd-host-networking.png and b/v2.7.1/assets/images/social/how-to/drbd-host-networking.png differ
diff --git a/v2.7.1/assets/images/social/how-to/drbd-loader.png b/v2.7.1/assets/images/social/how-to/drbd-loader.png
index 6906561..b145687 100644
Binary files a/v2.7.1/assets/images/social/how-to/drbd-loader.png and b/v2.7.1/assets/images/social/how-to/drbd-loader.png differ
diff --git a/v2.7.1/assets/images/social/how-to/drbd-tls.png b/v2.7.1/assets/images/social/how-to/drbd-tls.png
index 30ee80c..e73689f 100644
Binary files a/v2.7.1/assets/images/social/how-to/drbd-tls.png and b/v2.7.1/assets/images/social/how-to/drbd-tls.png differ
diff --git a/v2.7.1/assets/images/social/how-to/external-controller.png b/v2.7.1/assets/images/social/how-to/external-controller.png
index 0c432d7..4b419e8 100644
Binary files a/v2.7.1/assets/images/social/how-to/external-controller.png and b/v2.7.1/assets/images/social/how-to/external-controller.png differ
diff --git a/v2.7.1/assets/images/social/how-to/flatcar.png b/v2.7.1/assets/images/social/how-to/flatcar.png
index 7fec4b2..761bb0c 100644
Binary files a/v2.7.1/assets/images/social/how-to/flatcar.png and b/v2.7.1/assets/images/social/how-to/flatcar.png differ
diff --git a/v2.7.1/assets/images/social/how-to/http-proxy.png b/v2.7.1/assets/images/social/how-to/http-proxy.png
index cc74328..06e5b2f 100644
Binary files a/v2.7.1/assets/images/social/how-to/http-proxy.png and b/v2.7.1/assets/images/social/how-to/http-proxy.png differ
diff --git a/v2.7.1/assets/images/social/how-to/install-kernel-headers.png b/v2.7.1/assets/images/social/how-to/install-kernel-headers.png
index 421580b..5e3a837 100644
Binary files a/v2.7.1/assets/images/social/how-to/install-kernel-headers.png and b/v2.7.1/assets/images/social/how-to/install-kernel-headers.png differ
diff --git a/v2.7.1/assets/images/social/how-to/internal-tls.png b/v2.7.1/assets/images/social/how-to/internal-tls.png
index b2838df..1b27290 100644
Binary files a/v2.7.1/assets/images/social/how-to/internal-tls.png and b/v2.7.1/assets/images/social/how-to/internal-tls.png differ
diff --git a/v2.7.1/assets/images/social/how-to/k0s.png b/v2.7.1/assets/images/social/how-to/k0s.png
index a4b317f..ed274fd 100644
Binary files a/v2.7.1/assets/images/social/how-to/k0s.png and b/v2.7.1/assets/images/social/how-to/k0s.png differ
diff --git a/v2.7.1/assets/images/social/how-to/linstor-affinity-controller.png b/v2.7.1/assets/images/social/how-to/linstor-affinity-controller.png
index 88adddb..37f11ad 100644
Binary files a/v2.7.1/assets/images/social/how-to/linstor-affinity-controller.png and b/v2.7.1/assets/images/social/how-to/linstor-affinity-controller.png differ
diff --git a/v2.7.1/assets/images/social/how-to/microk8s.png b/v2.7.1/assets/images/social/how-to/microk8s.png
index c4170f9..bde1a02 100644
Binary files a/v2.7.1/assets/images/social/how-to/microk8s.png and b/v2.7.1/assets/images/social/how-to/microk8s.png differ
diff --git a/v2.7.1/assets/images/social/how-to/monitoring.png b/v2.7.1/assets/images/social/how-to/monitoring.png
index e874325..30e8378 100644
Binary files a/v2.7.1/assets/images/social/how-to/monitoring.png and b/v2.7.1/assets/images/social/how-to/monitoring.png differ
diff --git a/v2.7.1/assets/images/social/how-to/network-policy.png b/v2.7.1/assets/images/social/how-to/network-policy.png
index 77fc7f2..b6c920b 100644
Binary files a/v2.7.1/assets/images/social/how-to/network-policy.png and b/v2.7.1/assets/images/social/how-to/network-policy.png differ
diff --git a/v2.7.1/assets/images/social/how-to/openshift.png b/v2.7.1/assets/images/social/how-to/openshift.png
index 61eb8ed..8dfa254 100644
Binary files a/v2.7.1/assets/images/social/how-to/openshift.png and b/v2.7.1/assets/images/social/how-to/openshift.png differ
diff --git a/v2.7.1/assets/images/social/how-to/restore-linstor-db.png b/v2.7.1/assets/images/social/how-to/restore-linstor-db.png
index e9f36c0..f71ac4f 100644
Binary files a/v2.7.1/assets/images/social/how-to/restore-linstor-db.png and b/v2.7.1/assets/images/social/how-to/restore-linstor-db.png differ
diff --git a/v2.7.1/assets/images/social/how-to/secure-boot.png b/v2.7.1/assets/images/social/how-to/secure-boot.png
index df80af0..acf736a 100644
Binary files a/v2.7.1/assets/images/social/how-to/secure-boot.png and b/v2.7.1/assets/images/social/how-to/secure-boot.png differ
diff --git a/v2.7.1/assets/images/social/how-to/talos.png b/v2.7.1/assets/images/social/how-to/talos.png
index b04a96c..6c0f236 100644
Binary files a/v2.7.1/assets/images/social/how-to/talos.png and b/v2.7.1/assets/images/social/how-to/talos.png differ
diff --git a/v2.7.1/assets/images/social/how-to/upgrade/2-collect-information.png b/v2.7.1/assets/images/social/how-to/upgrade/2-collect-information.png
deleted file mode 100644
index 07e20cf..0000000
Binary files a/v2.7.1/assets/images/social/how-to/upgrade/2-collect-information.png and /dev/null differ
diff --git a/v2.7.1/assets/images/social/how-to/upgrade/3-remove-operator-v1.png b/v2.7.1/assets/images/social/how-to/upgrade/3-remove-operator-v1.png
deleted file mode 100644
index 14a4a31..0000000
Binary files a/v2.7.1/assets/images/social/how-to/upgrade/3-remove-operator-v1.png and /dev/null differ
diff --git a/v2.7.1/assets/images/social/how-to/upgrade/4-install-operator-v2.png b/v2.7.1/assets/images/social/how-to/upgrade/4-install-operator-v2.png
deleted file mode 100644
index ecc28cf..0000000
Binary files a/v2.7.1/assets/images/social/how-to/upgrade/4-install-operator-v2.png and /dev/null differ
diff --git a/v2.7.1/assets/images/social/how-to/upgrade/UPGRADE.png b/v2.7.1/assets/images/social/how-to/upgrade/UPGRADE.png
deleted file mode 100644
index 1eee40c..0000000
Binary files a/v2.7.1/assets/images/social/how-to/upgrade/UPGRADE.png and /dev/null differ
diff --git a/v2.7.1/assets/images/social/how-to/upgrade/index.png b/v2.7.1/assets/images/social/how-to/upgrade/index.png
deleted file mode 100644
index a73ac9e..0000000
Binary files a/v2.7.1/assets/images/social/how-to/upgrade/index.png and /dev/null differ
diff --git a/v2.7.1/assets/images/social/reference/README.png b/v2.7.1/assets/images/social/reference/README.png
index 452d775..9a250e3 100644
Binary files a/v2.7.1/assets/images/social/reference/README.png and b/v2.7.1/assets/images/social/reference/README.png differ
diff --git a/v2.7.1/assets/images/social/reference/linstorcluster.png b/v2.7.1/assets/images/social/reference/linstorcluster.png
index 035d296..823a7f7 100644
Binary files a/v2.7.1/assets/images/social/reference/linstorcluster.png and b/v2.7.1/assets/images/social/reference/linstorcluster.png differ
diff --git a/v2.7.1/assets/images/social/reference/linstornodeconnection.png b/v2.7.1/assets/images/social/reference/linstornodeconnection.png
index 0b507a2..c60d302 100644
Binary files a/v2.7.1/assets/images/social/reference/linstornodeconnection.png and b/v2.7.1/assets/images/social/reference/linstornodeconnection.png differ
diff --git a/v2.7.1/assets/images/social/reference/linstorsatellite.png b/v2.7.1/assets/images/social/reference/linstorsatellite.png
index 5f2f58f..bfb5264 100644
Binary files a/v2.7.1/assets/images/social/reference/linstorsatellite.png and b/v2.7.1/assets/images/social/reference/linstorsatellite.png differ
diff --git a/v2.7.1/assets/images/social/reference/linstorsatelliteconfiguration.png b/v2.7.1/assets/images/social/reference/linstorsatelliteconfiguration.png
index 5d7709c..67fba60 100644
Binary files a/v2.7.1/assets/images/social/reference/linstorsatelliteconfiguration.png and b/v2.7.1/assets/images/social/reference/linstorsatelliteconfiguration.png differ
diff --git a/v2.7.1/assets/images/social/tutorial/README.png b/v2.7.1/assets/images/social/tutorial/README.png
index 7d1ad18..1423c78 100644
Binary files a/v2.7.1/assets/images/social/tutorial/README.png and b/v2.7.1/assets/images/social/tutorial/README.png differ
diff --git a/v2.7.1/assets/images/social/tutorial/get-started.png b/v2.7.1/assets/images/social/tutorial/get-started.png
index 725de38..5f2f72b 100644
Binary files a/v2.7.1/assets/images/social/tutorial/get-started.png and b/v2.7.1/assets/images/social/tutorial/get-started.png differ
diff --git a/v2.7.1/assets/images/social/tutorial/replicated-volumes.png b/v2.7.1/assets/images/social/tutorial/replicated-volumes.png
index 6305214..cfc5932 100644
Binary files a/v2.7.1/assets/images/social/tutorial/replicated-volumes.png and b/v2.7.1/assets/images/social/tutorial/replicated-volumes.png differ
diff --git a/v2.7.1/assets/images/social/tutorial/snapshots.png b/v2.7.1/assets/images/social/tutorial/snapshots.png
index 92efb81..e9f411a 100644
Binary files a/v2.7.1/assets/images/social/tutorial/snapshots.png and b/v2.7.1/assets/images/social/tutorial/snapshots.png differ
diff --git a/v2.7.1/assets/images/social/upgrade/README.png b/v2.7.1/assets/images/social/upgrade/README.png
new file mode 100644
index 0000000..569af4b
Binary files /dev/null and b/v2.7.1/assets/images/social/upgrade/README.png differ
diff --git a/v2.7.1/assets/images/social/how-to/upgrade/1-migrate-database.png b/v2.7.1/assets/images/social/upgrade/migration/1-migrate-database.png
similarity index 69%
rename from v2.7.1/assets/images/social/how-to/upgrade/1-migrate-database.png
rename to v2.7.1/assets/images/social/upgrade/migration/1-migrate-database.png
index f6ffdbc..c0bf00e 100644
Binary files a/v2.7.1/assets/images/social/how-to/upgrade/1-migrate-database.png and b/v2.7.1/assets/images/social/upgrade/migration/1-migrate-database.png differ
diff --git a/v2.7.1/assets/images/social/upgrade/migration/2-collect-information.png b/v2.7.1/assets/images/social/upgrade/migration/2-collect-information.png
new file mode 100644
index 0000000..a71f2d1
Binary files /dev/null and b/v2.7.1/assets/images/social/upgrade/migration/2-collect-information.png differ
diff --git a/v2.7.1/assets/images/social/upgrade/migration/3-remove-operator-v1.png b/v2.7.1/assets/images/social/upgrade/migration/3-remove-operator-v1.png
new file mode 100644
index 0000000..975688e
Binary files /dev/null and b/v2.7.1/assets/images/social/upgrade/migration/3-remove-operator-v1.png differ
diff --git a/v2.7.1/assets/images/social/upgrade/migration/4-install-operator-v2.png b/v2.7.1/assets/images/social/upgrade/migration/4-install-operator-v2.png
new file mode 100644
index 0000000..0eb2b3e
Binary files /dev/null and b/v2.7.1/assets/images/social/upgrade/migration/4-install-operator-v2.png differ
diff --git a/v2.7.1/assets/images/social/upgrade/migration/README.png b/v2.7.1/assets/images/social/upgrade/migration/README.png
new file mode 100644
index 0000000..3c1bd69
Binary files /dev/null and b/v2.7.1/assets/images/social/upgrade/migration/README.png differ
diff --git a/v2.7.1/explanation/components/index.html b/v2.7.1/explanation/components/index.html
index d117ad9..5a7cc02 100644
--- a/v2.7.1/explanation/components/index.html
+++ b/v2.7.1/explanation/components/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Piraeus Components - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/explanation/components.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Piraeus Components - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/explanation/components.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1346,8 +1346,6 @@
       
         
       
-        
-      
     
     
       
@@ -1365,7 +1363,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1395,31 +1393,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1441,35 +1422,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1490,7 +1481,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1511,7 +1502,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1532,7 +1523,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1873,7 +1864,7 @@
   
 
 
-<h1 id="understanding-piraeus-datastore-components">Understanding Piraeus Datastore Components</h1>
+<h1 id="understanding-piraeus-datastore-components">Understanding Piraeus Datastore Components<a class="headerlink" href="#understanding-piraeus-datastore-components" title="Permanent link">&para;</a></h1>
 <p>Piraeus Datastore consists of several different components. Each component runs as a separate Deployment, DaemonSet or
 plain Pod.</p>
 <p>All Pods are labelled according to their component. You can check the Pods running in your own cluster by
@@ -1888,7 +1879,7 @@ <h1 id="understanding-piraeus-datastore-components">Understanding Piraeus Datast
 piraeus-operator-controller-manager-6dcfcb4568-6jntp   piraeus-operator
 piraeus-operator-gencert-59449cb449-nzg6z              piraeus-operator-gencert
 </code></pre></div>
-<h1 id="piraeus-operator"><code>piraeus-operator</code></h1>
+<h1 id="piraeus-operator"><code>piraeus-operator</code><a class="headerlink" href="#piraeus-operator" title="Permanent link">&para;</a></h1>
 <p>The Piraeus Operator creates and maintains the other components, except for the <code>piraeus-operator-gencert</code> component.</p>
 <p>Along with deploying the needed Kubernetes resources, it maintains the LINSTOR® Cluster state by:</p>
 <ul>
@@ -1896,21 +1887,21 @@ <h1 id="piraeus-operator"><code>piraeus-operator</code></h1>
 <li>Creating storage pools</li>
 <li>Maintaining node labels</li>
 </ul>
-<h1 id="piraeus-operator-gencert"><code>piraeus-operator-gencert</code></h1>
+<h1 id="piraeus-operator-gencert"><code>piraeus-operator-gencert</code><a class="headerlink" href="#piraeus-operator-gencert" title="Permanent link">&para;</a></h1>
 <p>The "generate certificate" Pod creates and maintains the TLS key and certificate used by the Piraeus Operator.
 The TLS secret, named <code>webhook-server-cert</code>, is needed to start the Piraeus Operator Pod. In addition, this Pod
 keeps the <code>ValidatingWebhookConfiguration</code> for the Piraeus Operator up-to-date.</p>
 <p>The Piraeus Operator needs a TLS certificate to serve the validation endpoint for the custom resources it maintains.</p>
 <p>Historically, TLS certificates where created by <code>cert-manager</code>. This was removed to reduce the number of dependencies
 for deploying Piraeus Datastore.</p>
-<h1 id="linstor-controller"><code>linstor-controller</code></h1>
+<h1 id="linstor-controller"><code>linstor-controller</code><a class="headerlink" href="#linstor-controller" title="Permanent link">&para;</a></h1>
 <p>The LINSTOR Controller is responsible for resource placement, resource configuration, and orchestration of any
 operational processes that require a view of the whole cluster. It maintains a database of all the configuration
 information for the whole cluster, stored as Kubernetes objects.</p>
 <p>The LINSTOR Controller connects to the LINSTOR Satellites and sends them instructions for achieving the desired cluster
 state.</p>
 <p>It provides an external API used by LINSTOR CSI and Piraeus Operator to change the cluster state.</p>
-<h1 id="linstor-satellite"><code>linstor-satellite</code></h1>
+<h1 id="linstor-satellite"><code>linstor-satellite</code><a class="headerlink" href="#linstor-satellite" title="Permanent link">&para;</a></h1>
 <p>The LINSTOR Satellite service runs on each node. It acts as the local configuration agent for LINSTOR managed storage.
 It is stateless and receives all the information it needs from the LINSTOR Controller.</p>
 <p>Satellites are started as DaemonSets, managed by the Piraeus Operator. We deploy one DaemonSet per node, this enables
@@ -1927,15 +1918,15 @@ <h1 id="linstor-satellite"><code>linstor-satellite</code></h1>
 </ul>
 <p>The use of separate UTS namespace should be completely transparent to users: running <code>kubectl exec ...</code> on a satellite
   Pod will drop you into this namespace, enabling you to run <code>drbdadm</code> commands as expected.</p>
-<h1 id="linstor-csi-controller"><code>linstor-csi-controller</code></h1>
+<h1 id="linstor-csi-controller"><code>linstor-csi-controller</code><a class="headerlink" href="#linstor-csi-controller" title="Permanent link">&para;</a></h1>
 <p>The LINSTOR CSI Controller Pod creates, modifies and deletes volumes and snapshots. It translates the state of Kubernetes
 resources (<code>StorageClass</code>, <code>PersistentVolumeClaims</code>, <code>VolumeSnapshots</code>) into their equivalent in LINSTOR.</p>
-<h1 id="linstor-csi-node"><code>linstor-csi-node</code></h1>
+<h1 id="linstor-csi-node"><code>linstor-csi-node</code><a class="headerlink" href="#linstor-csi-node" title="Permanent link">&para;</a></h1>
 <p>The LINSTOR CSI Node Pods execute mount and unmount operations. Mount and Unmount are initiated by kubelet before
 starting a Pod with a Piraeus volume.</p>
 <p>They are deployed as a DaemonSet on every node in the cluster by default. There needs to be a LINSTOR Satellite running
 on the same node as a CSI Node Pod.</p>
-<h1 id="ha-controller"><code>ha-controller</code></h1>
+<h1 id="ha-controller"><code>ha-controller</code><a class="headerlink" href="#ha-controller" title="Permanent link">&para;</a></h1>
 <p>The Piraeus High Availability Controller will speed up the fail-over process for stateful workloads using Piraeus for
 storage.</p>
 <p>It is deployed on every node in the cluster and listens for DRBD® events to detect storage failures on other nodes. It
diff --git a/v2.7.1/explanation/index.html b/v2.7.1/explanation/index.html
index 18f81da..bc11b68 100644
--- a/v2.7.1/explanation/index.html
+++ b/v2.7.1/explanation/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -15,7 +15,7 @@
         <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/explanation/">
       
       
-        <link rel="prev" href="../how-to/upgrade/4-install-operator-v2/">
+        <link rel="prev" href="../upgrade/migration/4-install-operator-v2/">
       
       
         <link rel="next" href="components/">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Understanding Piraeus - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/explanation/README.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Understanding Piraeus - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/explanation/README.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../how-to/upgrade/" class="md-tabs__link">
+        <a href="../upgrade/" class="md-tabs__link">
           
   
     
@@ -1346,8 +1346,6 @@
       
         
       
-        
-      
     
     
       
@@ -1365,7 +1363,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../how-to/upgrade/" class="md-nav__link ">
+            <a href="../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1395,31 +1393,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1441,35 +1422,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1490,7 +1481,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1511,7 +1502,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1532,7 +1523,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1880,9 +1871,9 @@
   
 
 
-<h1 id="understanding-piraeus-datastore">Understanding Piraeus Datastore</h1>
+<h1 id="understanding-piraeus-datastore">Understanding Piraeus Datastore<a class="headerlink" href="#understanding-piraeus-datastore" title="Permanent link">&para;</a></h1>
 <p>The following documents explain how Piraeus Datastore works, and why it works the way it does.</p>
-<h3 id="understanding-piraeus-datastore-components"><a href="components/">Understanding Piraeus Datastore Components</a></h3>
+<h3 id="understanding-piraeus-datastore-components"><a href="components/">Understanding Piraeus Datastore Components</a><a class="headerlink" href="#understanding-piraeus-datastore-components" title="Permanent link">&para;</a></h3>
 <p>A short introduction for every component of Piraeus Datastore.</p>
 
 
@@ -1922,7 +1913,7 @@ <h3 id="understanding-piraeus-datastore-components"><a href="components/">Unders
       <nav class="md-footer__inner md-grid" aria-label="Footer" >
         
           
-          <a href="../how-to/upgrade/4-install-operator-v2/" class="md-footer__link md-footer__link--prev" aria-label="Previous: Install Operator v2">
+          <a href="../upgrade/migration/4-install-operator-v2/" class="md-footer__link md-footer__link--prev" aria-label="Previous: Install Operator v2">
             <div class="md-footer__button md-icon">
               
               <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg>
diff --git a/v2.7.1/how-to/api-tls/index.html b/v2.7.1/how-to/api-tls/index.html
index fc10336..15d2ffe 100644
--- a/v2.7.1/how-to/api-tls/index.html
+++ b/v2.7.1/how-to/api-tls/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Configure TLS for the LINSTOR API - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/api-tls.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Configure TLS for the LINSTOR API - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/api-tls.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1435,8 +1435,6 @@
       
         
       
-        
-      
     
     
       
@@ -1454,7 +1452,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1484,31 +1482,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1530,35 +1511,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1579,7 +1570,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1600,7 +1591,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1621,7 +1612,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1982,7 +1973,7 @@
   
 
 
-<h1 id="how-to-configure-tls-for-the-linstor-api">How to Configure TLS for the LINSTOR API</h1>
+<h1 id="how-to-configure-tls-for-the-linstor-api">How to Configure TLS for the LINSTOR API<a class="headerlink" href="#how-to-configure-tls-for-the-linstor-api" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to set up TLS for the LINSTOR® API. The API, served by the LINSTOR Controller, is used by
 clients such as the CSI Driver and the Operator itself to control the LINSTOR Cluster.</p>
 <p>To complete this guide, you should be familiar with:</p>
@@ -1990,7 +1981,7 @@ <h1 id="how-to-configure-tls-for-the-linstor-api">How to Configure TLS for the L
 <li>editing <code>LinstorCluster</code> resources.</li>
 <li>using either <a href="https://cert-manager.io">cert-manager</a> or <code>openssl</code> to create TLS certificates.</li>
 </ul>
-<h2 id="provision-keys-and-certificates-using-cert-manager">Provision Keys and Certificates Using cert-manager</h2>
+<h2 id="provision-keys-and-certificates-using-cert-manager">Provision Keys and Certificates Using cert-manager<a class="headerlink" href="#provision-keys-and-certificates-using-cert-manager" title="Permanent link">&para;</a></h2>
 <p>This method requires a working <a href="https://cert-manager.io">cert-manager</a> deployment in your cluster. For an alternative
 way to provision keys and certificates, see the <a href="#provision-keys-and-certificates-using-openssl"><code>openssl</code> section</a>
 below.</p>
@@ -2044,7 +2035,7 @@ <h2 id="provision-keys-and-certificates-using-cert-manager">Provision Keys and C
 <span class="w">      </span><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Issuer</span>
 </code></pre></div>
 <p>This completes the necessary steps for secure the LINSTOR API with TLS using cert-manager. Skip to the <a href="#verifying-tls-configuration">last section</a> to verify TLS is working.</p>
-<h2 id="provision-keys-and-certificates-using-openssl">Provision Keys and Certificates Using <code>openssl</code></h2>
+<h2 id="provision-keys-and-certificates-using-openssl">Provision Keys and Certificates Using <code>openssl</code><a class="headerlink" href="#provision-keys-and-certificates-using-openssl" title="Permanent link">&para;</a></h2>
 <p>If you completed the <a href="#provision-keys-and-certificates-using-cert-manager">cert-manager section</a> above, skip directly
 to the <a href="#verifying-tls-configuration">verifying the configuration</a> below.</p>
 <p>This method requires the <code>openssl</code> program on the command line. For an alternative way to provision keys and
@@ -2090,7 +2081,7 @@ <h2 id="provision-keys-and-certificates-using-openssl">Provision Keys and Certif
 <span class="w">    </span><span class="nt">csiControllerSecretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">linstor-client-tls</span>
 <span class="w">    </span><span class="nt">csiNodeSecretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">linstor-client-tls</span>
 </code></pre></div>
-<h2 id="verifying-tls-configuration">Verifying TLS Configuration</h2>
+<h2 id="verifying-tls-configuration">Verifying TLS Configuration<a class="headerlink" href="#verifying-tls-configuration" title="Permanent link">&para;</a></h2>
 <p>You can verify that the secure API is running by manually connecting to the HTTPS endpoint using <code>curl</code></p>
 <div class="highlight"><pre><span></span><code>$ kubectl exec -n piraeus-datastore deploy/linstor-controller -- curl --key /etc/linstor/client/tls.key --cert /etc/linstor/client/tls.crt --cacert /etc/linstor/client/ca.crt https://linstor-controller.piraeus-datastore.svc:3371/v1/controller/version
 {&quot;version&quot;:&quot;1.20.2&quot;,&quot;git_hash&quot;:&quot;58a983a5c2f49eb8d22c89b277272e6c4299457a&quot;,&quot;build_time&quot;:&quot;2022-12-14T14:21:28+00:00&quot;,&quot;rest_api_version&quot;:&quot;1.16.0&quot;}%
diff --git a/v2.7.1/how-to/drbd-host-networking/index.html b/v2.7.1/how-to/drbd-host-networking/index.html
index 7a41ffb..3adf81e 100644
--- a/v2.7.1/how-to/drbd-host-networking/index.html
+++ b/v2.7.1/how-to/drbd-host-networking/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Use the Host Network for DRBD Replication - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/drbd-host-networking.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Use the Host Network for DRBD Replication - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/drbd-host-networking.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1450,8 +1450,6 @@
       
         
       
-        
-      
     
     
       
@@ -1469,7 +1467,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1499,31 +1497,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1545,35 +1526,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1594,7 +1585,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1615,7 +1606,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1636,7 +1627,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -2012,7 +2003,7 @@
   
 
 
-<h1 id="how-to-use-the-host-network-for-drbd-replication">How to Use the Host Network for DRBD Replication</h1>
+<h1 id="how-to-use-the-host-network-for-drbd-replication">How to Use the Host Network for DRBD Replication<a class="headerlink" href="#how-to-use-the-host-network-for-drbd-replication" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to use the host network for DRBD® replication.</p>
 <p>By default, DRBD will use the container network to replicate volume data. This ensures replication works on a wide
 range of clusters without further configuration. It also enables use of <code>NetworkPolicy</code> to block unauthorized access
@@ -2022,7 +2013,7 @@ <h1 id="how-to-use-the-host-network-for-drbd-replication">How to Use the Host Ne
 Satellite Pod. The host network might also offer better performance than the container network. As a downside, you
 will have to manually ensure connectivity between Nodes on the relevant ports.</p>
 <p>To follow the steps in this guide, you should be familiar with editing <code>LinstorSatelliteConfiguration</code> resources.</p>
-<h2 id="switch-from-container-network-to-host-network">Switch from Container Network to Host Network</h2>
+<h2 id="switch-from-container-network-to-host-network">Switch from Container Network to Host Network<a class="headerlink" href="#switch-from-container-network-to-host-network" title="Permanent link">&para;</a></h2>
 <p>Switching from the default container network to host network is possible at any time. Existing DRBD resources will be
 reconfigured to use the host network interface.</p>
 <p>To configure the host network for the LINSTOR Satellite, apply the following configuration:</p>
@@ -2037,10 +2028,10 @@ <h2 id="switch-from-container-network-to-host-network">Switch from Container Net
 </code></pre></div>
 <p>After the Satellite Pods are recreated, they will use the host network. Any existing DRBD resources are reconfigured
 to use the new IP Address instead.</p>
-<h2 id="switch-from-host-network-to-container-network">Switch from Host Network to Container Network</h2>
+<h2 id="switch-from-host-network-to-container-network">Switch from Host Network to Container Network<a class="headerlink" href="#switch-from-host-network-to-container-network" title="Permanent link">&para;</a></h2>
 <p>Switching back from host network to container network involves manually resetting the configured peer addresses used by
 DRBD. This can either be achieved by rebooting every node, or by manually resetting the address using <code>drbdadm</code>.</p>
-<h3 id="switch-from-host-network-to-container-network-using-reboots">Switch from Host Network to Container Network Using Reboots</h3>
+<h3 id="switch-from-host-network-to-container-network-using-reboots">Switch from Host Network to Container Network Using Reboots<a class="headerlink" href="#switch-from-host-network-to-container-network-using-reboots" title="Permanent link">&para;</a></h3>
 <p>First, you need to remove the <code>LinstorSatelliteConfiguration</code> that set <code>hostNetwork: true</code>:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl delete linstorsatelliteconfigurations.piraeus.io host-network
 linstorsatelliteconfiguration.piraeus.io &quot;host-network&quot; deleted
@@ -2050,7 +2041,7 @@ <h3 id="switch-from-host-network-to-container-network-using-reboots">Switch from
 are generally not reachable from the container network.</p>
 <p>After all nodes are rebooted, all resources are configured to use the container network, and all DRBD connections
 should be connected again.</p>
-<h3 id="switch-from-host-network-to-container-network-using-drbdadm">Switch from Host Network to Container Network Using <code>drbdadm</code></h3>
+<h3 id="switch-from-host-network-to-container-network-using-drbdadm">Switch from Host Network to Container Network Using <code>drbdadm</code><a class="headerlink" href="#switch-from-host-network-to-container-network-using-drbdadm" title="Permanent link">&para;</a></h3>
 <p>During this procedure, ensure no new volumes or snapshots are created: otherwise the migration to the
 container network might not be applied to all resources.</p>
 <p>First, you need to temporarily stop all replication and suspend all DRBD volumes using <code>drbdadm suspend-io all</code>.
diff --git a/v2.7.1/how-to/drbd-loader/index.html b/v2.7.1/how-to/drbd-loader/index.html
index d27695f..0356a30 100644
--- a/v2.7.1/how-to/drbd-loader/index.html
+++ b/v2.7.1/how-to/drbd-loader/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Configure the DRBD Module Loader - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/drbd-loader.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Configure the DRBD Module Loader - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/drbd-loader.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1435,8 +1435,6 @@
       
         
       
-        
-      
     
     
       
@@ -1454,7 +1452,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1484,31 +1482,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1530,35 +1511,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1579,7 +1570,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1600,7 +1591,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1621,7 +1612,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1982,7 +1973,7 @@
   
 
 
-<h1 id="how-to-configure-the-drbd-module-loader">How to Configure the DRBD Module Loader</h1>
+<h1 id="how-to-configure-the-drbd-module-loader">How to Configure the DRBD Module Loader<a class="headerlink" href="#how-to-configure-the-drbd-module-loader" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to configure various aspects of the DRBD® Module Loader.</p>
 <p>To follow the steps in this guide, you should be familiar with editing <code>LinstorSatelliteConfiguration</code> resources.</p>
 <p>DRBD Module Loader is the component responsible for making the DRBD kernel module available, as well as loading other
@@ -2030,7 +2021,7 @@ <h1 id="how-to-configure-the-drbd-module-loader">How to Configure the DRBD Modul
 </tr>
 </tbody>
 </table>
-<h2 id="disable-the-drbd-module-loader">Disable the DRBD Module Loader</h2>
+<h2 id="disable-the-drbd-module-loader">Disable the DRBD Module Loader<a class="headerlink" href="#disable-the-drbd-module-loader" title="Permanent link">&para;</a></h2>
 <p>In some circumstances it might be necessary to disable the DRBD Module Loader entirely. For example, you are using an
 immutable operating system, and DRBD and other modules are loaded as part of the host configuration.</p>
 <p>To disable the DRBD Module Loader completely, use the following configuration:</p>
@@ -2045,7 +2036,7 @@ <h2 id="disable-the-drbd-module-loader">Disable the DRBD Module Loader</h2>
 <span class="w">        </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">drbd-module-loader</span>
 <span class="w">          </span><span class="nt">$patch</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">delete</span>
 </code></pre></div>
-<h2 id="select-a-different-drbd-loader-version">Select a Different DRBD Loader Version</h2>
+<h2 id="select-a-different-drbd-loader-version">Select a Different DRBD Loader Version<a class="headerlink" href="#select-a-different-drbd-loader-version" title="Permanent link">&para;</a></h2>
 <p>By default, the Operator will try to find a DRBD Module Loader matching the host operating system. The host distribution
 is determined by inspecting the <code>.status.nodeInfo.osImage</code> field of the Kubernetes Node resource. A user-defined image
 can be used if the automatic mapping does not succeed or if you have different module loading requirements.</p>
@@ -2083,6 +2074,10 @@ <h2 id="select-a-different-drbd-loader-version">Select a Different DRBD Loader V
 <td>RedHat Enterprise Linux 7 rebuilds</td>
 </tr>
 <tr>
+<td><code>quay.io/piraeusdatastore/drbd9-noble</code></td>
+<td>Ubuntu 24.04</td>
+</tr>
+<tr>
 <td><code>quay.io/piraeusdatastore/drbd9-jammy</code></td>
 <td>Ubuntu 22.04</td>
 </tr>
@@ -2110,7 +2105,7 @@ <h2 id="select-a-different-drbd-loader-version">Select a Different DRBD Loader V
 </table>
 <p>You can create a loader image for your own distribution using the <a href="https://github.com/piraeusdatastore/piraeus/tree/master/dockerfiles/drbd-driver-loader">Piraeus sources</a>
 as reference.</p>
-<h2 id="change-the-way-drbd-module-loader-loads-the-drbd-module">Change the Way DRBD Module Loader Loads the DRBD Module</h2>
+<h2 id="change-the-way-drbd-module-loader-loads-the-drbd-module">Change the Way DRBD Module Loader Loads the DRBD Module<a class="headerlink" href="#change-the-way-drbd-module-loader-loads-the-drbd-module" title="Permanent link">&para;</a></h2>
 <p>By default, DRBD Module Loader will try to build the kernel module from source. The loader can also be configured to load the
 module from a Debian or RPM package included in the image, or skip loading DRBD entirely.</p>
 <p>To change the behaviour of the DRBD Loader, set the <code>LB_HOW</code> environment variable:</p>
diff --git a/v2.7.1/how-to/drbd-tls/index.html b/v2.7.1/how-to/drbd-tls/index.html
index e3cd213..1c184e7 100644
--- a/v2.7.1/how-to/drbd-tls/index.html
+++ b/v2.7.1/how-to/drbd-tls/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Configure TLS for DRBD Replication - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/drbd-tls.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Configure TLS for DRBD Replication - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/drbd-tls.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1453,8 +1453,6 @@
       
         
       
-        
-      
     
     
       
@@ -1472,7 +1470,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1502,31 +1500,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1548,35 +1529,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1597,7 +1588,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1618,7 +1609,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1639,7 +1630,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -2018,7 +2009,7 @@
   
 
 
-<h1 id="how-to-use-transport-layer-security-for-drbd-replication">How to Use Transport Layer Security for DRBD Replication</h1>
+<h1 id="how-to-use-transport-layer-security-for-drbd-replication">How to Use Transport Layer Security for DRBD Replication<a class="headerlink" href="#how-to-use-transport-layer-security-for-drbd-replication" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to use Transport Layer Security (TLS) for DRBD® replication.</p>
 <p>TLS is a protocol designed to provide security, including privacy, integrity and authentication for network
 communications. Starting with DRBD 9.2.6, replication traffic in DRBD can be encrypted using TLS, using the Linux
@@ -2028,7 +2019,7 @@ <h1 id="how-to-use-transport-layer-security-for-drbd-replication">How to Use Tra
 <li>editing <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code> resources.</li>
 <li>configuring <a href="../internal-tls/">TLS certificates for internal traffic</a>.</li>
 </ul>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li>Install Piraeus Operator &gt;= 2.3.0. The following command shows the deployed version, in this case v2.3.0:
   <div class="highlight"><pre><span></span><code>$ kubectl get pods -l app.kubernetes.io/component=piraeus-operator -ojsonpath=&#39;{.items[*].spec.containers[?(@.name==&quot;manager&quot;)].image}{&quot;\n&quot;}&#39;
@@ -2045,7 +2036,7 @@ <h2 id="prerequisites">Prerequisites</h2>
 done
 </code></pre></div></li>
 </ul>
-<h2 id="configure-tls-between-linstor-controller-and-linstor-satellite">Configure TLS Between LINSTOR Controller and LINSTOR Satellite</h2>
+<h2 id="configure-tls-between-linstor-controller-and-linstor-satellite">Configure TLS Between LINSTOR Controller and LINSTOR Satellite<a class="headerlink" href="#configure-tls-between-linstor-controller-and-linstor-satellite" title="Permanent link">&para;</a></h2>
 <p>This step is covered in <a href="../internal-tls/">a dedicated guide</a>. Follow the steps in the guide, but set the
 <code>tlsHandshakeDaemon</code> field in the <code>LinstorSatelliteConfiguration</code> resource:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
@@ -2063,7 +2054,7 @@ <h2 id="configure-tls-between-linstor-controller-and-linstor-satellite">Configur
 tlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06
 tlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06
 </code></pre></div>
-<h2 id="configure-tls-for-drbd">Configure TLS for DRBD</h2>
+<h2 id="configure-tls-for-drbd">Configure TLS for DRBD<a class="headerlink" href="#configure-tls-for-drbd" title="Permanent link">&para;</a></h2>
 <p>To instruct LINSTOR® to configure TLS for DRBD, the <code>DrbdOptions/Net/tls</code> property needs to be set to <code>yes</code>. This
 can be done directly on the <code>LinstorCluster</code> resource, so it automatically applies to all resources, or as part of
 the parameters in a StorageClass.</p>
@@ -2087,7 +2078,7 @@ <h2 id="configure-tls-for-drbd">Configure TLS for DRBD</h2>
 <span class="w">  </span><span class="nt">property.linstor.csi.linbit.com/DrbdOptions/Net/tls</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;yes&quot;</span>
 <span class="w">  </span><span class="c1"># ...</span>
 </code></pre></div>
-<h2 id="switch-existing-resources-to-tls">Switch Existing Resources to TLS</h2>
+<h2 id="switch-existing-resources-to-tls">Switch Existing Resources to TLS<a class="headerlink" href="#switch-existing-resources-to-tls" title="Permanent link">&para;</a></h2>
 <p>DRBD does not support online reconfiguration to use DRBD. To switch existing resources to use TLS, for example by
 setting the property on the <code>LinstorCluster</code> resource, you need to perform the following steps on all nodes:</p>
 <p>First, you need to temporarily stop all replication and suspend all DRBD volumes using <code>drbdadm suspend-io all</code>.
@@ -2106,7 +2097,7 @@ <h2 id="switch-existing-resources-to-tls">Switch Existing Resources to TLS</h2>
 $ kubectl exec node2.example.com -- drbdadm adjust all
 $ kubectl exec node3.example.com -- drbdadm adjust all
 </code></pre></div>
-<h2 id="confirm-drbd-uses-tls">Confirm DRBD Uses TLS</h2>
+<h2 id="confirm-drbd-uses-tls">Confirm DRBD Uses TLS<a class="headerlink" href="#confirm-drbd-uses-tls" title="Permanent link">&para;</a></h2>
 <p>To confirm that DRBD is using TLS for replication, check the following resources.</p>
 <p>First, confirm that the <code>ktls-utils</code> container performed the expected handshakes:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl logs -l app.kubernetes.io/component=linstor-satellite -c ktls-utils
diff --git a/v2.7.1/how-to/external-controller/index.html b/v2.7.1/how-to/external-controller/index.html
index 98c1179..3a4722b 100644
--- a/v2.7.1/how-to/external-controller/index.html
+++ b/v2.7.1/how-to/external-controller/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Use Piraeus Datastore with an Existing LINSTOR Cluster - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/external-controller.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Use Piraeus Datastore with an Existing LINSTOR Cluster - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/external-controller.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1435,8 +1435,6 @@
       
         
       
-        
-      
     
     
       
@@ -1454,7 +1452,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1484,31 +1482,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1530,35 +1511,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1579,7 +1570,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1600,7 +1591,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1621,7 +1612,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1982,13 +1973,13 @@
   
 
 
-<h1 id="how-to-use-an-existing-linstor-cluster">How to Use an Existing LINSTOR Cluster</h1>
+<h1 id="how-to-use-an-existing-linstor-cluster">How to Use an Existing LINSTOR Cluster<a class="headerlink" href="#how-to-use-an-existing-linstor-cluster" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to connect Piraeus with an existing LINSTOR® Cluster, managed outside Kubernetes.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
 <li>editing <code>LinstorCluster</code> resources.</li>
 </ul>
-<h2 id="configure-the-piraeus-resources">Configure the Piraeus Resources</h2>
+<h2 id="configure-the-piraeus-resources">Configure the Piraeus Resources<a class="headerlink" href="#configure-the-piraeus-resources" title="Permanent link">&para;</a></h2>
 <p>To use an externally managed LINSTOR Cluster, specify the URL of the LINSTOR Controller in the <code>LinstorCluster</code>
 resource. In the following example, the Controller is reachable at <code>http://linstor-controller.example.com:3370</code>:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
@@ -2004,7 +1995,7 @@ <h2 id="configure-the-piraeus-resources">Configure the Piraeus Resources</h2>
 <li>The <code>linstor-controller</code> Deployment is removed</li>
 <li>The <code>linstor-csi-controller</code> and <code>linstor-csi-node</code> resources will reference the external controller.</li>
 </ul>
-<h2 id="configuring-host-networking-for-linstor-satellites">Configuring Host Networking for LINSTOR Satellites</h2>
+<h2 id="configuring-host-networking-for-linstor-satellites">Configuring Host Networking for LINSTOR Satellites<a class="headerlink" href="#configuring-host-networking-for-linstor-satellites" title="Permanent link">&para;</a></h2>
 <p>Normally the Pod network is not reachable from outside the Kubernetes Cluster.
 In this case the existing LINSTOR Controller won't be able to communicate with the Satellites in the Kubernetes cluster.
 So you should configure your Satellites to use <a href="../drbd-host-networking/">host networking</a>.</p>
@@ -2018,7 +2009,7 @@ <h2 id="configuring-host-networking-for-linstor-satellites">Configuring Host Net
 <span class="w">    </span><span class="nt">spec</span><span class="p">:</span>
 <span class="w">      </span><span class="nt">hostNetwork</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">true</span>
 </code></pre></div>
-<h2 id="verifying-the-configuration">Verifying the Configuration</h2>
+<h2 id="verifying-the-configuration">Verifying the Configuration<a class="headerlink" href="#verifying-the-configuration" title="Permanent link">&para;</a></h2>
 <p>To verify that the external LINSTOR Controller is configured, check:</p>
 <ul>
 <li>The <code>Available</code> condition on the <code>LinstorCluster</code> resource reports the expected Controller URL:
diff --git a/v2.7.1/how-to/flatcar/index.html b/v2.7.1/how-to/flatcar/index.html
index c3beddb..e4d85c6 100644
--- a/v2.7.1/how-to/flatcar/index.html
+++ b/v2.7.1/how-to/flatcar/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Flatcar Container Linux - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/flatcar.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Flatcar Container Linux - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/flatcar.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1417,8 +1417,6 @@
       
         
       
-        
-      
     
     
       
@@ -1436,7 +1434,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1466,31 +1464,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1512,35 +1493,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1561,7 +1552,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1582,7 +1573,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1603,7 +1594,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1946,13 +1937,13 @@
   
 
 
-<h1 id="how-to-load-drbd-on-flatcar-container-linux">How to Load DRBD on Flatcar Container Linux</h1>
+<h1 id="how-to-load-drbd-on-flatcar-container-linux">How to Load DRBD on Flatcar Container Linux<a class="headerlink" href="#how-to-load-drbd-on-flatcar-container-linux" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to set up the DRBD® Module Loader when using <a href="https://www.flatcar.org">Flatcar Container Linux</a>.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
 <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li>
 </ul>
-<h2 id="configure-the-drbd-module-loader">Configure the DRBD Module Loader</h2>
+<h2 id="configure-the-drbd-module-loader">Configure the DRBD Module Loader<a class="headerlink" href="#configure-the-drbd-module-loader" title="Permanent link">&para;</a></h2>
 <p>Flatcar Container Linux uses a read-only <code>/usr</code> file system. For building DRBD from source on Flatcar Container Linux,
 the default bind mount for the not existing <code>/usr/src</code> directory needs to be disabled for the <code>drbd-module-loader</code> init container.</p>
 <p>To change the configuration for the <code>drbd-module-loader</code> container, apply the following <code>LinstorSatelliteConfiguration</code>:</p>
diff --git a/v2.7.1/how-to/http-proxy/index.html b/v2.7.1/how-to/http-proxy/index.html
index 69a38f8..912f82e 100644
--- a/v2.7.1/how-to/http-proxy/index.html
+++ b/v2.7.1/how-to/http-proxy/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Deploy Piraeus Datastore behind an HTTP Proxy - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/http-proxy.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Deploy Piraeus Datastore behind an HTTP Proxy - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/http-proxy.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1417,8 +1417,6 @@
       
         
       
-        
-      
     
     
       
@@ -1436,7 +1434,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1466,31 +1464,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1512,35 +1493,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1561,7 +1552,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1582,7 +1573,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1603,7 +1594,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1946,14 +1937,14 @@
   
 
 
-<h1 id="how-to-use-piraeus-datastore-with-an-http-proxy">How to Use Piraeus Datastore with an HTTP Proxy</h1>
+<h1 id="how-to-use-piraeus-datastore-with-an-http-proxy">How to Use Piraeus Datastore with an HTTP Proxy<a class="headerlink" href="#how-to-use-piraeus-datastore-with-an-http-proxy" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to configure the DRBD® Module Loader when using a HTTP Proxy.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
 <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li>
 <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li>
 </ul>
-<h2 id="configuration">Configuration</h2>
+<h2 id="configuration">Configuration<a class="headerlink" href="#configuration" title="Permanent link">&para;</a></h2>
 <p>We will use environment variables to configure the proxy, this tells the drbd-module-loader component to use the proxy for outgoing communication.</p>
 <p>Configure the sample below according to your environment and apply the configuration using <code>kubectl apply -f filename.yml</code>.</p>
 <p>This sample configuration assumes that a HTTP proxy is reacheable at <code>http://10.0.0.1:3128</code>.</p>
diff --git a/v2.7.1/how-to/index.html b/v2.7.1/how-to/index.html
index ce09eb6..0836ee0 100644
--- a/v2.7.1/how-to/index.html
+++ b/v2.7.1/how-to/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="How-To Guides - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/README.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="How-To Guides - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/README.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="upgrade/" class="md-tabs__link">
+        <a href="../upgrade/" class="md-tabs__link">
           
   
     
@@ -1366,8 +1366,6 @@
       
         
       
-        
-      
     
     
       
@@ -1385,7 +1383,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="upgrade/" class="md-nav__link ">
+            <a href="../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1415,31 +1413,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1461,35 +1442,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1510,7 +1501,7 @@
   
   
     <li class="md-nav__item">
-      <a href="upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1531,7 +1522,7 @@
   
   
     <li class="md-nav__item">
-      <a href="upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1552,7 +1543,7 @@
   
   
     <li class="md-nav__item">
-      <a href="upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1931,9 +1922,9 @@
   
 
 
-<h1 id="how-to">How To</h1>
+<h1 id="how-to">How To<a class="headerlink" href="#how-to" title="Permanent link">&para;</a></h1>
 <p>These guides show you how to configure a specific aspect or achieve a specific task with Piraeus Datastore.</p>
-<h2 id="advanced-deployments">Advanced Deployments</h2>
+<h2 id="advanced-deployments">Advanced Deployments<a class="headerlink" href="#advanced-deployments" title="Permanent link">&para;</a></h2>
 <div class="cards grid">
 <ul>
 <li>
@@ -1946,7 +1937,7 @@ <h2 id="advanced-deployments">Advanced Deployments</h2>
 </li>
 </ul>
 </div>
-<h2 id="securing-components">Securing Components</h2>
+<h2 id="securing-components">Securing Components<a class="headerlink" href="#securing-components" title="Permanent link">&para;</a></h2>
 <div class="cards grid">
 <ul>
 <li>
@@ -1967,7 +1958,7 @@ <h2 id="securing-components">Securing Components</h2>
 </li>
 </ul>
 </div>
-<h2 id="kubernetes-distributions">Kubernetes Distributions</h2>
+<h2 id="kubernetes-distributions">Kubernetes Distributions<a class="headerlink" href="#kubernetes-distributions" title="Permanent link">&para;</a></h2>
 <div class="cards grid">
 <ul>
 <li>
@@ -1992,7 +1983,7 @@ <h2 id="kubernetes-distributions">Kubernetes Distributions</h2>
 </li>
 </ul>
 </div>
-<h2 id="networking">Networking</h2>
+<h2 id="networking">Networking<a class="headerlink" href="#networking" title="Permanent link">&para;</a></h2>
 <div class="cards grid">
 <ul>
 <li>
@@ -2009,7 +2000,7 @@ <h2 id="networking">Networking</h2>
 </li>
 </ul>
 </div>
-<h2 id="maintenance-tasks">Maintenance Tasks</h2>
+<h2 id="maintenance-tasks">Maintenance Tasks<a class="headerlink" href="#maintenance-tasks" title="Permanent link">&para;</a></h2>
 <div class="cards grid">
 <ul>
 <li>
diff --git a/v2.7.1/how-to/install-kernel-headers/index.html b/v2.7.1/how-to/install-kernel-headers/index.html
index 9f848a9..a9091d8 100644
--- a/v2.7.1/how-to/install-kernel-headers/index.html
+++ b/v2.7.1/how-to/install-kernel-headers/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Install Kernel Headers to build DRBD - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/install-kernel-headers.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Install Kernel Headers to build DRBD - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/install-kernel-headers.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1435,8 +1435,6 @@
       
         
       
-        
-      
     
     
       
@@ -1454,7 +1452,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1484,31 +1482,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1530,35 +1511,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1579,7 +1570,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1600,7 +1591,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1621,7 +1612,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1982,14 +1973,14 @@
   
 
 
-<h1 id="installing-linux-kernel-headers">Installing Linux Kernel Headers</h1>
+<h1 id="installing-linux-kernel-headers">Installing Linux Kernel Headers<a class="headerlink" href="#installing-linux-kernel-headers" title="Permanent link">&para;</a></h1>
 <p>Piraeus Datastore uses <a href="https://linbit.com/DRBD/">DRBD®</a> to mirror your volume data to one or more nodes. This document
 aims to describe the way to install the necessary files for common Linux distributions.</p>
 <p>To check if your nodes already have the necessary files installed, try running:</p>
 <div class="highlight"><pre><span></span><code>$ test -d /lib/modules/$(uname -r)/build/ &amp;&amp; echo found headers
 </code></pre></div>
 <p>If the command prints <code>found headers</code>, your nodes are good to go.</p>
-<h2 id="installing-on-ubuntu">Installing on Ubuntu</h2>
+<h2 id="installing-on-ubuntu">Installing on Ubuntu<a class="headerlink" href="#installing-on-ubuntu" title="Permanent link">&para;</a></h2>
 <p>Installation of Linux Kernel headers on Ubuntu can be done through the <code>apt</code> package manager:</p>
 <div class="highlight"><pre><span></span><code>$ sudo apt-get update
 $ sudo apt-get install -y linux-headers-$(uname -r)
@@ -1999,7 +1990,7 @@ <h2 id="installing-on-ubuntu">Installing on Ubuntu</h2>
 <div class="highlight"><pre><span></span><code>$ sudo apt-get update
 $ sudo apt-get install -y linux-headers-virtual
 </code></pre></div>
-<h2 id="installing-on-debian">Installing on Debian</h2>
+<h2 id="installing-on-debian">Installing on Debian<a class="headerlink" href="#installing-on-debian" title="Permanent link">&para;</a></h2>
 <p>Installation of Linux Kernel headers on Debian can be done through the <code>apt</code> package manager:</p>
 <div class="highlight"><pre><span></span><code>$ sudo apt-get update
 $ sudo apt-get install -y linux-headers-$(uname -r)
@@ -2008,7 +1999,7 @@ <h2 id="installing-on-debian">Installing on Debian</h2>
 <div class="highlight"><pre><span></span><code>$ sudo apt-get update
 $ sudo apt-get install -y linux-headers-$(dpkg --print-architecture)
 </code></pre></div>
-<h2 id="installing-on-redhat-enterprise-linux">Installing on RedHat Enterprise Linux</h2>
+<h2 id="installing-on-redhat-enterprise-linux">Installing on RedHat Enterprise Linux<a class="headerlink" href="#installing-on-redhat-enterprise-linux" title="Permanent link">&para;</a></h2>
 <p>Installing on RedHat Enterprise Linux or compatible distributions, such as AlmaLinux or Rocky Linux can be done through
 the <code>dnf</code> package manager:</p>
 <div class="highlight"><pre><span></span><code>$ sudo dnf install -y kernel-devel-$(uname -r)
diff --git a/v2.7.1/how-to/internal-tls/index.html b/v2.7.1/how-to/internal-tls/index.html
index 3e3ecc1..d6f9ee9 100644
--- a/v2.7.1/how-to/internal-tls/index.html
+++ b/v2.7.1/how-to/internal-tls/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Configure TLS Between LINSTOR Controller and LINSTOR Satellite - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/internal-tls.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Configure TLS Between LINSTOR Controller and LINSTOR Satellite - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/internal-tls.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1435,8 +1435,6 @@
       
         
       
-        
-      
     
     
       
@@ -1454,7 +1452,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1484,31 +1482,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1530,35 +1511,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1579,7 +1570,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1600,7 +1591,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1621,7 +1612,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1982,7 +1973,7 @@
   
 
 
-<h1 id="how-to-configure-tls-between-linstor-controller-and-linstor-satellite">How to Configure TLS Between LINSTOR Controller and LINSTOR Satellite</h1>
+<h1 id="how-to-configure-tls-between-linstor-controller-and-linstor-satellite">How to Configure TLS Between LINSTOR Controller and LINSTOR Satellite<a class="headerlink" href="#how-to-configure-tls-between-linstor-controller-and-linstor-satellite" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to set up TLS between LINSTOR® Controller and LINSTOR Satellite.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
@@ -1990,7 +1981,7 @@ <h1 id="how-to-configure-tls-between-linstor-controller-and-linstor-satellite">H
 <li>using the LINSTOR client to verify success.</li>
 <li>using either <a href="https://cert-manager.io">cert-manager</a> or <code>openssl</code> to create TLS certificates.</li>
 </ul>
-<h2 id="provision-keys-and-certificates-using-cert-manager">Provision Keys and Certificates Using cert-manager</h2>
+<h2 id="provision-keys-and-certificates-using-cert-manager">Provision Keys and Certificates Using cert-manager<a class="headerlink" href="#provision-keys-and-certificates-using-cert-manager" title="Permanent link">&para;</a></h2>
 <p>This method requires a working <a href="https://cert-manager.io">cert-manager</a> deployment in your cluster. For an alternative
 way to provision keys and certificates, see the <a href="#provision-keys-and-certificates-using-openssl"><code>openssl</code> section</a>
 below.</p>
@@ -2056,7 +2047,7 @@ <h2 id="provision-keys-and-certificates-using-cert-manager">Provision Keys and C
 </code></pre></div>
 <p>This completes the necessary steps for secure TLS connections between LINSTOR Controller and Satellite using
 cert-manager. Skip to the <a href="#verifying-tls-configuration">last section</a> to verify TLS is working.</p>
-<h2 id="provision-keys-and-certificates-using-openssl">Provision Keys and Certificates Using <code>openssl</code></h2>
+<h2 id="provision-keys-and-certificates-using-openssl">Provision Keys and Certificates Using <code>openssl</code><a class="headerlink" href="#provision-keys-and-certificates-using-openssl" title="Permanent link">&para;</a></h2>
 <p>If you completed the <a href="#provision-keys-and-certificates-using-cert-manager">cert-manager section</a> above, skip directly
 to the <a href="#verifying-tls-configuration">verifying the configuration</a> below.</p>
 <p>This method requires the <code>openssl</code> program on the command line. For an alternative way to provision keys and
@@ -2095,7 +2086,7 @@ <h2 id="provision-keys-and-certificates-using-openssl">Provision Keys and Certif
 <span class="w">  </span><span class="nt">internalTLS</span><span class="p">:</span>
 <span class="w">    </span><span class="nt">secretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">linstor-satellite-internal-tls</span>
 </code></pre></div>
-<h2 id="verifying-tls-configuration">Verifying TLS Configuration</h2>
+<h2 id="verifying-tls-configuration">Verifying TLS Configuration<a class="headerlink" href="#verifying-tls-configuration" title="Permanent link">&para;</a></h2>
 <p>You can verify the secure TLS connection between LINSTOR Controller and Satellite by checking the output of the
 <code>linstor node list</code> command. If TLS is enabled, you will see <code>(SSL)</code> next to the active satellite address:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl exec -n piraeus-datastore deploy/linstor-controller -- linstor node list
diff --git a/v2.7.1/how-to/k0s/index.html b/v2.7.1/how-to/k0s/index.html
index d3774fd..19db8de 100644
--- a/v2.7.1/how-to/k0s/index.html
+++ b/v2.7.1/how-to/k0s/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="k0s - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/k0s.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="k0s - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/k0s.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1417,8 +1417,6 @@
       
         
       
-        
-      
     
     
       
@@ -1436,7 +1434,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1466,31 +1464,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1512,35 +1493,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1561,7 +1552,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1582,7 +1573,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1603,7 +1594,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1946,13 +1937,13 @@
   
 
 
-<h1 id="how-to-configure-piraeus-datastore-on-k0s">How to Configure Piraeus Datastore on k0s</h1>
+<h1 id="how-to-configure-piraeus-datastore-on-k0s">How to Configure Piraeus Datastore on k0s<a class="headerlink" href="#how-to-configure-piraeus-datastore-on-k0s" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to configure Piraeus Datastore when using <a href="https://k0sproject.io">k0s</a>.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
 <li>editing <code>LinstorCluster</code> resources.</li>
 </ul>
-<h2 id="configure-the-csi-driver">Configure the CSI Driver</h2>
+<h2 id="configure-the-csi-driver">Configure the CSI Driver<a class="headerlink" href="#configure-the-csi-driver" title="Permanent link">&para;</a></h2>
 <p>Because k0s store their state in a separate directory (<code>/var/lib/k0s</code>) the LINSTOR CSI Driver needs to be updated to use a new path for mounting volumes.</p>
 <p>To change the LINSTOR CSI Driver, so that it uses the k0s state paths, apply the following <code>LinstorCluster</code>:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
diff --git a/v2.7.1/how-to/linstor-affinity-controller/index.html b/v2.7.1/how-to/linstor-affinity-controller/index.html
index 0a7198c..e6978fc 100644
--- a/v2.7.1/how-to/linstor-affinity-controller/index.html
+++ b/v2.7.1/how-to/linstor-affinity-controller/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Keep Persistent Volume Affinity Updated with LINSTOR Affinity Controller - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/linstor-affinity-controller.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Keep Persistent Volume Affinity Updated with LINSTOR Affinity Controller - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/linstor-affinity-controller.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1426,8 +1426,6 @@
       
         
       
-        
-      
     
     
       
@@ -1445,7 +1443,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1475,31 +1473,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1521,35 +1502,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1570,7 +1561,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1591,7 +1582,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1612,7 +1603,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1964,7 +1955,7 @@
   
 
 
-<h1 id="how-to-deploy-the-linstor-affinity-controller">How to Deploy the LINSTOR Affinity Controller</h1>
+<h1 id="how-to-deploy-the-linstor-affinity-controller">How to Deploy the LINSTOR Affinity Controller<a class="headerlink" href="#how-to-deploy-the-linstor-affinity-controller" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to deploy the <a href="https://github.com/piraeusdatastore/linstor-affinity-controller">LINSTOR Affinity Controller</a> for Piraeus Datastore.</p>
 <p>The LINSTOR Affinity Controller keeps the affinity of your volumes in sync between Kubernetes and LINSTOR.</p>
 <p>When using a strict volume affinity setting, such as <code>allowRemoteVolumeAccess: false</code>, the Persistent Volume (PV)
@@ -1975,12 +1966,12 @@ <h1 id="how-to-deploy-the-linstor-affinity-controller">How to Deploy the LINSTOR
 <ul>
 <li>Deploying workloads in Kubernetes using <a href="https://helm.sh/"><code>helm</code></a></li>
 </ul>
-<h2 id="add-the-piraeus-datastore-chart-repository">Add the Piraeus Datastore Chart Repository</h2>
+<h2 id="add-the-piraeus-datastore-chart-repository">Add the Piraeus Datastore Chart Repository<a class="headerlink" href="#add-the-piraeus-datastore-chart-repository" title="Permanent link">&para;</a></h2>
 <p>Piraeus Datastore maintains a helm chart repository for commonly deployed components, including the LINSTOR Affinity
 Controller. To add the repository to your helm configuration, run:</p>
 <div class="highlight"><pre><span></span><code>$ helm repo add piraeus-charts https://piraeus.io/helm-charts/
 </code></pre></div>
-<h2 id="deploy-the-linstor-affinity-controller">Deploy the LINSTOR Affinity Controller</h2>
+<h2 id="deploy-the-linstor-affinity-controller">Deploy the LINSTOR Affinity Controller<a class="headerlink" href="#deploy-the-linstor-affinity-controller" title="Permanent link">&para;</a></h2>
 <p>After adding the repository, deploy the LINSTOR Affinity Controller:</p>
 <div class="highlight"><pre><span></span><code>$ helm install linstor-affinity-controller piraeus-charts/linstor-affinity-controller
 NAME: linstor-affinity-controller
diff --git a/v2.7.1/how-to/microk8s/index.html b/v2.7.1/how-to/microk8s/index.html
index 3e238a3..a7bda6d 100644
--- a/v2.7.1/how-to/microk8s/index.html
+++ b/v2.7.1/how-to/microk8s/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Microk8s - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/microk8s.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Microk8s - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/microk8s.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1417,8 +1417,6 @@
       
         
       
-        
-      
     
     
       
@@ -1436,7 +1434,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1466,31 +1464,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1512,35 +1493,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1561,7 +1552,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1582,7 +1573,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1603,7 +1594,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1946,13 +1937,13 @@
   
 
 
-<h1 id="how-to-configure-piraeus-datastore-on-microk8s">How to Configure Piraeus Datastore on MicroK8s</h1>
+<h1 id="how-to-configure-piraeus-datastore-on-microk8s">How to Configure Piraeus Datastore on MicroK8s<a class="headerlink" href="#how-to-configure-piraeus-datastore-on-microk8s" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to configure Piraeus Datastore when using <a href="https://microk8s.io/">MicroK8s</a>.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
 <li>editing <code>LinstorCluster</code> resources.</li>
 </ul>
-<h2 id="configure-the-csi-driver">Configure the CSI Driver</h2>
+<h2 id="configure-the-csi-driver">Configure the CSI Driver<a class="headerlink" href="#configure-the-csi-driver" title="Permanent link">&para;</a></h2>
 <p>MicroK8s is distributed as a <a href="https://ubuntu.com/core/services/guide/snaps-intro">Snap</a>. Because Snaps store their state
 in a separate directory (<code>/var/snap</code>) the LINSTOR CSI Driver needs to be updated to use a new path for mounting volumes.</p>
 <p>To change the LINSTOR CSI Driver, so that it uses the MicroK8s state paths, apply the following <code>LinstorCluster</code>:</p>
diff --git a/v2.7.1/how-to/monitoring/index.html b/v2.7.1/how-to/monitoring/index.html
index a9a7b5e..55adee5 100644
--- a/v2.7.1/how-to/monitoring/index.html
+++ b/v2.7.1/how-to/monitoring/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Monitor Piraeus Datastore with Prometheus Operator - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/monitoring.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Monitor Piraeus Datastore with Prometheus Operator - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/monitoring.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1435,8 +1435,6 @@
       
         
       
-        
-      
     
     
       
@@ -1454,7 +1452,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1484,31 +1482,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1530,35 +1511,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1579,7 +1570,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1600,7 +1591,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1621,7 +1612,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1982,7 +1973,7 @@
   
 
 
-<h1 id="how-to-deploy-monitoring-with-prometheus-operator">How to Deploy Monitoring with Prometheus Operator</h1>
+<h1 id="how-to-deploy-monitoring-with-prometheus-operator">How to Deploy Monitoring with Prometheus Operator<a class="headerlink" href="#how-to-deploy-monitoring-with-prometheus-operator" title="Permanent link">&para;</a></h1>
 <p>Piraeus Datastore offers integration with the <a href="https://github.com/prometheus-operator/kube-prometheus">Prometheus monitoring stack</a>.</p>
 <p>The integration configures:</p>
 <ul>
@@ -1995,7 +1986,7 @@ <h1 id="how-to-deploy-monitoring-with-prometheus-operator">How to Deploy Monitor
 <li>Deploying workloads in Kubernetes using <a href="https://helm.sh/"><code>helm</code></a></li>
 <li>Deploying resources using <a href="https://kubernetes.io/docs/tasks/tools/"><code>kubectl</code></a></li>
 </ul>
-<h2 id="deploying-prometheus-operator">Deploying Prometheus Operator</h2>
+<h2 id="deploying-prometheus-operator">Deploying Prometheus Operator<a class="headerlink" href="#deploying-prometheus-operator" title="Permanent link">&para;</a></h2>
 <blockquote>
 <p>🗒️ NOTE: If you already have a working Prometheus Operator deployment, skip this step.</p>
 </blockquote>
@@ -2017,12 +2008,12 @@ <h2 id="deploying-prometheus-operator">Deploying Prometheus Operator</h2>
 Datastore is usually deployed in a different namespace, so Prometheus needs to be configured to watch this namespace.
 In the example above, this is achieved by setting the various <code>*NilUsesHelmValues</code> parameters to <code>false</code>.</p>
 </blockquote>
-<h2 id="deploying-monitoring-and-alerting-rules-for-piraeus-datastore">Deploying Monitoring and Alerting Rules for Piraeus Datastore</h2>
+<h2 id="deploying-monitoring-and-alerting-rules-for-piraeus-datastore">Deploying Monitoring and Alerting Rules for Piraeus Datastore<a class="headerlink" href="#deploying-monitoring-and-alerting-rules-for-piraeus-datastore" title="Permanent link">&para;</a></h2>
 <p>After creating a Prometheus Operator deployment and configuring it to watch all namespaces, apply the monitoring
 and alerting resources for Piraeus Datastore:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl apply --server-side -n piraeus-datastore -k &quot;https://github.com/piraeusdatastore/piraeus-operator//config/extras/monitoring?ref=v2&quot;
 </code></pre></div>
-<h2 id="verify-monitoring">Verify Monitoring</h2>
+<h2 id="verify-monitoring">Verify Monitoring<a class="headerlink" href="#verify-monitoring" title="Permanent link">&para;</a></h2>
 <p>Verify that the monitoring configuration is working by checking the prometheus console. First, get access to the
 prometheus console from your local browser by forwarding it to local port 9090:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl port-forward -n monitoring services/prometheus-kube-prometheus-prometheus 9090:9090
diff --git a/v2.7.1/how-to/network-policy/index.html b/v2.7.1/how-to/network-policy/index.html
index 29fc304..9940fa9 100644
--- a/v2.7.1/how-to/network-policy/index.html
+++ b/v2.7.1/how-to/network-policy/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Deploy a NetworkPolicy for Piraeus Datastore - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/network-policy.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Deploy a NetworkPolicy for Piraeus Datastore - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/network-policy.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1378,8 +1378,6 @@
       
         
       
-        
-      
     
     
       
@@ -1397,7 +1395,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1427,31 +1425,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1473,35 +1454,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1522,7 +1513,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1543,7 +1534,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1564,7 +1555,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1890,7 +1881,7 @@
   
 
 
-<h1 id="how-to-deploy-a-networkpolicy-for-piraeus-datastore">How to Deploy a NetworkPolicy for Piraeus Datastore</h1>
+<h1 id="how-to-deploy-a-networkpolicy-for-piraeus-datastore">How to Deploy a NetworkPolicy for Piraeus Datastore<a class="headerlink" href="#how-to-deploy-a-networkpolicy-for-piraeus-datastore" title="Permanent link">&para;</a></h1>
 <p><a href="https://kubernetes.io/docs/concepts/services-networking/network-policies/">Network Policies</a> offer a way to restrict network access of specific pods. They can be used to block undesired
 network connections to specific Pods.</p>
 <p>Piraeus Datastore provides basic Network Policies that configure restricted access to the LINSTOR Satellites.
diff --git a/v2.7.1/how-to/openshift/index.html b/v2.7.1/how-to/openshift/index.html
index c7b0846..808630e 100644
--- a/v2.7.1/how-to/openshift/index.html
+++ b/v2.7.1/how-to/openshift/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Openshift - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/openshift.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Openshift - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/openshift.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1435,8 +1435,6 @@
       
         
       
-        
-      
     
     
       
@@ -1454,7 +1452,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1484,31 +1482,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1530,35 +1511,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1579,7 +1570,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1600,7 +1591,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1621,7 +1612,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1982,21 +1973,21 @@
   
 
 
-<h1 id="how-to-load-drbd-on-openshift">How to Load DRBD on OpenShift</h1>
+<h1 id="how-to-load-drbd-on-openshift">How to Load DRBD on OpenShift<a class="headerlink" href="#how-to-load-drbd-on-openshift" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to set the DRBD® Module Loader when using OpenShift.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
 <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li>
 <li>using the <code>oc</code> command line tool to access the OpenShift cluster.</li>
 </ul>
-<h2 id="find-the-driver-toolkit-image">Find the Driver Toolkit Image</h2>
+<h2 id="find-the-driver-toolkit-image">Find the Driver Toolkit Image<a class="headerlink" href="#find-the-driver-toolkit-image" title="Permanent link">&para;</a></h2>
 <p>The <a href="https://github.com/openshift/driver-toolkit">Driver Toolkit</a> image contains the necessary files for building DRBD.
 Every OpenShift release includes a version of the Driver Toolkit image matching the operating system version of the
 release. You can use <code>oc</code> to print the correct image version:</p>
 <div class="highlight"><pre><span></span><code>$ oc adm release info --image-for=driver-toolkit
 quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709
 </code></pre></div>
-<h2 id="configure-the-drbd-module-loader">Configure the DRBD Module Loader</h2>
+<h2 id="configure-the-drbd-module-loader">Configure the DRBD Module Loader<a class="headerlink" href="#configure-the-drbd-module-loader" title="Permanent link">&para;</a></h2>
 <p>By default, the DRBD Module Loader will try to find the necessary header files to build DRBD from source on the host
 system. In OpenShift, these header files are not included in the host system. Instead, they are included in the Driver
 Toolkit image.</p>
@@ -2034,7 +2025,7 @@ <h2 id="configure-the-drbd-module-loader">Configure the DRBD Module Loader</h2>
 <p><strong>NOTE</strong>: Replace the <code>image</code> of the <code>kernel-header-copy</code> container with the image returned by <code>oc adm release info</code>.</p>
 <p>After the automatic restart of the LINSTOR® Satellite Pods, DRBD will be built from source, using the correct header
 files.</p>
-<h2 id="openshift-update-considerations">OpenShift Update Considerations</h2>
+<h2 id="openshift-update-considerations">OpenShift Update Considerations<a class="headerlink" href="#openshift-update-considerations" title="Permanent link">&para;</a></h2>
 <p>OpenShift updates also update the host operating system. Since every node will be rebooted during the update, the DRBD
 Module loader needs to rebuild DRBD once after the restart for the new host operating system.</p>
 <p>To ensure that the DRBD rebuild is successful, you need to update the image in the <code>openshift-loader-override</code>
diff --git a/v2.7.1/how-to/restore-linstor-db/index.html b/v2.7.1/how-to/restore-linstor-db/index.html
index 52e49a6..8798435 100644
--- a/v2.7.1/how-to/restore-linstor-db/index.html
+++ b/v2.7.1/how-to/restore-linstor-db/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -18,7 +18,7 @@
         <link rel="prev" href="../linstor-affinity-controller/">
       
       
-        <link rel="next" href="../upgrade/">
+        <link rel="next" href="../../upgrade/">
       
       
       <link rel="icon" href="../../assets/favicon.png">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Restore a LINSTOR Database Backup - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/restore-linstor-db.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Restore a LINSTOR Database Backup - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/restore-linstor-db.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1453,8 +1453,6 @@
       
         
       
-        
-      
     
     
       
@@ -1472,7 +1470,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1502,31 +1500,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1548,35 +1529,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1597,7 +1588,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1618,7 +1609,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1639,7 +1630,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -2018,7 +2009,7 @@
   
 
 
-<h1 id="how-to-restore-a-linstor-database-backup">How to Restore a LINSTOR Database Backup</h1>
+<h1 id="how-to-restore-a-linstor-database-backup">How to Restore a LINSTOR Database Backup<a class="headerlink" href="#how-to-restore-a-linstor-database-backup" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to restore a LINSTOR® Controller from a database backup. A backup is created automatically
 on every database migration of the default <code>k8s</code> database.</p>
 <blockquote>
@@ -2030,7 +2021,7 @@ <h1 id="how-to-restore-a-linstor-database-backup">How to Restore a LINSTOR Datab
 <ul>
 <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li>
 </ul>
-<h2 id="find-the-latest-backup">Find the Latest Backup</h2>
+<h2 id="find-the-latest-backup">Find the Latest Backup<a class="headerlink" href="#find-the-latest-backup" title="Permanent link">&para;</a></h2>
 <p>The backup is stored in Kubernetes Secrets. List all backups by using the following command:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl get secrets --field-selector type=piraeus.io/linstor-backup --sort-by .metadata.creationTimestamp -ocustom-columns=&quot;NAME:.metadata.name,CREATED-AT:metadata.creationTimestamp,VERSION:.metadata.annotations.piraeus\.io/linstor-version&quot;
 NAME                                                     CREATED-AT             VERSION
@@ -2041,7 +2032,7 @@ <h2 id="find-the-latest-backup">Find the Latest Backup</h2>
 we set:</p>
 <div class="highlight"><pre><span></span><code>$ BACKUP_NAME=linstor-backup-for-linstor-controller-db7fbfd95-zsfmm
 </code></pre></div>
-<h2 id="temporarily-stop-the-linstor-controller-deployment">Temporarily stop the LINSTOR Controller Deployment</h2>
+<h2 id="temporarily-stop-the-linstor-controller-deployment">Temporarily stop the LINSTOR Controller Deployment<a class="headerlink" href="#temporarily-stop-the-linstor-controller-deployment" title="Permanent link">&para;</a></h2>
 <p>To safely restore the database, ensure that the LINSTOR Controller is shut down by scaling the Piraeus Operator and
 LINSTOR Controller deployment to 0 replicas:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl scale deployment piraeus-operator-controller-manager --replicas 0
@@ -2049,14 +2040,14 @@ <h2 id="temporarily-stop-the-linstor-controller-deployment">Temporarily stop the
 $ kubectl scale deployment linstor-controller --replicas 0
 deployment.apps/linstor-controller scaled
 </code></pre></div>
-<h2 id="create-a-new-backup-of-the-current-cluster-state">Create a New Backup of the Current Cluster State</h2>
+<h2 id="create-a-new-backup-of-the-current-cluster-state">Create a New Backup of the Current Cluster State<a class="headerlink" href="#create-a-new-backup-of-the-current-cluster-state" title="Permanent link">&para;</a></h2>
 <p>Since the restore process is destructive, first create a backup of the current database:</p>
 <div class="highlight"><pre><span></span><code>$ mkdir backup
 $ cd backup
 $ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty kubectl get crds -oyaml &gt; crds.yaml
 $ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty -I {} sh -c &#39;kubectl get {} -oyaml &gt; {}.yaml&#39;
 </code></pre></div>
-<h2 id="restore-the-database">Restore the Database</h2>
+<h2 id="restore-the-database">Restore the Database<a class="headerlink" href="#restore-the-database" title="Permanent link">&para;</a></h2>
 <p>Copy and unpack the selected backup to a local directory by using the following commands:</p>
 <div class="highlight"><pre><span></span><code>$ mkdir restore
 $ cd restore
@@ -2070,7 +2061,7 @@ <h2 id="restore-the-database">Restore the Database</h2>
 <div class="highlight"><pre><span></span><code>$ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty kubectl delete crds
 $ kubectl create -f .
 </code></pre></div>
-<h2 id="restart-the-linstor-controller-deployment">Restart the LINSTOR Controller Deployment</h2>
+<h2 id="restart-the-linstor-controller-deployment">Restart the LINSTOR Controller Deployment<a class="headerlink" href="#restart-the-linstor-controller-deployment" title="Permanent link">&para;</a></h2>
 <p>Now we can safely restart the Piraeus Operator and LINSTOR Controller Deployment.</p>
 <div class="highlight"><pre><span></span><code>$ kubectl scale deployment piraeus-operator-controller-manager --replicas 1
 deployment.apps/piraeus-operator-controller-manager scaled
@@ -2138,7 +2129,7 @@ <h2 id="restart-the-linstor-controller-deployment">Restart the LINSTOR Controlle
         
         
           
-          <a href="../upgrade/" class="md-footer__link md-footer__link--next" aria-label="Next: Upgrades">
+          <a href="../../upgrade/" class="md-footer__link md-footer__link--next" aria-label="Next: Upgrades">
             <div class="md-footer__title">
               <span class="md-footer__direction">
                 Next
diff --git a/v2.7.1/how-to/secure-boot/index.html b/v2.7.1/how-to/secure-boot/index.html
index bfb465b..a2716f8 100644
--- a/v2.7.1/how-to/secure-boot/index.html
+++ b/v2.7.1/how-to/secure-boot/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Load DRBD with SecureBoot Enabled - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/secure-boot.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Load DRBD with SecureBoot Enabled - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/secure-boot.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1453,8 +1453,6 @@
       
         
       
-        
-      
     
     
       
@@ -1472,7 +1470,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1502,31 +1500,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1548,35 +1529,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1597,7 +1588,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1618,7 +1609,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1639,7 +1630,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -2018,7 +2009,7 @@
   
 
 
-<h1 id="how-to-load-drbd-with-secureboot-enabled">How to Load DRBD with SecureBoot Enabled</h1>
+<h1 id="how-to-load-drbd-with-secureboot-enabled">How to Load DRBD with SecureBoot Enabled<a class="headerlink" href="#how-to-load-drbd-with-secureboot-enabled" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to use the DRBD® Module Loader on machines with SecureBoot enabled.</p>
 <p>When SecureBoot is enabled the Linux Kernel refuses to load unsigned kernel modules. Since the DRBD modules are built
 from source, they do not have a valid signature by default. To load them, they need to be signed, and the signing key
@@ -2030,7 +2021,7 @@ <h1 id="how-to-load-drbd-with-secureboot-enabled">How to Load DRBD with SecureBo
 <li>managing machine owner keys with <code>mokutil</code>.</li>
 <li>creating and protecting Kubernetes Secret resources.</li>
 </ul>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li>A Kubernetes node running with SecureBoot enabled. This can be checked by running the following command on each node:
   <div class="highlight"><pre><span></span><code># mokutil --sb-state
@@ -2038,7 +2029,7 @@ <h2 id="prerequisites">Prerequisites</h2>
 </code></pre></div></li>
 <li>Console access to the machine during early boot, or permissions to update the EFI platform keys another way.</li>
 </ul>
-<h2 id="generate-key-material">Generate Key Material</h2>
+<h2 id="generate-key-material">Generate Key Material<a class="headerlink" href="#generate-key-material" title="Permanent link">&para;</a></h2>
 <p>Create a private key and self-signed certificate using the <code>openssl</code> command line utility. The following command will
 create a new private key named <code>signing_key.pem</code> and a certificate named <code>signing_key.x509</code>, valid for 10 years, in the
 appropriate format:</p>
@@ -2063,7 +2054,7 @@ <h2 id="generate-key-material">Generate Key Material</h2>
 authorityKeyIdentifier=keyid
 EOF
 </code></pre></div>
-<h2 id="enroll-the-certificate-in-the-machine-trust-store">Enroll the Certificate in the Machine Trust Store</h2>
+<h2 id="enroll-the-certificate-in-the-machine-trust-store">Enroll the Certificate in the Machine Trust Store<a class="headerlink" href="#enroll-the-certificate-in-the-machine-trust-store" title="Permanent link">&para;</a></h2>
 <p>The generated certificate needs to be added to the machine's trust store. This step depends on the machine platform you
 are using. The instructions here apply to any system where you have console access during early boot, such as bare-metal
 or most virtualization platforms.</p>
@@ -2085,7 +2076,7 @@ <h2 id="enroll-the-certificate-in-the-machine-trust-store">Enroll the Certificat
 <p><img alt="mok-password.png" src="../../assets/mok-password.png" />
 * Reboot the machine:</p>
 <p><img alt="mok-reboot.png" src="../../assets/mok-reboot.png" /></p>
-<h2 id="sign-the-drbd-module-using-the-created-key-material">Sign the DRBD Module Using the Created Key Material</h2>
+<h2 id="sign-the-drbd-module-using-the-created-key-material">Sign the DRBD Module Using the Created Key Material<a class="headerlink" href="#sign-the-drbd-module-using-the-created-key-material" title="Permanent link">&para;</a></h2>
 <p>Create a Kubernetes Secret resource containing the generated key material. The following command creates a secret named
 <code>drbd-signing-keys</code>:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl create secret generic drbd-signing-keys --type piraeus.io/signing-key \
@@ -2116,7 +2107,7 @@ <h2 id="sign-the-drbd-module-using-the-created-key-material">Sign the DRBD Modul
 <span class="w">        </span><span class="nt">secret</span><span class="p">:</span>
 <span class="w">          </span><span class="nt">secretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">drbd-signing-keys</span>
 </code></pre></div>
-<h2 id="verifying-success">Verifying Success</h2>
+<h2 id="verifying-success">Verifying Success<a class="headerlink" href="#verifying-success" title="Permanent link">&para;</a></h2>
 <p>When everything is configured correctly, the <code>drbd-module-loader</code> init container will be able to insert the DRBD
 modules.</p>
 <div class="highlight"><pre><span></span><code>$ kubectl logs ds/linstor-satellite.node1.example.com drbd-module-loader
diff --git a/v2.7.1/how-to/talos/index.html b/v2.7.1/how-to/talos/index.html
index a4866b2..5e7bd6d 100644
--- a/v2.7.1/how-to/talos/index.html
+++ b/v2.7.1/how-to/talos/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Talos Linux - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/talos.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Talos Linux - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/talos.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1426,8 +1426,6 @@
       
         
       
-        
-      
     
     
       
@@ -1445,7 +1443,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1475,31 +1473,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1521,35 +1502,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1570,7 +1561,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1591,7 +1582,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1612,7 +1603,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1964,7 +1955,7 @@
   
 
 
-<h1 id="how-to-load-drbd-on-talos-linux">How to Load DRBD on Talos Linux</h1>
+<h1 id="how-to-load-drbd-on-talos-linux">How to Load DRBD on Talos Linux<a class="headerlink" href="#how-to-load-drbd-on-talos-linux" title="Permanent link">&para;</a></h1>
 <p>This guide shows you how to set the DRBD® Module Loader when using <a href="https://talos.dev">Talos Linux</a>.</p>
 <p>To complete this guide, you should be familiar with:</p>
 <ul>
@@ -1972,7 +1963,7 @@ <h1 id="how-to-load-drbd-on-talos-linux">How to Load DRBD on Talos Linux</h1>
 <li>using the <code>talosctl</code> command line to to access Talos Linux nodes.</li>
 <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li>
 </ul>
-<h2 id="configure-talos-system-extension-for-drbd">Configure Talos system extension for DRBD</h2>
+<h2 id="configure-talos-system-extension-for-drbd">Configure Talos system extension for DRBD<a class="headerlink" href="#configure-talos-system-extension-for-drbd" title="Permanent link">&para;</a></h2>
 <p>By default, the DRBD Module Loader will try to find the necessary header files to build DRBD from source on the host system. In <a href="https://talos.dev">Talos Linux</a> these header files are not included in the host system. Instead, the Kernel modules is packed into a system extension.</p>
 <p>Ensure Talos has the correct <code>drbd</code> <a href="https://github.com/siderolabs/extensions">system extension</a> loaded for the running Kernel.</p>
 <p>This is done by building a install image from the <a href="https://factory.talos.dev">talos factory</a> with drbd included</p>
@@ -1994,7 +1985,7 @@ <h2 id="configure-talos-system-extension-for-drbd">Configure Talos system extens
 <div class="highlight"><pre><span></span><code>$<span class="w"> </span>talosctl<span class="w"> </span>-n<span class="w"> </span>&lt;NODE_IP&gt;<span class="w"> </span><span class="nb">read</span><span class="w"> </span>/sys/module/drbd/parameters/usermode_helper
 disabled
 </code></pre></div></p>
-<h2 id="configure-the-drbd-module-loader">Configure the DRBD Module Loader</h2>
+<h2 id="configure-the-drbd-module-loader">Configure the DRBD Module Loader<a class="headerlink" href="#configure-the-drbd-module-loader" title="Permanent link">&para;</a></h2>
 <p>To change the DRBD Module Loader, so that it uses the modules provided by system extension, apply the following <code>LinstorSatelliteConfiguration</code>:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorSatelliteConfiguration</span>
diff --git a/v2.7.1/index.html b/v2.7.1/index.html
index 4c93f13..078dc27 100644
--- a/v2.7.1/index.html
+++ b/v2.7.1/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -61,7 +61,7 @@
       
         <meta  property="og:title"  content="Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/README.png" >
       
@@ -77,7 +77,7 @@
       
         <meta  name="twitter:title"  content="Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/README.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="how-to/upgrade/" class="md-tabs__link">
+        <a href="upgrade/" class="md-tabs__link">
           
   
     
@@ -1356,8 +1356,6 @@
       
         
       
-        
-      
     
     
       
@@ -1375,7 +1373,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="how-to/upgrade/" class="md-nav__link ">
+            <a href="upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1405,31 +1403,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1451,35 +1432,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1500,7 +1491,7 @@
   
   
     <li class="md-nav__item">
-      <a href="how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1521,7 +1512,7 @@
   
   
     <li class="md-nav__item">
-      <a href="how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1542,7 +1533,7 @@
   
   
     <li class="md-nav__item">
-      <a href="how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1870,7 +1861,7 @@
   
 
 
-<h1 id="piraeus-datastore">Piraeus Datastore</h1>
+<h1 id="piraeus-datastore">Piraeus Datastore<a class="headerlink" href="#piraeus-datastore" title="Permanent link">&para;</a></h1>
 <p>Piraeus is a cloud-native storage system that empowers Kubernetes Local Persistent Volumes with dynamic provisioning,
 resource management, and high-availability. It deploys and scales out automatically within Kubernetes nodes. With
 Piraeus, Kubernetes workloads can now consume high performance local storage using the same volume APIs that app
@@ -1894,7 +1885,7 @@ <h1 id="piraeus-datastore">Piraeus Datastore</h1>
 <p><span class="twemoji lg middle"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M21 10.12h-6.78l2.74-2.82c-2.73-2.7-7.15-2.8-9.88-.1a6.887 6.887 0 0 0 0 9.8c2.73 2.7 7.15 2.7 9.88 0 1.36-1.35 2.04-2.92 2.04-4.9h2c0 1.98-.88 4.55-2.64 6.29-3.51 3.48-9.21 3.48-12.72 0-3.5-3.47-3.53-9.11-.02-12.58a8.987 8.987 0 0 1 12.65 0L21 3zM12.5 8v4.25l3.5 2.08-.72 1.21L11 13V8z"/></svg></span> <strong>Upgrades</strong></p>
 <hr />
 <p>Read how to upgrade a Piraeus Datastore deployment</p>
-<p><a href="how-to/upgrade/"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.75.75 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0"/></svg></span> Upgrades</a></p>
+<p><a href="upgrade/"><span class="twemoji"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M13.22 19.03a.75.75 0 0 1 0-1.06L18.19 13H3.75a.75.75 0 0 1 0-1.5h14.44l-4.97-4.97a.749.749 0 0 1 .326-1.275.75.75 0 0 1 .734.215l6.25 6.25a.75.75 0 0 1 0 1.06l-6.25 6.25a.75.75 0 0 1-1.06 0"/></svg></span> Upgrades</a></p>
 </li>
 <li>
 <p><span class="twemoji lg middle"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M12 3 1 9l11 6 9-4.91V17h2V9M5 13.18v4L12 21l7-3.82v-4L12 17z"/></svg></span> <strong>Understanding Piraeus Datastore</strong></p>
diff --git a/v2.7.1/reference/index.html b/v2.7.1/reference/index.html
index 50dc37b..487aeb8 100644
--- a/v2.7.1/reference/index.html
+++ b/v2.7.1/reference/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Reference - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/README.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Reference - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/README.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../how-to/upgrade/" class="md-tabs__link">
+        <a href="../upgrade/" class="md-tabs__link">
           
   
     
@@ -1346,8 +1346,6 @@
       
         
       
-        
-      
     
     
       
@@ -1365,7 +1363,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../how-to/upgrade/" class="md-nav__link ">
+            <a href="../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1395,31 +1393,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1441,35 +1422,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1490,7 +1481,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1511,7 +1502,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1532,7 +1523,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1863,7 +1854,7 @@
   
 
 
-<h1 id="api-reference">API Reference</h1>
+<h1 id="api-reference">API Reference<a class="headerlink" href="#api-reference" title="Permanent link">&para;</a></h1>
 <p>This is the API Reference for Piraeus Operator. A user may make modifications to these resources to change the cluster
 state (<code>LinstorCluster</code> or <code>LinstorSatelliteConfiguration</code>) or check the status of a resource (<code>LinstorSatellite</code>).</p>
 <div class="cards grid">
diff --git a/v2.7.1/reference/linstorcluster/index.html b/v2.7.1/reference/linstorcluster/index.html
index c870bba..b9cd76a 100644
--- a/v2.7.1/reference/linstorcluster/index.html
+++ b/v2.7.1/reference/linstorcluster/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="LinstorCluster - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstorcluster.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="LinstorCluster - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstorcluster.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1346,8 +1346,6 @@
       
         
       
-        
-      
     
     
       
@@ -1365,7 +1363,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1395,31 +1393,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1441,35 +1422,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1490,7 +1481,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1511,7 +1502,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1532,7 +1523,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1785,21 +1776,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeSelector">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1809,21 +1785,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeAffinity">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_1" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1833,21 +1794,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.repository">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_2" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1857,21 +1803,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.properties">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_3" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1881,21 +1812,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.linstorPassphraseSecret">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_4" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1905,30 +1821,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.patches">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#warning" class="md-nav__link">
-    <span class="md-ellipsis">
-      Warning
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_5" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1938,21 +1830,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.externalController">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_6" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1962,21 +1839,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.controller">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_7" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1986,21 +1848,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.csiController">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_8" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2010,21 +1857,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.csiNode">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_9" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2034,21 +1866,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.highAvailabilityController">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_10" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2058,30 +1875,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.internalTLS">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_11" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_12" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2091,30 +1884,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.apiTLS">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_13" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_14" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
       </ul>
@@ -2129,15 +1898,21 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
+    <nav class="md-nav" aria-label=".status">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
   <a href="#statusconditions" class="md-nav__link">
     <span class="md-ellipsis">
       .status.conditions
     </span>
   </a>
   
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
     </ul>
@@ -2282,21 +2057,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeSelector">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2306,21 +2066,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeAffinity">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_1" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2330,21 +2075,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.repository">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_2" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2354,21 +2084,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.properties">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_3" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2378,21 +2093,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.linstorPassphraseSecret">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_4" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2402,30 +2102,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.patches">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#warning" class="md-nav__link">
-    <span class="md-ellipsis">
-      Warning
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_5" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2435,21 +2111,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.externalController">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_6" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2459,21 +2120,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.controller">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_7" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2483,21 +2129,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.csiController">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_8" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2507,21 +2138,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.csiNode">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_9" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2531,21 +2147,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.highAvailabilityController">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_10" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2555,30 +2156,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.internalTLS">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_11" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_12" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2588,30 +2165,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.apiTLS">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_13" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_14" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
       </ul>
@@ -2626,15 +2179,21 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
+    <nav class="md-nav" aria-label=".status">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
   <a href="#statusconditions" class="md-nav__link">
     <span class="md-ellipsis">
       .status.conditions
     </span>
   </a>
   
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
     </ul>
@@ -2655,7 +2214,7 @@
   
 
 
-<h1 id="linstorcluster"><code>LinstorCluster</code></h1>
+<h1 id="linstorcluster"><code>LinstorCluster</code><a class="headerlink" href="#linstorcluster" title="Permanent link">&para;</a></h1>
 <p>This resource controls the state of the LINSTOR® cluster and integration with Kubernetes.
 In particular, it controls:</p>
 <ul>
@@ -2663,15 +2222,15 @@ <h1 id="linstorcluster"><code>LinstorCluster</code></h1>
 <li>LINSTOR CSI Driver</li>
 <li><code>LinstorSatellite</code>, configured through <code>LinstorSatelliteConfiguration</code> resources.</li>
 </ul>
-<h2 id="spec"><code>.spec</code></h2>
+<h2 id="spec"><code>.spec</code><a class="headerlink" href="#spec" title="Permanent link">&para;</a></h2>
 <p>Configures the desired state of the cluster.</p>
-<h3 id="specnodeselector"><code>.spec.nodeSelector</code></h3>
+<h3 id="specnodeselector"><code>.spec.nodeSelector</code><a class="headerlink" href="#specnodeselector" title="Permanent link">&para;</a></h3>
 <p>Selects on which nodes Piraeus Datastore should be deployed. Nodes that are
 excluded by the selector will not be able to run any workload using a Piraeus volume.</p>
 <p>If empty (the default), Piraeus will be deployed on all nodes in the cluster.</p>
 <p>When this is used together with <code>.spec.nodeAffinity</code>, both need to match in order for
 a node to run Piraeus.</p>
-<h4 id="example">Example</h4>
+<h4 id="example">Example<a class="headerlink" href="#example" title="Permanent link">&para;</a></h4>
 <p>This example restricts Piraeus Datastore to nodes matching <code>example.com/storage: "yes"</code>:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2681,13 +2240,13 @@ <h4 id="example">Example</h4>
 <span class="w">  </span><span class="nt">nodeSelector</span><span class="p">:</span>
 <span class="w">    </span><span class="nt">example.com/storage</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;yes&quot;</span>
 </code></pre></div>
-<h3 id="specnodeaffinity"><code>.spec.nodeAffinity</code></h3>
+<h3 id="specnodeaffinity"><code>.spec.nodeAffinity</code><a class="headerlink" href="#specnodeaffinity" title="Permanent link">&para;</a></h3>
 <p>Selects on which nodes Piraeus Datastore should be deployed. Nodes that are
 excluded by the affinity will not be able to run any workload using a Piraeus volume.</p>
 <p>If empty (the default), Piraeus will be deployed on all nodes in the cluster.</p>
 <p>When this is used together with <code>.spec.nodeSelector</code>, both need to match in order for
 a node to run Piraeus.</p>
-<h4 id="example_1">Example</h4>
+<h4 id="example_1">Example<a class="headerlink" href="#example_1" title="Permanent link">&para;</a></h4>
 <p>This example restricts Piraeus Datastore to nodes in zones <code>a</code> and <code>b</code>, but not on <code>control-plane</code> nodes:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2705,12 +2264,12 @@ <h4 id="example_1">Example</h4>
 <span class="w">          </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">node-role.kubernetes.io/control-plane</span>
 <span class="w">            </span><span class="nt">operator</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">DoesNotExist</span>
 </code></pre></div>
-<h3 id="specrepository"><code>.spec.repository</code></h3>
+<h3 id="specrepository"><code>.spec.repository</code><a class="headerlink" href="#specrepository" title="Permanent link">&para;</a></h3>
 <p>Sets the default image registry to use for all Piraeus images. The full image name is
 created by appending an image identifier and tag.</p>
 <p>If empty (the default), Piraeus will use <code>quay.io/piraeusdatastore</code>.</p>
-<p>The current list of default images is available <a href="https://github.com/piraeus/config/manager/0_piraeus_datastore_images.yaml">here</a>.</p>
-<h4 id="example_2">Example</h4>
+<p>The current list of default images is available <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v2/config/manager/0_piraeus_datastore_images.yaml">here</a>.</p>
+<h4 id="example_2">Example<a class="headerlink" href="#example_2" title="Permanent link">&para;</a></h4>
 <p>This example pulls all Piraeus images from <code>registry.example.com/piraeus-mirror</code>
 rather than <code>quay.io/piraeusdatastore</code>.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
@@ -2720,9 +2279,9 @@ <h4 id="example_2">Example</h4>
 <span class="nt">spec</span><span class="p">:</span>
 <span class="w">  </span><span class="nt">repository</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">registry.example.com/piraeus-mirror</span>
 </code></pre></div>
-<h3 id="specproperties"><code>.spec.properties</code></h3>
+<h3 id="specproperties"><code>.spec.properties</code><a class="headerlink" href="#specproperties" title="Permanent link">&para;</a></h3>
 <p>Sets the given properties on the LINSTOR Controller level, applying them to the whole Cluster.</p>
-<h4 id="example_3">Example</h4>
+<h4 id="example_3">Example<a class="headerlink" href="#example_3" title="Permanent link">&para;</a></h4>
 <p>This example sets the port range used for DRBD® volumes to <code>10000-20000</code>.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2733,13 +2292,13 @@ <h4 id="example_3">Example</h4>
 <span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">TcpPortAutoRange</span>
 <span class="w">      </span><span class="nt">value</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;10000-20000&quot;</span>
 </code></pre></div>
-<h3 id="speclinstorpassphrasesecret"><code>.spec.linstorPassphraseSecret</code></h3>
+<h3 id="speclinstorpassphrasesecret"><code>.spec.linstorPassphraseSecret</code><a class="headerlink" href="#speclinstorpassphrasesecret" title="Permanent link">&para;</a></h3>
 <p>Configures the <a href="https://linbit.com/drbd-user-guide/linstor-guide-1_0-en/#s-linstor-encrypted-volumes">LINSTOR passphrase</a>,
 used by LINSTOR when creating encrypted volumes and storing access credentials
 for backups.</p>
 <p>The referenced secret must exist in the same namespace as the operator
 (by default <code>piraeus-datastore</code>), and have a <code>MASTER_PASSPHRASE</code> entry.</p>
-<h4 id="example_4">Example</h4>
+<h4 id="example_4">Example<a class="headerlink" href="#example_4" title="Permanent link">&para;</a></h4>
 <p>This example configures a passphrase <code>example-passphrase</code>. Please <strong>choose a different passphrase</strong> for your deployment.</p>
 <div class="highlight"><pre><span></span><code><span class="nn">---</span>
 <span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">v1</span>
@@ -2759,15 +2318,15 @@ <h4 id="example_4">Example</h4>
 <span class="nt">spec</span><span class="p">:</span>
 <span class="w">  </span><span class="nt">linstorPassphraseSecret</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">linstor-passphrase</span>
 </code></pre></div>
-<h3 id="specpatches"><code>.spec.patches</code></h3>
+<h3 id="specpatches"><code>.spec.patches</code><a class="headerlink" href="#specpatches" title="Permanent link">&para;</a></h3>
 <p>The given patches will be applied to all resources controlled by the operator. The patches are
 forwarded to <code>kustomize</code> internally, and take the <a href="https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/patches/">same format</a>.</p>
 <p>The unpatched resources are available in the <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v2/pkg/resources/cluster">subdirectories of the <code>pkg/resources</code> directory</a>.</p>
-<h4 id="warning">Warning</h4>
+<h4 id="warning">Warning<a class="headerlink" href="#warning" title="Permanent link">&para;</a></h4>
 <p>No checks are run on the result of user-supplied patches: the resources are applied
 as-is. Patching some fundamental aspect, such as removing a specific volume from a
 container may lead to a degraded cluster.</p>
-<h4 id="example_5">Example</h4>
+<h4 id="example_5">Example<a class="headerlink" href="#example_5" title="Permanent link">&para;</a></h4>
 <p>This example sets a CPU limit of <code>10m</code> on the CSI Node init container and changes the
 LINSTOR Controller service to run in <code>SingleStack</code> mode.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
@@ -2796,9 +2355,9 @@ <h4 id="example_5">Example</h4>
 <span class="w">        </span><span class="no">spec:</span>
 <span class="w">          </span><span class="no">ipFamilyPolicy: SingleStack</span>
 </code></pre></div>
-<h3 id="specexternalcontroller"><code>.spec.externalController</code></h3>
+<h3 id="specexternalcontroller"><code>.spec.externalController</code><a class="headerlink" href="#specexternalcontroller" title="Permanent link">&para;</a></h3>
 <p>Configures the Operator to use an external controller instead of deploying one in the Cluster.</p>
-<h4 id="example_6">Example</h4>
+<h4 id="example_6">Example<a class="headerlink" href="#example_6" title="Permanent link">&para;</a></h4>
 <p>This examples instructs the Operator to use the external LINSTOR Controller reachable at <code>http://linstor.example.com:3370</code>.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2808,11 +2367,11 @@ <h4 id="example_6">Example</h4>
 <span class="w">  </span><span class="nt">externalController</span><span class="p">:</span>
 <span class="w">    </span><span class="nt">url</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">http://linstor.example.com:3370</span>
 </code></pre></div>
-<h3 id="speccontroller"><code>.spec.controller</code></h3>
+<h3 id="speccontroller"><code>.spec.controller</code><a class="headerlink" href="#speccontroller" title="Permanent link">&para;</a></h3>
 <p>Controls the LINSTOR Controller Deployment:
 * Setting <code>enabled: false</code> disables the controller deployment entirely. See also <a href="#specexternalcontroller"><code>.spec.externalController</code></a>.
 * Setting a <code>podTemplate:</code> allows for simple modification of the LINSTOR Controller Deployment.</p>
-<h4 id="example_7">Example</h4>
+<h4 id="example_7">Example<a class="headerlink" href="#example_7" title="Permanent link">&para;</a></h4>
 <p>This example configures a resource request of <code>memory: 1Gi</code> for the LINSTOR Controller Deployment:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2829,11 +2388,11 @@ <h4 id="example_7">Example</h4>
 <span class="w">              </span><span class="nt">requests</span><span class="p">:</span>
 <span class="w">                </span><span class="nt">memory</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">1Gi</span>
 </code></pre></div>
-<h3 id="speccsicontroller"><code>.spec.csiController</code></h3>
+<h3 id="speccsicontroller"><code>.spec.csiController</code><a class="headerlink" href="#speccsicontroller" title="Permanent link">&para;</a></h3>
 <p>Controls the CSI Controller Deployment:
 * Setting <code>enabled: false</code> disables the deployment entirely.
 * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Controller Deployment.</p>
-<h4 id="example_8">Example</h4>
+<h4 id="example_8">Example<a class="headerlink" href="#example_8" title="Permanent link">&para;</a></h4>
 <p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Controller Deployment:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2850,11 +2409,11 @@ <h4 id="example_8">Example</h4>
 <span class="w">              </span><span class="nt">requests</span><span class="p">:</span>
 <span class="w">                </span><span class="nt">memory</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">1Gi</span>
 </code></pre></div>
-<h3 id="speccsinode"><code>.spec.csiNode</code></h3>
+<h3 id="speccsinode"><code>.spec.csiNode</code><a class="headerlink" href="#speccsinode" title="Permanent link">&para;</a></h3>
 <p>Controls the CSI Node DaemonSet:
 * Setting <code>enabled: false</code> disables the deployment entirely.
 * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Node DaemonSet.</p>
-<h4 id="example_9">Example</h4>
+<h4 id="example_9">Example<a class="headerlink" href="#example_9" title="Permanent link">&para;</a></h4>
 <p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Node DaemonSet:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2871,11 +2430,11 @@ <h4 id="example_9">Example</h4>
 <span class="w">              </span><span class="nt">requests</span><span class="p">:</span>
 <span class="w">                </span><span class="nt">memory</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">1Gi</span>
 </code></pre></div>
-<h3 id="spechighavailabilitycontroller"><code>.spec.highAvailabilityController</code></h3>
+<h3 id="spechighavailabilitycontroller"><code>.spec.highAvailabilityController</code><a class="headerlink" href="#spechighavailabilitycontroller" title="Permanent link">&para;</a></h3>
 <p>Controls the High Availability Controller DaemonSet:
 * Setting <code>enabled: false</code> disables the deployment entirely.
 * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Node Deployment.</p>
-<h4 id="example_10">Example</h4>
+<h4 id="example_10">Example<a class="headerlink" href="#example_10" title="Permanent link">&para;</a></h4>
 <p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Node Deployment:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorCluster</span>
@@ -2892,7 +2451,7 @@ <h4 id="example_10">Example</h4>
 <span class="w">              </span><span class="nt">requests</span><span class="p">:</span>
 <span class="w">                </span><span class="nt">memory</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">1Gi</span>
 </code></pre></div>
-<h3 id="specinternaltls"><code>.spec.internalTLS</code></h3>
+<h3 id="specinternaltls"><code>.spec.internalTLS</code><a class="headerlink" href="#specinternaltls" title="Permanent link">&para;</a></h3>
 <p>Configures a TLS secret used by the LINSTOR Controller to:
 * Validate the certificate of the LINSTOR Satellites, that is the Satellites must have certificates signed by <code>ca.crt</code>.
 * Provide a client certificate for authentication with LINSTOR Satellites, that is <code>tls.key</code> and <code>tls.crt</code> must be accepted by the Satellites.</p>
@@ -2903,7 +2462,7 @@ <h3 id="specinternaltls"><code>.spec.internalTLS</code></h3>
 to let the operator create the required secret.</p>
 <p>If the referenced secret does not contain a <code>ca.crt</code> certificate of a certificate authority, a <code>caReference</code> pointing
 to a secondary <code>Secret</code> or <code>ConfigMap</code> resource can be configured.</p>
-<h4 id="example_11">Example</h4>
+<h4 id="example_11">Example<a class="headerlink" href="#example_11" title="Permanent link">&para;</a></h4>
 <p>This example creates a manually provisioned TLS secret and references it in the
 LinstorCluster configuration.</p>
 <div class="highlight"><pre><span></span><code><span class="nn">---</span>
@@ -2925,7 +2484,7 @@ <h4 id="example_11">Example</h4>
 <span class="w">  </span><span class="nt">internalTLS</span><span class="p">:</span>
 <span class="w">    </span><span class="nt">secretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">my-linstor-controller-tls</span>
 </code></pre></div>
-<h4 id="example_12">Example</h4>
+<h4 id="example_12">Example<a class="headerlink" href="#example_12" title="Permanent link">&para;</a></h4>
 <p>This example sets up automatic creation of the LINSTOR Controller TLS secret using a
 cert-manager issuer named <code>piraeus-root</code>. The certificates will be validated against the certificate in the <code>trust-root</code>
 ConfigMap.</p>
@@ -2943,7 +2502,7 @@ <h4 id="example_12">Example</h4>
 <span class="w">      </span><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">ConfigMap</span>
 <span class="w">      </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">root.crt</span>
 </code></pre></div>
-<h3 id="specapitls"><code>.spec.apiTLS</code></h3>
+<h3 id="specapitls"><code>.spec.apiTLS</code><a class="headerlink" href="#specapitls" title="Permanent link">&para;</a></h3>
 <p>Configures the TLS secrets used to secure the LINSTOR API. There are four different secrets to configure:</p>
 <ul>
 <li><code>apiSecretName</code>: sets the name of the secret used by the LINSTOR Controller to enable HTTPS. Defaults to
@@ -2960,7 +2519,7 @@ <h3 id="specapitls"><code>.spec.apiTLS</code></h3>
 to let the operator create the required secrets.</p>
 <p>If the referenced secret does not contain a <code>ca.crt</code> certificate of a certificate authority, a <code>caReference</code> pointing
 to a secondary <code>Secret</code> or <code>ConfigMap</code> resource can be configured.</p>
-<h4 id="example_13">Example</h4>
+<h4 id="example_13">Example<a class="headerlink" href="#example_13" title="Permanent link">&para;</a></h4>
 <p>This example creates a manually provisioned TLS secret and references it in the
 LinstorCluster configuration. It uses the same secret for all clients of the LINSTOR API.</p>
 <div class="highlight"><pre><span></span><code><span class="nn">---</span>
@@ -2995,7 +2554,7 @@ <h4 id="example_13">Example</h4>
 <span class="w">    </span><span class="nt">csiControllerSecretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">my-linstor-client-tls</span>
 <span class="w">    </span><span class="nt">csiNodeSecretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">my-linstor-client-tls</span>
 </code></pre></div>
-<h4 id="example_14">Example</h4>
+<h4 id="example_14">Example<a class="headerlink" href="#example_14" title="Permanent link">&para;</a></h4>
 <p>This example sets up automatic creation of the LINSTOR API and LINSTOR Client TLS secret using a
 cert-manager issuer named <code>piraeus-root</code>. The certificates will be validated against the certificate in the <code>trust-root</code>
 Secret.</p>
@@ -3013,9 +2572,9 @@ <h4 id="example_14">Example</h4>
 <span class="w">      </span><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Secret</span>
 <span class="w">      </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">root.crt</span>
 </code></pre></div>
-<h2 id="status"><code>.status</code></h2>
+<h2 id="status"><code>.status</code><a class="headerlink" href="#status" title="Permanent link">&para;</a></h2>
 <p>Reports the actual state of the cluster.</p>
-<h2 id="statusconditions"><code>.status.conditions</code></h2>
+<h3 id="statusconditions"><code>.status.conditions</code><a class="headerlink" href="#statusconditions" title="Permanent link">&para;</a></h3>
 <p>The Operator reports the current state of the Cluster through a set of conditions. Conditions are identified by their
 <code>type</code>.</p>
 <table>
diff --git a/v2.7.1/reference/linstornodeconnection/index.html b/v2.7.1/reference/linstornodeconnection/index.html
index f13bb60..a69521d 100644
--- a/v2.7.1/reference/linstornodeconnection/index.html
+++ b/v2.7.1/reference/linstornodeconnection/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="LinstorNodeConnection - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstornodeconnection.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="LinstorNodeConnection - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstornodeconnection.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1346,8 +1346,6 @@
       
         
       
-        
-      
     
     
       
@@ -1365,7 +1363,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1395,31 +1393,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1441,35 +1422,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1490,7 +1481,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1511,7 +1502,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1532,7 +1523,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1827,30 +1818,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.selector">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_1" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1860,21 +1827,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.paths">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_2" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1884,21 +1836,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.properties">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_3" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
       </ul>
@@ -2030,30 +1967,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.selector">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_1" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2063,21 +1976,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.paths">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_2" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2087,21 +1985,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.properties">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_3" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
       </ul>
@@ -2151,12 +2034,12 @@
   
 
 
-<h1 id="linstornodeconnection"><code>LinstorNodeConnection</code></h1>
+<h1 id="linstornodeconnection"><code>LinstorNodeConnection</code><a class="headerlink" href="#linstornodeconnection" title="Permanent link">&para;</a></h1>
 <p>This resource controls the state of the LINSTOR® node connections.</p>
 <p>Node connections control the DRBD options set on a particular path, such as which protocol and network interface to use.</p>
-<h2 id="spec"><code>.spec</code></h2>
+<h2 id="spec"><code>.spec</code><a class="headerlink" href="#spec" title="Permanent link">&para;</a></h2>
 <p>Configures the desired state of the node connections.</p>
-<h3 id="specselector"><code>.spec.selector</code></h3>
+<h3 id="specselector"><code>.spec.selector</code><a class="headerlink" href="#specselector" title="Permanent link">&para;</a></h3>
 <p>Selects which connections the resource should apply to. By default, a <code>LinstorNodeConnection</code> resource applies to every
 possible connection in the cluster.</p>
 <p>A resource applies to a connection if one of the provided selectors match. A selector itself can contain multiple
@@ -2173,7 +2056,7 @@ <h3 id="specselector"><code>.spec.selector</code></h3>
 <li><code>Same</code> the label specified in <code>key</code> has the same value for the nodes in the connection.</li>
 <li><code>NotSame</code> the label specified in <code>key</code> has different values for the nodes in the connection.</li>
 </ul>
-<h4 id="example">Example</h4>
+<h4 id="example">Example<a class="headerlink" href="#example" title="Permanent link">&para;</a></h4>
 <p>This example restricts the resource to connections between nodes matching <code>example.com/storage: "yes"</code>:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorNodeConnection</span>
@@ -2187,7 +2070,7 @@ <h4 id="example">Example</h4>
 <span class="w">          </span><span class="nt">values</span><span class="p">:</span>
 <span class="w">            </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">yes</span>
 </code></pre></div>
-<h4 id="example_1">Example</h4>
+<h4 id="example_1">Example<a class="headerlink" href="#example_1" title="Permanent link">&para;</a></h4>
 <p>This example restricts the resource to connections between nodes in the same region, but different zones.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorNodeConnection</span>
@@ -2201,11 +2084,11 @@ <h4 id="example_1">Example</h4>
 <span class="w">        </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">key</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">topology.kubernetes.io/zone</span>
 <span class="w">          </span><span class="nt">op</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">NotSame</span>
 </code></pre></div>
-<h3 id="specpaths"><code>.spec.paths</code></h3>
+<h3 id="specpaths"><code>.spec.paths</code><a class="headerlink" href="#specpaths" title="Permanent link">&para;</a></h3>
 <p>Paths configure one or more network connections between nodes. If a path is configured, LINSTOR will use the given
 network interface to configure DRBD replication. The network interfaces have to be registered with LINSTOR first, using
 <code>linstor node interface create ...</code>.</p>
-<h4 id="example_2">Example</h4>
+<h4 id="example_2">Example<a class="headerlink" href="#example_2" title="Permanent link">&para;</a></h4>
 <p>This example configures all nodes to use the "data-nic" network interface instead of the default interface.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorNodeConnection</span>
@@ -2216,9 +2099,9 @@ <h4 id="example_2">Example</h4>
 <span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">path1</span>
 <span class="w">      </span><span class="nt">interface</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">data-nic</span>
 </code></pre></div>
-<h3 id="specproperties"><code>.spec.properties</code></h3>
+<h3 id="specproperties"><code>.spec.properties</code><a class="headerlink" href="#specproperties" title="Permanent link">&para;</a></h3>
 <p>Sets the given properties on the LINSTOR Node Connection level.</p>
-<h4 id="example_3">Example</h4>
+<h4 id="example_3">Example<a class="headerlink" href="#example_3" title="Permanent link">&para;</a></h4>
 <p>This example sets the DRBD® protocol to <code>C</code>.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorNodeConnection</span>
@@ -2229,9 +2112,9 @@ <h4 id="example_3">Example</h4>
 <span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">DrbdOptions/Net/protocol</span>
 <span class="w">      </span><span class="nt">value</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">C</span>
 </code></pre></div>
-<h2 id="status"><code>.status</code></h2>
+<h2 id="status"><code>.status</code><a class="headerlink" href="#status" title="Permanent link">&para;</a></h2>
 <p>Reports the actual state of the connections.</p>
-<h3 id="statusconditions"><code>.status.conditions</code></h3>
+<h3 id="statusconditions"><code>.status.conditions</code><a class="headerlink" href="#statusconditions" title="Permanent link">&para;</a></h3>
 <p>The Operator reports the current state of the LINSTOR Node Connection through a set of conditions. Conditions are
 identified by their <code>type</code>.</p>
 <table>
diff --git a/v2.7.1/reference/linstorsatellite/index.html b/v2.7.1/reference/linstorsatellite/index.html
index 51a1a7e..98f02ec 100644
--- a/v2.7.1/reference/linstorsatellite/index.html
+++ b/v2.7.1/reference/linstorsatellite/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="LinstorSatellite - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstorsatellite.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="LinstorSatellite - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstorsatellite.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1346,8 +1346,6 @@
       
         
       
-        
-      
     
     
       
@@ -1365,7 +1363,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1395,31 +1393,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1441,35 +1422,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1490,7 +1481,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1511,7 +1502,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1532,7 +1523,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1907,15 +1898,21 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
+    <nav class="md-nav" aria-label=".status">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
   <a href="#statusconditions" class="md-nav__link">
     <span class="md-ellipsis">
       .status.conditions
     </span>
   </a>
   
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
     </ul>
@@ -2056,15 +2053,21 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
+    <nav class="md-nav" aria-label=".status">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
   <a href="#statusconditions" class="md-nav__link">
     <span class="md-ellipsis">
       .status.conditions
     </span>
   </a>
   
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
     </ul>
@@ -2085,33 +2088,33 @@
   
 
 
-<h1 id="linstorsatellite"><code>LinstorSatellite</code></h1>
+<h1 id="linstorsatellite"><code>LinstorSatellite</code><a class="headerlink" href="#linstorsatellite" title="Permanent link">&para;</a></h1>
 <p>This resource controls the state of a LINSTOR® satellite.</p>
 <p><strong>NOTE:</strong> This resource is not intended to be changed directly, instead it is created by the Piraeus Operator
 by merging all matching <a href="../linstorsatelliteconfiguration/"><code>LinstorSatelliteConfiguration</code></a> resources.</p>
-<h2 id="spec"><code>.spec</code></h2>
+<h2 id="spec"><code>.spec</code><a class="headerlink" href="#spec" title="Permanent link">&para;</a></h2>
 <p>Holds the desired state the satellite.</p>
-<h3 id="specrepository"><code>.spec.repository</code></h3>
+<h3 id="specrepository"><code>.spec.repository</code><a class="headerlink" href="#specrepository" title="Permanent link">&para;</a></h3>
 <p>Holds the default image registry to use for all Piraeus images. Inherited from
 <a href="../linstorcluster/#specrepository"><code>LinstorCluster</code></a>.</p>
 <p>If empty (the default), the operator will use <code>quay.io/piraeusdatastore</code>.</p>
-<h3 id="specclusterref"><code>.spec.clusterRef</code></h3>
+<h3 id="specclusterref"><code>.spec.clusterRef</code><a class="headerlink" href="#specclusterref" title="Permanent link">&para;</a></h3>
 <p>Holds a reference to the <a href="../linstorcluster/"><code>LinstorCluster</code></a> that controls this satellite.</p>
-<h3 id="specstoragepools"><code>.spec.storagePools</code></h3>
+<h3 id="specstoragepools"><code>.spec.storagePools</code><a class="headerlink" href="#specstoragepools" title="Permanent link">&para;</a></h3>
 <p>Holds the storage pools to configure on the node. Inherited from matching
 <a href="../linstorsatelliteconfiguration/#specstoragepools"><code>LinstorSatelliteConfiguration</code></a> resources.</p>
-<h3 id="specproperties"><code>.spec.properties</code></h3>
+<h3 id="specproperties"><code>.spec.properties</code><a class="headerlink" href="#specproperties" title="Permanent link">&para;</a></h3>
 <p>Holds the properties which should be set on the node level. Inherited from matching
 <a href="../linstorsatelliteconfiguration/#specproperties"><code>LinstorSatelliteConfiguration</code></a> resources.</p>
-<h3 id="specinternaltls"><code>.spec.internalTLS</code></h3>
+<h3 id="specinternaltls"><code>.spec.internalTLS</code><a class="headerlink" href="#specinternaltls" title="Permanent link">&para;</a></h3>
 <p>Configures a TLS secret used by the LINSTOR Satellite. Inherited from matching
 <a href="../linstorsatelliteconfiguration/#specproperties"><code>LinstorSatelliteConfiguration</code></a> resources.</p>
-<h3 id="specpatches"><code>.spec.patches</code></h3>
+<h3 id="specpatches"><code>.spec.patches</code><a class="headerlink" href="#specpatches" title="Permanent link">&para;</a></h3>
 <p>Holds patches to apply to the Kubernetes resources. Inherited from matching
 <a href="../linstorsatelliteconfiguration/#specpatches"><code>LinstorSatelliteConfiguration</code></a> resources.</p>
-<h2 id="status"><code>.status</code></h2>
+<h2 id="status"><code>.status</code><a class="headerlink" href="#status" title="Permanent link">&para;</a></h2>
 <p>Reports the actual state of the satellite.</p>
-<h2 id="statusconditions"><code>.status.conditions</code></h2>
+<h3 id="statusconditions"><code>.status.conditions</code><a class="headerlink" href="#statusconditions" title="Permanent link">&para;</a></h3>
 <p>The Operator reports the current state of the LINSTOR Satellite through a set of conditions. Conditions are
 identified by their <code>type</code>.</p>
 <table>
diff --git a/v2.7.1/reference/linstorsatelliteconfiguration/index.html b/v2.7.1/reference/linstorsatelliteconfiguration/index.html
index 6d6a485..9da3e01 100644
--- a/v2.7.1/reference/linstorsatelliteconfiguration/index.html
+++ b/v2.7.1/reference/linstorsatelliteconfiguration/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="LinstorSatelliteConfiguration - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstorsatelliteconfiguration.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="LinstorSatelliteConfiguration - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/reference/linstorsatelliteconfiguration.png" >
       
@@ -325,7 +325,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1346,8 +1346,6 @@
       
         
       
-        
-      
     
     
       
@@ -1365,7 +1363,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1395,31 +1393,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1441,35 +1422,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1490,7 +1481,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1511,7 +1502,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1532,7 +1523,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1806,21 +1797,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeSelector">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1830,21 +1806,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeAffinity">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_1" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1854,21 +1815,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.properties">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_2" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1878,21 +1824,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.storagePools">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_3" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1902,30 +1833,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.internalTLS">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_4" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_5" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1935,21 +1842,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.ipFamilies">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_6" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1959,21 +1851,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.podTemplate">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_7" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -1983,30 +1860,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.patches">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#warning" class="md-nav__link">
-    <span class="md-ellipsis">
-      Warning
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_8" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
       </ul>
@@ -2021,15 +1874,21 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
+    <nav class="md-nav" aria-label=".status">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
   <a href="#statusconditions" class="md-nav__link">
     <span class="md-ellipsis">
       .status.conditions
     </span>
   </a>
   
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
     </ul>
@@ -2153,21 +2012,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeSelector">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2177,21 +2021,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.nodeAffinity">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_1" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2201,21 +2030,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.properties">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_2" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2225,21 +2039,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.storagePools">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_3" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2249,30 +2048,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.internalTLS">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_4" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_5" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2282,21 +2057,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.ipFamilies">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_6" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2306,21 +2066,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.podTemplate">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#example_7" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
           <li class="md-nav__item">
@@ -2330,30 +2075,6 @@
     </span>
   </a>
   
-    <nav class="md-nav" aria-label=".spec.patches">
-      <ul class="md-nav__list">
-        
-          <li class="md-nav__item">
-  <a href="#warning" class="md-nav__link">
-    <span class="md-ellipsis">
-      Warning
-    </span>
-  </a>
-  
-</li>
-        
-          <li class="md-nav__item">
-  <a href="#example_8" class="md-nav__link">
-    <span class="md-ellipsis">
-      Example
-    </span>
-  </a>
-  
-</li>
-        
-      </ul>
-    </nav>
-  
 </li>
         
       </ul>
@@ -2368,15 +2089,21 @@
     </span>
   </a>
   
-</li>
-      
-        <li class="md-nav__item">
+    <nav class="md-nav" aria-label=".status">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
   <a href="#statusconditions" class="md-nav__link">
     <span class="md-ellipsis">
       .status.conditions
     </span>
   </a>
   
+</li>
+        
+      </ul>
+    </nav>
+  
 </li>
       
     </ul>
@@ -2397,13 +2124,13 @@
   
 
 
-<h1 id="linstorsatelliteconfiguration"><code>LinstorSatelliteConfiguration</code></h1>
+<h1 id="linstorsatelliteconfiguration"><code>LinstorSatelliteConfiguration</code><a class="headerlink" href="#linstorsatelliteconfiguration" title="Permanent link">&para;</a></h1>
 <p>This resource controls the state of one or more LINSTOR® satellites.</p>
-<h2 id="spec"><code>.spec</code></h2>
+<h2 id="spec"><code>.spec</code><a class="headerlink" href="#spec" title="Permanent link">&para;</a></h2>
 <p>Configures the desired state of satellites.</p>
-<h3 id="specnodeselector"><code>.spec.nodeSelector</code></h3>
+<h3 id="specnodeselector"><code>.spec.nodeSelector</code><a class="headerlink" href="#specnodeselector" title="Permanent link">&para;</a></h3>
 <p>Selects which nodes the LinstorSatelliteConfiguration should apply to. If empty, the configuration applies to all nodes.</p>
-<h4 id="example">Example</h4>
+<h4 id="example">Example<a class="headerlink" href="#example" title="Permanent link">&para;</a></h4>
 <p>This example sets the <code>AutoplaceTarget</code> property to <code>no</code> on all nodes labelled <code>piraeus.io/autoplace: "no"</code>.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorSatelliteConfiguration</span>
@@ -2416,11 +2143,11 @@ <h4 id="example">Example</h4>
 <span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">AutoplaceTarget</span>
 <span class="w">      </span><span class="nt">value</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;no&quot;</span>
 </code></pre></div>
-<h3 id="specnodeaffinity"><code>.spec.nodeAffinity</code></h3>
+<h3 id="specnodeaffinity"><code>.spec.nodeAffinity</code><a class="headerlink" href="#specnodeaffinity" title="Permanent link">&para;</a></h3>
 <p>Selects which nodes the LinstorSatelliteConfiguration should apply to. If empty, the configuration applies to all nodes.</p>
 <p>When this is used together with <code>.spec.nodeSelector</code>, both need to match in order for the configuration to apply to a
 node.</p>
-<h4 id="example_1">Example</h4>
+<h4 id="example_1">Example<a class="headerlink" href="#example_1" title="Permanent link">&para;</a></h4>
 <p>This example sets the <code>AutoplaceTarget</code> property to <code>no</code> on all non-worker nodes:</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorSatelliteConfiguration</span>
@@ -2436,7 +2163,7 @@ <h4 id="example_1">Example</h4>
 <span class="w">    </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">AutoplaceTarget</span>
 <span class="w">      </span><span class="nt">value</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;no&quot;</span>
 </code></pre></div>
-<h3 id="specproperties"><code>.spec.properties</code></h3>
+<h3 id="specproperties"><code>.spec.properties</code><a class="headerlink" href="#specproperties" title="Permanent link">&para;</a></h3>
 <p>Sets the given properties on the LINSTOR Satellite level.</p>
 <p>The property value can either be set directly using <code>value</code>, inherited from the Kubernetes Node's metadata using
 <code>valueFrom</code>, or <em>expanded</em> from Kubernetes Node's metadata using <code>expandFrom</code>. Metadata fields are specified using the
@@ -2456,7 +2183,7 @@ <h3 id="specproperties"><code>.spec.properties</code></h3>
   is joined using the optional <code>delimiter</code> value.</p>
 <p>In addition, setting <code>optional</code> to true means the property is only applied if the value is not empty. This is useful
 in case the property value should be inherited from the node's metadata</p>
-<h4 id="example_2">Example</h4>
+<h4 id="example_2">Example<a class="headerlink" href="#example_2" title="Permanent link">&para;</a></h4>
 <p>This examples sets the following Properties on every satellite:
 * <code>PrefNic</code> (the preferred network interface) is always set to <code>default-ipv6</code>
 * <code>Aux/example-property</code> (an auxiliary property, unused by LINSTOR itself) takes the value from the <code>piraeus.io/example</code>
@@ -2495,7 +2222,7 @@ <h4 id="example_2">Example</h4>
 <span class="w">        </span><span class="nt">valueTemplate</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;$1&quot;</span>
 <span class="w">        </span><span class="nt">delimiter</span><span class="p">:</span><span class="w"> </span><span class="s">&quot;,&quot;</span>
 </code></pre></div>
-<h3 id="specstoragepools"><code>.spec.storagePools</code></h3>
+<h3 id="specstoragepools"><code>.spec.storagePools</code><a class="headerlink" href="#specstoragepools" title="Permanent link">&para;</a></h3>
 <p>Configures LINSTOR Storage Pools.</p>
 <p>Every Storage Pool needs at least a <code>name</code>, and a type. Types are specified by setting a (potentially empty) value on
 the matching key. Available types are:</p>
@@ -2518,7 +2245,7 @@ <h3 id="specstoragepools"><code>.spec.storagePools</code></h3>
 of raw block devices, which LINSTOR will prepare as the chosen backing pool.</p>
 <p>All storage pools also can also be configured with <code>properties</code>. Properties are set on the Storage Pool level. The
 configuration values have the same form as <a href="#specproperties">Satellite Properties</a>.</p>
-<h4 id="example_3">Example</h4>
+<h4 id="example_3">Example<a class="headerlink" href="#example_3" title="Permanent link">&para;</a></h4>
 <p>This example configures these LINSTOR Storage Pools on all satellites:
 * A LVM Pool named <code>vg1</code>. It will use the VG <code>vg1</code>, which needs to exist on the nodes already.
 * A LVM Thin Pool named <code>vg1-thin</code>. It will use the thin pool <code>vg1/thin</code>, which also needs to exist on the nodes.
@@ -2567,7 +2294,7 @@ <h4 id="example_3">Example</h4>
 <span class="w">        </span><span class="nt">hostDevices</span><span class="p">:</span>
 <span class="w">        </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">/dev/sdd</span>
 </code></pre></div>
-<h3 id="specinternaltls"><code>.spec.internalTLS</code></h3>
+<h3 id="specinternaltls"><code>.spec.internalTLS</code><a class="headerlink" href="#specinternaltls" title="Permanent link">&para;</a></h3>
 <p>Configures a TLS secret used by the LINSTOR Satellites to:
 * Validate the certificate of the LINSTOR Controller, that is the Controller must have certificates signed by <code>ca.crt</code>.
 * Provide a server certificate for authentication by the LINSTOR Controller, that is <code>tls.key</code> and <code>tls.crt</code> must be accepted by the Controller.</p>
@@ -2576,7 +2303,7 @@ <h3 id="specinternaltls"><code>.spec.internalTLS</code></h3>
 name of the Kubernetes Node.</p>
 <p>Optional, a reference to a <a href="https://cert-manager.io/docs/concepts/issuer/">cert-manager <code>Issuer</code></a> can be provided
 to let the operator create the required secret.</p>
-<h4 id="example_4">Example</h4>
+<h4 id="example_4">Example<a class="headerlink" href="#example_4" title="Permanent link">&para;</a></h4>
 <p>This example creates a manually provisioned TLS secret and references it in the LinstorSatelliteConfiguration, setting
 it for all nodes.</p>
 <div class="highlight"><pre><span></span><code><span class="nn">---</span>
@@ -2598,7 +2325,7 @@ <h4 id="example_4">Example</h4>
 <span class="w">  </span><span class="nt">internalTLS</span><span class="p">:</span>
 <span class="w">    </span><span class="nt">secretName</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">my-node-tls</span>
 </code></pre></div>
-<h4 id="example_5">Example</h4>
+<h4 id="example_5">Example<a class="headerlink" href="#example_5" title="Permanent link">&para;</a></h4>
 <p>This example sets up automatic creation of the LINSTOR Satellite TLS secrets using a
 cert-manager issuer named <code>piraeus-root</code>.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
@@ -2611,14 +2338,14 @@ <h4 id="example_5">Example</h4>
 <span class="w">      </span><span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">Issuer</span>
 <span class="w">      </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus-root</span>
 </code></pre></div>
-<h3 id="specipfamilies"><code>.spec.ipFamilies</code></h3>
+<h3 id="specipfamilies"><code>.spec.ipFamilies</code><a class="headerlink" href="#specipfamilies" title="Permanent link">&para;</a></h3>
 <p>Configures the IP Family (IPv4 or IPv6) to use to connect to the LINSTOR Satellite.</p>
 <p>If unset, the LINSTOR Controller will attempt to reach the LINSTOR Satellite via all recognized addresses in the
 Satellite Pods' Status.
 If set, the LINSTOR Controller will only attempt to reach the LINSTOR Satellite via all addresses matching the listed
 IP Families.</p>
 <p>Valid values are <code>IPv4</code> and <code>IPv6</code>.</p>
-<h4 id="example_6">Example</h4>
+<h4 id="example_6">Example<a class="headerlink" href="#example_6" title="Permanent link">&para;</a></h4>
 <p>This example configures the LINSTOR Controller to only use IPv4, even in a dual stack cluster.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorSatelliteConfiguration</span>
@@ -2628,11 +2355,11 @@ <h4 id="example_6">Example</h4>
 <span class="w">  </span><span class="nt">ipFamilies</span><span class="p">:</span>
 <span class="w">  </span><span class="p p-Indicator">-</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">IPv4</span>
 </code></pre></div>
-<h3 id="specpodtemplate"><code>.spec.podTemplate</code></h3>
+<h3 id="specpodtemplate"><code>.spec.podTemplate</code><a class="headerlink" href="#specpodtemplate" title="Permanent link">&para;</a></h3>
 <p>Configures the Pod used to run the LINSTOR Satellite.</p>
 <p>The template is applied as a patch (see <a href="#specpatches"><code>.spec.patches</code></a>) to the default resources, so it can be
 "sparse".</p>
-<h4 id="example_7">Example</h4>
+<h4 id="example_7">Example<a class="headerlink" href="#example_7" title="Permanent link">&para;</a></h4>
 <p>This example configures a resource request of <code>cpu: 100m</code> on the satellite, and also enables host networking.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorSatelliteConfiguration</span>
@@ -2648,15 +2375,15 @@ <h4 id="example_7">Example</h4>
 <span class="w">            </span><span class="nt">requests</span><span class="p">:</span>
 <span class="w">              </span><span class="nt">cpu</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">100m</span>
 </code></pre></div>
-<h3 id="specpatches"><code>.spec.patches</code></h3>
+<h3 id="specpatches"><code>.spec.patches</code><a class="headerlink" href="#specpatches" title="Permanent link">&para;</a></h3>
 <p>The given patches will be applied to all resources controlled by the operator. The patches are
 forwarded to <code>kustomize</code> internally, and take the <a href="https://kubectl.docs.kubernetes.io/references/kustomize/kustomization/patches/">same format</a>.</p>
 <p>The unpatched resources are available in the <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v2/pkg/resources/satellite">subdirectories of the <code>pkg/resources/satellite</code> directory</a>.</p>
-<h4 id="warning">Warning</h4>
+<h4 id="warning">Warning<a class="headerlink" href="#warning" title="Permanent link">&para;</a></h4>
 <p>No checks are run on the result of user-supplied patches: the resources are applied
 as-is. Patching some fundamental aspect, such as removing a specific volume from a
 container may lead to a degraded cluster.</p>
-<h4 id="example_8">Example</h4>
+<h4 id="example_8">Example<a class="headerlink" href="#example_8" title="Permanent link">&para;</a></h4>
 <p>This example configures the LINSTOR Satellite to use the "TRACE" log level, creating very verbose output.</p>
 <div class="highlight"><pre><span></span><code><span class="nt">apiVersion</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">piraeus.io/v1</span>
 <span class="nt">kind</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">LinstorSatelliteConfiguration</span>
@@ -2677,9 +2404,9 @@ <h4 id="example_8">Example</h4>
 <span class="w">            </span><span class="no">[logging]</span>
 <span class="w">              </span><span class="no">linstor_level = &quot;TRACE&quot;</span>
 </code></pre></div>
-<h2 id="status"><code>.status</code></h2>
+<h2 id="status"><code>.status</code><a class="headerlink" href="#status" title="Permanent link">&para;</a></h2>
 <p>Reports the actual state of the cluster.</p>
-<h2 id="statusconditions"><code>.status.conditions</code></h2>
+<h3 id="statusconditions"><code>.status.conditions</code><a class="headerlink" href="#statusconditions" title="Permanent link">&para;</a></h3>
 <p>The Operator reports the current state of the Satellite Configuration through a set of conditions. Conditions are
 identified by their <code>type</code>.</p>
 <table>
diff --git a/v2.7.1/search/search_index.json b/v2.7.1/search/search_index.json
index 62bd743..79bf789 100644
--- a/v2.7.1/search/search_index.json
+++ b/v2.7.1/search/search_index.json
@@ -1 +1 @@
-{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Piraeus Datastore","text":"<p>Piraeus is a cloud-native storage system that empowers Kubernetes Local Persistent Volumes with dynamic provisioning, resource management, and high-availability. It deploys and scales out automatically within Kubernetes nodes. With Piraeus, Kubernetes workloads can now consume high performance local storage using the same volume APIs that app developers have become accustomed to.</p> <ul> <li> <p> Tutorials</p> <p>Get started with Piraeus Datastore. These tutorials will guide you through the basics of setting up Piraeus Datastore.</p> <p> Tutorials</p> </li> <li> <p> How-To Guides</p> <p>How-To Guides show you how to configure a specific aspect or achieve a specific task with Piraeus Datastore.</p> <p> How-To Guides</p> </li> <li> <p> Upgrades</p> <p>Read how to upgrade a Piraeus Datastore deployment</p> <p> Upgrades</p> </li> <li> <p> Understanding Piraeus Datastore</p> <p>Read how Piraeus Datastore and it's components work, and why they work the way they do.</p> <p> Understanding Piraeus</p> </li> <li> <p> Reference</p> <p>The API Reference for the Piraeus Operator. Contains documentation of the LINSTOR related resources that the user can modify or observe.</p> <p> Reference</p> </li> </ul>"},{"location":"CHANGELOG/","title":"Changelog","text":"<p>All notable changes to this project will be documented in this file.</p> <p>The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.</p>"},{"location":"CHANGELOG/#unreleased","title":"Unreleased","text":""},{"location":"CHANGELOG/#v271-2024-11-25","title":"v2.7.1 - 2024-11-25","text":""},{"location":"CHANGELOG/#changed","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>DRBD 9.2.12</li> <li>DRBD Reactor 1.6.0</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v270-2024-11-11","title":"v2.7.0 - 2024-11-11","text":""},{"location":"CHANGELOG/#added","title":"Added","text":"<ul> <li>Option to select IP Family to use for LINSTOR control traffic.</li> </ul>"},{"location":"CHANGELOG/#changed_1","title":"Changed","text":"<ul> <li>Reconciliation of a Satellites network interfaces now also deletes unneeded interfaces.</li> <li>Satellites try to detect the LVM configuration on the host, reusing locks and udev rules if available.</li> <li>Updated images:<ul> <li>LINSTOR 1.29.2</li> <li>LINSTOR CSI 1.6.4</li> <li>DRBD Reactor 1.5.0</li> <li>LINSTOR HA Controller 1.2.2</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v260-2024-09-04","title":"v2.6.0 - 2024-09-04","text":""},{"location":"CHANGELOG/#added_1","title":"Added","text":"<ul> <li>Support wildcard patterns when referencing property values from node labels and annotations.</li> </ul>"},{"location":"CHANGELOG/#changed_2","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>LINSTOR 1.29.0</li> <li>DRBD 9.2.11</li> <li>Latest CSI Sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v252-2024-07-17","title":"v2.5.2 - 2024-07-17","text":""},{"location":"CHANGELOG/#added_2","title":"Added","text":"<ul> <li>Option to specify custom CA certificate resources for TLS configuration.</li> <li>Ensure all Certificate resources have <code>dnsNames</code> set.</li> </ul>"},{"location":"CHANGELOG/#changed_3","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>LINSTOR 1.28.0</li> <li>LINSTOR CSI 1.6.3</li> <li>DRBD 9.2.10</li> <li>DRBD Reactor 1.4.1</li> <li>kTLS-utils 0.11</li> <li>Latest CSI sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed","title":"Fixed","text":"<ul> <li>The operator will no longer restart reconciliation on every change to <code>ServiceAccount</code> resources.</li> </ul>"},{"location":"CHANGELOG/#v251-2024-05-02","title":"v2.5.1 - 2024-05-02","text":""},{"location":"CHANGELOG/#added_3","title":"Added","text":"<ul> <li>Default PriorityClasses for all components</li> </ul>"},{"location":"CHANGELOG/#changed_4","title":"Changed","text":"<ul> <li>New DRBD loader detection for:<ul> <li>Ubuntu Noble Numbat (24.04)</li> </ul> </li> <li>Updated images:<ul> <li>LINSTOR 1.27.1</li> <li>LINSTOR CSI 1.6.0</li> <li>DRBD 9.2.9</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v250-2024-04-03","title":"v2.5.0 - 2024-04-03","text":""},{"location":"CHANGELOG/#added_4","title":"Added","text":"<ul> <li>Support for managing ZFS Storage Pools using <code>LinstorSatelliteConfiguration</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_5","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>LINSTOR 1.27.0</li> <li>LINSTOR CSI 1.5.0</li> <li>High Availability Controller 1.2.1</li> <li>Latest CSI sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v241-2024-03-06","title":"v2.4.1 - 2024-03-06","text":""},{"location":"CHANGELOG/#added_5","title":"Added","text":"<ul> <li>New DRBD loader detection for:<ul> <li>Debian 12 (Bookworm)</li> <li>Rocky Linux 8 &amp; 9</li> </ul> </li> <li>Report <code>seLinuxMount</code> capability for the CSI Driver, speeding up volume mounts with SELinux   relabelling enabled.</li> <li>Alerts for offline LINSTOR Controller and Satellites.</li> </ul>"},{"location":"CHANGELOG/#changed_6","title":"Changed","text":"<ul> <li>Use node label instead of pod name for Prometheus alerting descriptions.</li> <li>Updated images:<ul> <li>LINSTOR 1.26.2</li> <li>DRBD 9.2.8</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v240-2024-01-30","title":"v2.4.0 - 2024-01-30","text":""},{"location":"CHANGELOG/#added_6","title":"Added","text":"<ul> <li>Validating Webhook for Piraeus StorageClasses.</li> </ul>"},{"location":"CHANGELOG/#breaking","title":"Breaking","text":"<ul> <li>Use DaemonSet to manage Satellite resources instead of bare Pods. This enables better integration with   common administrative tasks such as node draining. This change should be transparent for users, any patches   applied on the satellite Pods are internally converted to work on the new DaemonSet instead.</li> </ul>"},{"location":"CHANGELOG/#changed_7","title":"Changed","text":"<ul> <li>Change default monitoring address for DRBD Reactor to support systems with IPv6 completely disabled.</li> <li>Updated images:<ul> <li>LINSTOR 1.26.1</li> <li>LINSTOR CSI 1.4.0</li> <li>DRBD 9.2.7</li> <li>High Availability Controller 1.2.0</li> <li>Latest CSI sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v230-2023-12-05","title":"v2.3.0 - 2023-12-05","text":""},{"location":"CHANGELOG/#added_7","title":"Added","text":"<ul> <li>Add a new option <code>.spec.internalTLS.tlsHandshakeDaemon</code> to enable deployment of <code>tlshd</code> alongside the LINSTOR   Satellite.</li> <li>Shortcuts to configure specific components. Components can be disabled by setting <code>enabled: false</code>, and the deployed   workload can be influenced using the <code>podTemplate</code> value. Available components:<ul> <li><code>LinstorCluster.spec.controller</code></li> <li><code>LinstorCluster.spec.csiController</code></li> <li><code>LinstorCluster.spec.csiNode</code></li> <li><code>LinstorCluster.spec.highAvailabilityController</code></li> </ul> </li> <li>Shortcut to modify the pod of a satellite by adding a <code>LinstorSatelliteConfiguration.spec.podTemplate</code>, which is   a shortcut for creating a <code>.spec.patches</code> patch.</li> </ul>"},{"location":"CHANGELOG/#changed_8","title":"Changed","text":"<ul> <li>Fixed service resources relying on default protocol version.</li> <li>Moved NetworkPolicy for DRBD out of default deployed resources.</li> <li>Updated images:<ul> <li>LINSTOR 1.25.1</li> <li>LINSTOR CSI 1.3.0</li> <li>DRBD Reactor 1.4.0</li> <li>Latest CSI sidecars</li> </ul> </li> <li>Add a default toleration for the HA Controller taints to the operator.</li> </ul>"},{"location":"CHANGELOG/#v220-2023-08-31","title":"v2.2.0 - 2023-08-31","text":""},{"location":"CHANGELOG/#added_8","title":"Added","text":"<ul> <li>A new <code>LinstorNodeConnection</code> resource, used to configure the LINSTOR Node Connection feature in a Kubernetes way.</li> <li>Allow image configuration to be customized by adding additional items to the config map. Items using a \"greater\" key   take precedence when referencing the same images.</li> <li>Add image configuration for CSI sidecars.</li> <li>Check kernel module parameters for DRBD on load.</li> <li>Automatically set SELinux labels when loading kernel modules.</li> <li>Allow more complex node selection by adding <code>LinstorCluster.spec.nodeAffinity</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_9","title":"Changed","text":"<ul> <li>Upgrade to operator-sdk 1.29</li> <li>Upgrade to kubebuilder v4 layout</li> <li>Updated images:<ul> <li>LINSTOR 1.24.2</li> <li>LINSTOR CSI 1.2.3</li> <li>DRBD 9.2.5</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#removed","title":"Removed","text":"<ul> <li>Disable operator metrics by default. This removes a dependency on an external container.</li> <li>Dependency on cert-manager for initial deployment.</li> </ul>"},{"location":"CHANGELOG/#fixed_1","title":"Fixed","text":"<ul> <li>A crash caused by insufficient permissions on the LINSTOR Controller.</li> <li>Satellite will now restart if the Pods terminated for unexpected reasons.</li> </ul>"},{"location":"CHANGELOG/#v211-2023-05-24","title":"v2.1.1 - 2023-05-24","text":""},{"location":"CHANGELOG/#added_9","title":"Added","text":"<ul> <li>LINSTOR Controller deployment now runs DB migrations as a separate init container, creating   a backup of current DB state if needed.</li> <li>Apply global rate limit to LINSTOR API, defaulting to 100 qps.</li> </ul>"},{"location":"CHANGELOG/#changed_10","title":"Changed","text":"<ul> <li>Store LINSTOR Satellite logs on the host.</li> <li>Updated images:<ul> <li>LINSTOR 1.23.0</li> <li>LINSTOR CSI 1.1.0</li> <li>DRBD Reactor 1.2.0</li> <li>HA Controller 1.1.4</li> <li>external CSI images upgraded to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_2","title":"Fixed","text":"<ul> <li>Fixed a bug where <code>LinstorSatellite</code> resources would be not be cleaned up when the satellite is already gone.</li> <li>Fixed a bug where the LINSTOR Controller would never report readiness when TLS is enabled.</li> <li>Fixed order in which patches are applied. Always apply user patches last.</li> </ul>"},{"location":"CHANGELOG/#v210-2023-04-24","title":"v2.1.0 - 2023-04-24","text":""},{"location":"CHANGELOG/#added_10","title":"Added","text":"<ul> <li>Ability to skip deploying the LINSTOR Controller by setting <code>LinstorCluster.spec.externalController</code>.</li> <li>Automatically reconcile changed image configuration.</li> </ul>"},{"location":"CHANGELOG/#changed_11","title":"Changed","text":"<ul> <li>Fix an issue where the CSI node driver would use the CSI socket not through the expected path in the container.</li> <li>Updated images:<ul> <li>LINSTOR 1.22.0</li> <li>LINSTOR CSI 1.0.1</li> <li>DRBD 9.2.3</li> <li>DRBD Reactor 1.1.0</li> <li>HA Controller 1.1.3</li> <li>external CSI images upgraded to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v201-2023-03-08","title":"v2.0.1 - 2023-03-08","text":""},{"location":"CHANGELOG/#added_11","title":"Added","text":"<ul> <li><code>drbd-shutdown-guard</code> init-container, installing a systemd unit that runs on shutdown.   It's purpose is to run <code>drbdsetup secondary --force</code> during shutdown, so that systemd can unmount all volumes, even   with <code>suspend-io</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_12","title":"Changed","text":"<ul> <li>Updated LINSTOR CSI to 1.0.0, mounting the <code>/run/mount</code> directory from the host to enable the <code>_netdev</code> mount option.</li> </ul>"},{"location":"CHANGELOG/#fixed_3","title":"Fixed","text":"<ul> <li>HA Controller deployment requires additional rules to run on OpenShift.</li> </ul>"},{"location":"CHANGELOG/#v200-2023-02-23","title":"v2.0.0 - 2023-02-23","text":""},{"location":"CHANGELOG/#breaking_1","title":"Breaking","text":"<ul> <li>Removed existing CRD <code>LinstorController</code>, <code>LinstorSatelliteSet</code> and <code>LinstorCSIDriver</code>.</li> <li>Helm chart deprecated in favor of new <code>kustomize</code> deployment.</li> <li>Helm chart changed to only deploy the Operator. The LinstorCluster resource to create the storage cluster needs to be   created separately.</li> </ul>"},{"location":"CHANGELOG/#added_12","title":"Added","text":"<ul> <li>New CRDs to control storage cluster: <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code>.</li> <li>Tutorials on how to get started.</li> <li>Automatic selection of loader images based on operating system of node.</li> <li>Customization of single nodes or groups of nodes.</li> <li>Possibility to run DRBD replication using the container network.</li> <li>Support for file system backed storage pools</li> <li>Default deployment for HA Controller. Since we switch to defaulting to <code>suspend-io</code> for lost quorum, we should include   a way for Pods to get unstuck.</li> </ul>"},{"location":"CHANGELOG/#v1100-2022-10-18","title":"v1.10.0 - 2022-10-18","text":""},{"location":"CHANGELOG/#added_13","title":"Added","text":"<ul> <li>Can set the variable <code>mountDrbdResourceDirectoriesFromHost</code> in the Helm chart to create hostPath Volumes for DRBD and   LINSTOR configuration directories for the satellite set.</li> </ul>"},{"location":"CHANGELOG/#changed_13","title":"Changed","text":"<ul> <li>Change default bind address for satellite monitoring to use IPv6 anylocal <code>[::]</code>. This will still to work on IPv4   only systems with IPv6 disabled via sysctl.</li> <li>Default images:<ul> <li>LINSTOR 1.20.0</li> <li>DRBD 9.1.11</li> <li>DRBD Reactor 0.9.0</li> <li>external CSI images upgraded to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_4","title":"Fixed","text":"<ul> <li>Comparing IP addresses for registered components uses golang's built-in net.IP type.</li> <li>Restoring satellites after eviction only happens if the node is ready.</li> </ul>"},{"location":"CHANGELOG/#v191-2022-07-27","title":"v1.9.1 - 2022-07-27","text":""},{"location":"CHANGELOG/#fixed_5","title":"Fixed","text":"<ul> <li>ServiceMonitor resources can't be patched, instead we recreate them.</li> </ul>"},{"location":"CHANGELOG/#v190-2022-07-20","title":"v1.9.0 - 2022-07-20","text":""},{"location":"CHANGELOG/#added_14","title":"Added","text":"<ul> <li>Support for custom labels and annotations with added options to <code>values.yaml</code>.</li> <li>Instructions for deploying the affinity controller.</li> </ul>"},{"location":"CHANGELOG/#changed_14","title":"Changed","text":"<ul> <li>Satellite operator now reports basic satellite status even if controller is not reachable</li> <li>Query single satellite devices to receive errors when the satellite is offline instead of assuming   devices are already configured.</li> <li>Disabled the legacy HA Controller deployment by default. It has been replaced a   separate chart.</li> <li>Default images:<ul> <li>LINSTOR 1.19.1</li> <li>LINSTOR CSI 0.20.0</li> <li>DRBD 9.1.8</li> <li>DRBD Reactor 0.8.0</li> <li>external CSI images to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_6","title":"Fixed","text":"<ul> <li><code>last-applied-configuration</code>annotation was never updated, so updating of some fields was not performed correctly.</li> </ul>"},{"location":"CHANGELOG/#v182-2022-05-24","title":"v1.8.2 - 2022-05-24","text":""},{"location":"CHANGELOG/#added_15","title":"Added","text":"<ul> <li>Option to disable creating monitoring resources (Services and ServiceMonitors)</li> <li>Add options <code>csi.controllerSidecars</code>, <code>csi.controllerExtraVolumes</code>, <code>csi.nodeSidecars</code>, <code>csi.nodeExtraVolumes</code>,   <code>operator.controller.sidecars</code>, <code>operator.controller.extraVolumes</code>, <code>operator.satelliteSet.sidecars</code>,   <code>operator.satelliteSet.extraVolumes</code> to allow specifying extra sidecar containers.</li> <li>Add options <code>operator.controller.httpBindAddress</code>, <code>operator.controller.httpsBindAddress</code>,   <code>operator.satelliteSet.monitoringBindAddress</code> to allow specifying bind address.</li> <li>Add example values and doc reference to run piraeus-operator with rbac-proxy.</li> </ul>"},{"location":"CHANGELOG/#changed_15","title":"Changed","text":"<ul> <li>Default images:<ul> <li>LINSTOR 1.18.2</li> <li>LINSTOR CSI 0.19.1</li> <li>DRBD Reactor 0.7.0</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#removed_1","title":"Removed","text":"<ul> <li>Get rid of operator-sdk binary, use native controller-gen instead</li> </ul>"},{"location":"CHANGELOG/#v181-2022-05-12","title":"v1.8.1 - 2022-05-12","text":""},{"location":"CHANGELOG/#changed_16","title":"Changed","text":"<ul> <li>Default images:<ul> <li>LINSTOR 1.18.1</li> <li>LINSTOR CSI 0.19.0</li> <li>DRBD 9.1.7</li> <li>DRBD Reactor 0.6.1</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#added_16","title":"Added","text":"<ul> <li>Upgrades involving k8s databases no long require manually confirming a backup exists using   <code>--set IHaveBackedUpAllMyLinstorResources=true</code>.</li> </ul>"},{"location":"CHANGELOG/#v180-2022-03-15","title":"v1.8.0 - 2022-03-15","text":""},{"location":"CHANGELOG/#added_17","title":"Added","text":"<ul> <li>Allow setting the number of parallel requests created by the CSI sidecars. This limits the load on the LINSTOR   backend, which could easily overload when creating many volumes at once.</li> <li>Unify certificates format for SSL enabled installation, no more java tooling required.</li> <li>Automatic certificates generation using Helm or Cert-manager</li> <li>HA Controller and CSI components now wait for the LINSTOR API to be initialized using InitContainers.</li> </ul>"},{"location":"CHANGELOG/#changed_17","title":"Changed","text":"<ul> <li>Create backups of LINSTOR resource if the \"k8s\" database backend is used and an image change is detected. Backups   are stored in Secret resources as a <code>tar.gz</code>. If the secret would get too big, the backup can be downloaded from   the operator pod.</li> <li>Default images:<ul> <li>LINSTOR 1.18.0</li> <li>LINSTOR CSI 0.18.0</li> <li>DRBD 9.1.6</li> <li>DRBD Reactor 0.5.3</li> <li>LINSTOR HA Controller 0.3.0</li> <li>CSI Attacher v3.4.0</li> <li>CSI Node Driver Registrar v2.4.0</li> <li>CSI Provisioner v3.1.0</li> <li>CSI Snapshotter v5.0.1</li> <li>CSI Resizer v1.4.0</li> <li>Stork v2.8.2</li> </ul> </li> <li>Stork updated to support Kubernetes v1.22+.</li> <li>Satellites no longer have a readiness probe defined. This caused issues in the satellites by repeatedly opening   unexpected connections, especially when using SSL.</li> <li>Only query node devices if a storage pool needs to be created.</li> <li>Use cached storage pool response to avoid causing excessive load on LINSTOR satellites.</li> <li>Protect LINSTOR passphrase from accidental deletion by using a finalizer.</li> </ul>"},{"location":"CHANGELOG/#breaking_2","title":"Breaking","text":"<ul> <li>If you have SSL configured, then the certificates must be regenerated in PEM format.   Learn more in the upgrade guide.</li> </ul>"},{"location":"CHANGELOG/#v171-2022-01-18","title":"v1.7.1 - 2022-01-18","text":""},{"location":"CHANGELOG/#added_18","title":"Added","text":"<ul> <li>Allow the external-provisioner and external-snapshotter access to secrets. This is required to support StorageClass   and SnapshotClass secrets.</li> <li>Instruct external-provisioner to pass PVC name+namespace to the CSI driver, enabling optional support for PVC based   names for LINSTOR volumes.</li> <li>Allow setting the log level of LINSTOR components via CRs. Other components are left using their default log level.   The new default log level is INFO (was DEBUG previously, which was often too verbose).</li> <li>Override the kernel source directory used when compiling DRBD (defaults to /usr/src). See    <code>operator.satelliteSet.kernelModuleInjectionAdditionalSourceDirectory</code></li> <li>etcd-chart: add option to set priorityClassName.</li> </ul>"},{"location":"CHANGELOG/#fixed_7","title":"Fixed","text":"<ul> <li>Use correct secret name when setting up TLS for satellites</li> <li>Correctly configure ServiceMonitor resource if TLS is enabled for LINSTOR Controller.</li> </ul>"},{"location":"CHANGELOG/#v170-2021-12-14","title":"v1.7.0 - 2021-12-14","text":""},{"location":"CHANGELOG/#added_19","title":"Added","text":"<ul> <li><code>pv-hostpath</code>: automatically determine on which nodes PVs should be created if no override is given.</li> <li>Automatically add labels on Kubernetes Nodes to LINSTOR satellites as Auxiliary Properties. This enables using   Kubernetes labels for volume scheduling, for example using <code>replicasOnSame: topology.kubernetes.io/zone</code>.</li> <li>Support LINSTORs <code>k8s</code> backend by adding the necessary RBAC resources and documentation.</li> <li>Automatically create a LINSTOR passphrase when none is configured.</li> <li>Automatic eviction and deletion of offline satellites if the Kubernetes node object was also deleted.</li> </ul>"},{"location":"CHANGELOG/#changed_18","title":"Changed","text":"<ul> <li>Default images:<ul> <li><code>quay.io/piraeusdatastore/piraeus-server:v1.17.0</code></li> <li><code>quay.io/piraeusdatastore/piraeus-csi:v0.17.0</code></li> <li><code>quay.io/piraeusdatastore/drbd9-bionic:v9.1.4</code></li> <li><code>quay.io/piraeusdatastore/drbd-reactor:v0.4.4</code></li> </ul> </li> <li>Recreates or updates to the satellite pods are now applied at once, instead of waiting for a node to complete before   moving to the next.</li> <li>Enable CSI topology by default, allowing better volume scheduling with <code>volumeBindingMode: WaitForFirstConsumer</code>.</li> <li>Disable STORK by default. Instead, we recommend using <code>volumeBindingMode: WaitForFirstConsumer</code> in storage classes.</li> </ul>"},{"location":"CHANGELOG/#v160-2021-09-02","title":"v1.6.0 - 2021-09-02","text":""},{"location":"CHANGELOG/#added_20","title":"Added","text":"<ul> <li>Allow CSI to work with distributions that use a kubelet working directory other than <code>/var/lib/kubelet</code>. See   the <code>csi.kubeletPath</code> option.</li> <li>Enable Storage Capacity Tacking. This enables Kubernetes to base Pod scheduling decisions on remaining storage   capacity. The feature is in beta and enabled by default starting with Kubernetes 1.21.</li> </ul>"},{"location":"CHANGELOG/#changed_19","title":"Changed","text":"<ul> <li> <p>Disable Stork Health Monitoring by default. Stork cannot distinguish between control plane and data plane issues,   which can lead to instances where Stork will migrate a volume that is still mounted on another node, making the   volume effectively unusable.</p> </li> <li> <p>Updated operator to kubernetes v1.21 components.</p> </li> <li> <p>Default images:</p> <ul> <li><code>quay.io/piraeusdatastore/piraeus-server:v1.14.0</code></li> <li><code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.30</code></li> <li><code>quay.io/piraeusdatastore/drbd-reactor:v0.4.3</code></li> <li><code>quay.io/piraeusdatastore/piraeus-ha-controller:v0.2.0</code></li> <li>external CSI images</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#removed_2","title":"Removed","text":"<ul> <li>The cluster-wide snapshot controller is no longer deployed as a dependency of the piraeus-operator chart.   Instead, separate charts are available on artifacthub.io   that deploy the snapshot controller and extra validation for snapshot resources.</li> </ul> <p>The subchart was removed, as it unnecessarily tied updates of the snapshot controller to piraeus and vice versa. With   the tightened validation starting with snapshot CRDs <code>v1</code>, moving the snapshot controller to a proper chart seems   like a good solution.</p>"},{"location":"CHANGELOG/#v151-2021-06-21","title":"v1.5.1 - 2021-06-21","text":""},{"location":"CHANGELOG/#changed_20","title":"Changed","text":"<ul> <li>Default images:<ul> <li>Piraeus Server v1.13.0</li> <li>Piraeus CSI v0.13.1</li> <li>CSI Provisioner v2.1.2</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v150-2021-05-12","title":"v1.5.0 - 2021-05-12","text":""},{"location":"CHANGELOG/#added_21","title":"Added","text":"<ul> <li>All operator-managed workloads apply recommended labels. This requires the recreation of Deployments and DaemonSets   on upgrade. This is automatically handled by the operator, however any customizations applied to the deployments   not managed by the operator will be reverted in the process.</li> <li>Use <code>drbd-reactor</code> to expose Prometheus endpoints on each satellite.</li> <li>Configure <code>ServiceMonitor</code> resources if they are supported by the cluster (i.e. prometheus operator is configured)</li> </ul>"},{"location":"CHANGELOG/#changed_21","title":"Changed","text":"<ul> <li>CSI Nodes no longer use <code>hostNetwork: true</code>. The pods already got the correct hostname via the downwardAPI and do not   talk to DRBD's netlink interface directly.</li> <li>External: CSI snapshotter subchart now packages <code>v1</code> CRDs. Fixes deprecation warnings when installing   the snapshot controller.</li> <li>Default images:<ul> <li>Piraeus Server v1.12.3</li> <li>Piraeus CSI v0.13.0</li> <li>DRBD v9.0.29</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v140-2021-04-07","title":"v1.4.0 - 2021-04-07","text":""},{"location":"CHANGELOG/#added_22","title":"Added","text":"<ul> <li>Additional environment variables and Linstor properties can now be set in the <code>LinstorController</code> CRD.</li> <li>Set node name variable for Controller Pods, enabling k8s-await-election to correctly set up the endpoint for   hairpin mode.</li> </ul>"},{"location":"CHANGELOG/#fixed_8","title":"Fixed","text":"<ul> <li>Update the network address of controller pods if they diverged between Linstor and kubernetes. This can happen after   a node restart, where a pod is recreated with the same name but different IP address.</li> </ul>"},{"location":"CHANGELOG/#v131-2021-01-14","title":"v1.3.1 - 2021-01-14","text":""},{"location":"CHANGELOG/#added_23","title":"Added","text":"<ul> <li>New guide on host preparation here.</li> </ul>"},{"location":"CHANGELOG/#changed_22","title":"Changed","text":"<ul> <li>Default image updated:<ul> <li><code>operator.satelliteSet.kernelModuleInjectionImage</code>: <code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.27</code></li> <li><code>operator.satelliteSet.satelliteImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.1</code></li> <li><code>operator.controller.controllerImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.1</code></li> <li><code>haController.image</code>: <code>quay.io/piraeusdatastore/piraeus-ha-controller:v0.1.3</code></li> <li><code>pv-hostpath</code>: <code>chownerImage</code>: <code>quay.io/centos/centos:8</code></li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v130-2020-12-21","title":"v1.3.0 - 2020-12-21","text":""},{"location":"CHANGELOG/#added_24","title":"Added","text":"<ul> <li>New component: <code>haController</code> will deploy the Piraeus High Availability Controller.   More information is available in   the optional components page</li> <li>Enable strict checking of DRBD parameter to disable usermode helper in container environments.</li> <li>Override the image used in \"chown\" jobs in the <code>pv-hostpath</code> chart by using <code>--set chownerImage=&lt;my-image&gt;</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_23","title":"Changed","text":"<ul> <li>Updated <code>operator-sdk</code> to v0.19.4</li> <li>Set CSI component timeout to 1 minute to reduce the number of retries in the CSI driver</li> <li>Default images updated:<ul> <li><code>operator.controller.controllerImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.0</code></li> <li><code>operator.satelliteSet.satelliteImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.0</code></li> <li><code>operator.satelliteSet.kernelModuleInjectionImage</code>: <code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.26</code></li> <li><code>csi.pluginImage</code>: <code>quay.io/piraeusdatastore/piraeus-csi:v0.11.0</code></li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_9","title":"Fixed","text":"<ul> <li>Fixed Helm warnings when setting \"csi.controllerAffinity\", \"operator.controller.affinity\" and   \"operator.satelliteSet.storagePools\".</li> </ul>"},{"location":"CHANGELOG/#v120-2020-11-18","title":"v1.2.0 - 2020-11-18","text":""},{"location":"CHANGELOG/#added_25","title":"Added","text":"<ul> <li><code>storagePools</code> can now also set up devices similar to <code>automaticStorageType</code>, but with more fine grained control.   See the updated storage guide</li> <li>New Helm options to disable creation of LinstorController and LinstorSatelliteSet resource   <code>operator.controller.enabled</code> and <code>operator.satelliteSet.enabled</code>.</li> <li>New Helm option to override the generated controller endpoint: <code>controllerEndpoint</code></li> <li>Allow overriding the default <code>securityContext</code> on a component basis:<ul> <li><code>etcd.podsecuritycontext</code> sets the securityContext of etcd pods</li> <li><code>stork.podsecuritycontext</code> sets the securityContext of stork plugin and scheduler pods</li> <li><code>csi-snapshotter.podsecuritycontext</code> sets the securityContext of the CSI-Snapshotter pods</li> <li><code>operator.podsecuritycontext</code> sets the securityContext of the operator pods</li> </ul> </li> <li>Example settings for openshift</li> <li>LINSTOR controller runs with additional GID 1000, to ensure write access to log directory</li> </ul>"},{"location":"CHANGELOG/#changed_24","title":"Changed","text":"<ul> <li>Fixed a bug in <code>pv-hostpath</code> where permissions on the created directory are not applied on all nodes.</li> <li>Volumes created by <code>pv-hostpath</code> are now group writable. This makes them easier to integrate with <code>fsGroup</code> settings.</li> <li>Default value for affinity on LINSTOR controller and CSI controller changed. The new default is to distribute the pods   across all available nodes.</li> <li>Default value for tolerations for etcd pods changed. They are now able to run on master nodes.</li> <li>Updates to LinstorController, LinstorSatelliteSet and LinstorCSIDriver are now propagated across all created resources</li> <li>Updated default images:<ul> <li>csi sidecar containers updated (compatible with Kubernetes v1.17+)</li> <li>LINSTOR 1.10.0</li> <li>LINSTOR CSI 0.10.0</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#deprecation","title":"Deprecation","text":"<ul> <li>Using <code>automaticStorageType</code> is deprecated. Use the <code>storagePools</code> values instead.</li> </ul>"},{"location":"CHANGELOG/#v110-2020-10-13","title":"v1.1.0 - 2020-10-13","text":""},{"location":"CHANGELOG/#breaking_3","title":"Breaking","text":"<ul> <li>The LINSTOR controller image given in <code>operator.controller.controllerImage</code> has to have   its entrypoint set to <code>k8s-await-election v0.2.0</code>   or newer. Learn more in the upgrade guide.</li> </ul>"},{"location":"CHANGELOG/#added_26","title":"Added","text":"<ul> <li>LINSTOR controller can be started with multiple replicas. See  <code>operator.controller.replicas</code>.   NOTE: This requires support from the container. You need <code>piraeus-server:v1.8.0</code> or newer.</li> <li>The <code>pv-hostpath</code> helper chart automatically sets up permissions for non-root etcd containers.</li> <li>Disable securityContext enforcement by setting <code>global.setSecurityContext=false</code>.</li> <li>Add cluster roles to work with OpenShift's SCC system.</li> <li>Control volume placement and accessibility by using CSIs Topology feature. Controlled by setting   <code>csi.enableTopology</code>.</li> <li>All pods use a dedicated service account to allow for fine-grained permission control.</li> <li>The new helm section <code>psp.*</code> can automatically configure the ServiceAccount   of all components to use the appropriate PSP roles.</li> </ul>"},{"location":"CHANGELOG/#changed_25","title":"Changed","text":"<ul> <li>Default values:<ul> <li><code>operator.controller.controllerImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.9.0</code></li> <li><code>operator.satelliteSet.satelliteImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.9.0</code></li> <li><code>operator.satelliteSet.kernelModuleInjectionImage</code>: <code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.25</code></li> <li><code>stork.storkImage</code>: <code>docker.io/openstorage/stork:2.5.0</code></li> </ul> </li> <li>linstor-controller no longer starts in a privileged container.</li> </ul>"},{"location":"CHANGELOG/#removed_3","title":"Removed","text":"<ul> <li>legacy CRDs (LinstorControllerSet, LinstorNodeSet) have been removed.</li> <li><code>v1alpha</code> CRD versions have been removed.</li> <li>default pull secret <code>drbdiocred</code> removed. To keep using it, use <code>--set drbdRepoCred=drbdiocred</code>.</li> </ul>"},{"location":"CHANGELOG/#v100-2020-08-06","title":"v1.0.0 - 2020-08-06","text":""},{"location":"CHANGELOG/#added_27","title":"Added","text":"<ul> <li><code>v1</code> of all CRDs</li> <li>Central value for controller image pull policy of all pods. Use <code>--set global.imagePullPolicy=&lt;value&gt;</code> on   helm deployment.</li> <li><code>charts/piraeus/values.cn.yaml</code> a set of helm values for faster image download for CN users.</li> <li>Allow specifying resource requirements for all pods. In helm you can set:<ul> <li><code>etcd.resources</code> for etcd containers</li> <li><code>stork.storkResources</code> for stork plugin resources</li> <li><code>stork.schedulerResources</code> for the kube-scheduler deployed for use with stork</li> <li><code>csi-snapshotter.resources</code> for the cluster snapshotter controller</li> <li><code>csi.resources</code> for all CSI related containers. for brevity, there is only one setting for ALL CSI containers.   They   are all stateless go process which use the same amount of resources.</li> <li><code>operator.resources</code> for operator containers</li> <li><code>operator.controller.resources</code> for LINSTOR controller containers</li> <li><code>operator.satelliteSet.resources</code> for LINSTOR satellite containers</li> <li><code>operator.satelliteSet.kernelModuleInjectionResources</code> for kernel module injector/builder containers</li> </ul> </li> <li>Components deployed by the operator can now run with multiple replicas. Components   elect a leader, that will take on the actual work as long as it is active. Should one   pod go down, another replica will take over.   Currently these components support multiple replicas:<ul> <li><code>etcd</code> =&gt; set <code>etcd.replicas</code> to the desired count</li> <li><code>stork</code> =&gt; set <code>stork.replicas</code> to the desired count for stork scheduler and controller</li> <li><code>snapshot-controller</code> =&gt; set <code>csi-snapshotter.replicas</code> to the desired count for cluster-wide CSI snapshot   controller</li> <li><code>csi-controller</code> =&gt; set <code>csi.controllerReplicas</code> to the desired count for the linstor CSI controller</li> <li><code>operator</code> =&gt; set <code>operator.replicas</code> to have multiple replicas of the operator running</li> </ul> </li> <li>Reference docs for all helm settings. Link</li> <li><code>stork.schedulerTag</code> can override the automatically chosen tag for the <code>kube-scheduler</code> image.   Previously, the tag always matched the kubernetes release.</li> </ul>"},{"location":"CHANGELOG/#changed_26","title":"Changed","text":"<ul> <li>Renamed <code>LinstorNodeSet</code> to <code>LinstorSatelliteSet</code>. This brings the operator in line with other LINSTOR resources.   Existing <code>LinstorNodeSet</code> resources will automatically be migrated to <code>LinstorSatelliteSet</code>.</li> <li>Renamed <code>LinstorControllerSet</code> to <code>LinstorController</code>. The old name implied the existence of multiple (separate)   controllers. Existing <code>LinstorControllerSet</code> resources will automatically be migrated to <code>LinstorController</code>.</li> <li>Helm values renamed to align with new CRD names:<ul> <li><code>operator.controllerSet</code> to <code>operator.controller</code></li> <li><code>operator.nodeSet</code> to <code>operator.satelliteSet</code></li> </ul> </li> <li> <p>Node scheduling no longer relies on <code>linstor.linbit.com/piraeus-node</code> labels. Instead, all CRDs support   setting pod affinity and tolerations.   In detail:</p> <ul> <li><code>linstorcsidrivers</code> gained 4 new resource keys, with no change in default behaviour:<ul> <li><code>nodeAffinity</code> affinity passed to the csi nodes</li> <li><code>nodeTolerations</code> tolerations passed to the csi nodes</li> <li><code>controllerAffinity</code> affinity passed to the csi controller</li> <li><code>controllerTolerations</code> tolerations passed to the csi controller</li> </ul> </li> <li><code>linstorcontrollerset</code> gained 2 new resource keys, with no change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> <li><code>linstornodeset</code> gained 2 new resource keys, with change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> </ul> </li> <li> <p>Controller is now a Deployment instead of StatefulSet.</p> </li> <li>Renamed <code>kernelModImage</code> to <code>kernelModuleInjectionImage</code></li> <li>Renamed <code>drbdKernelModuleInjectionMode</code> to <code>KernelModuleInjectionMode</code></li> </ul>"},{"location":"CHANGELOG/#v050-2020-06-29","title":"v0.5.0 - 2020-06-29","text":""},{"location":"CHANGELOG/#added_28","title":"Added","text":"<ul> <li>Support volume resizing with newer CSI versions.</li> <li>A new Helm chart <code>csi-snapshotter</code> that deploys extra components needed for volume snapshots.</li> <li> <p>Add new kmod injection mode <code>DepsOnly</code>. Will try load kmods for LINSTOR layers from the host. Deprecates <code>None</code>.</p> </li> <li> <p>Automatic deployment of Stork scheduler configured for LINSTOR.</p> </li> </ul>"},{"location":"CHANGELOG/#removed_4","title":"Removed","text":""},{"location":"CHANGELOG/#changed_27","title":"Changed","text":"<ul> <li>Replaced <code>bitnami/etcd</code> dependency with vendored custom version   Some important keys for the <code>etcd</code> helm chart have changed:<ul> <li><code>statefulset.replicaCount</code> -&gt; <code>replicas</code></li> <li><code>persistence.enabled</code> -&gt; <code>persistentVolume.enabled</code></li> <li><code>persistence.size</code> -&gt; <code>persistentVolume.storage</code></li> <li><code>\u00e0uth.rbac</code> was removed: use tls certificates</li> <li><code>auth.peer.useAutoTLS</code> was removed</li> <li><code>envVarsConfigMap</code> was removed</li> <li>When using etcd with TLS enabled:<ul> <li>For peer communication, peers need valid certificates for <code>*.&lt;release-name&gt;-etcd</code> (was   <code>.&lt;release-name&gt;&gt;-etcd-headless.&lt;namespace&gt;.svc.cluster.local</code>)</li> <li>For client communication, servers need valid certificates for <code>*.&lt;release-name&gt;-etcd</code>  (was   <code>.&lt;release-name&gt;&gt;-etcd.&lt;namespace&gt;.svc.cluster.local</code>)</li> </ul> </li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v041-2020-06-10","title":"v0.4.1 - 2020-06-10","text":""},{"location":"CHANGELOG/#added_29","title":"Added","text":"<ul> <li>Automatic storage pool creation via <code>automaticStorageType</code> on <code>LinstorNodeSet</code>. If this option is set, LINSTOR   will create a storage pool based on all available devices on a node.</li> </ul>"},{"location":"CHANGELOG/#changed_28","title":"Changed","text":"<ul> <li>Moved storage documentation to the storage guide</li> <li>Helm: update default images</li> </ul>"},{"location":"CHANGELOG/#v040-2020-06-05","title":"v0.4.0 - 2020-06-05","text":""},{"location":"CHANGELOG/#added_30","title":"Added","text":"<ul> <li>Secured database connection for Linstor: When using the <code>etcd</code> connector, you can specify a secret containing a CA   certificate to switch from HTTP to HTTPS communication.</li> <li>Secured connection between Linstor components: You can specify TLS keys to secure the communication between   controller and satellite</li> <li>Secure storage with LUKS: You can specify the master passphrase used by Linstor when creating encrypted volumes   when installing via Helm.</li> <li>Authentication with etcd using TLS client certificates.</li> <li>Secured connection between linstor-client and controller (HTTPS). More in   the security guide</li> <li>Linstor controller endpoint can now be customized for all resources. If not specified, the old default values will be   filled in.</li> </ul>"},{"location":"CHANGELOG/#removed_5","title":"Removed","text":"<ul> <li>NodeSet service (<code>piraeus-op-ns</code>) was replaced by the ControllerSet service (<code>piraeus-op-cs</code>) everywhere</li> </ul>"},{"location":"CHANGELOG/#changed_29","title":"Changed","text":"<ul> <li>CSI storage driver setup: move setup from helm to go operator. This is mostly an internal change.   These changes may be of note if you used a non-default CSI configuration:<ul> <li>helm value <code>csi.image</code> was renamed to <code>csi.pluginImage</code></li> <li>CSI deployment can be controlled by a new resource <code>linstorcsidrivers.piraeus.linbit.com</code></li> </ul> </li> <li>PriorityClasses are not automatically created. When not specified, the priority class is:<ul> <li>\"system-node-critical\", if deployed in \"kube-system\" namespace</li> <li>default PriorityClass in other namespaces</li> </ul> </li> <li>RBAC rules for CSI: creation moved to deployment step (Helm/OLM). ServiceAccounts should be specified in CSI resource.   If no ServiceAccounts are named, the implicitly created accounts from previous deployments will be used.</li> <li>Helm: update default images</li> </ul>"},{"location":"CHANGELOG/#v030-2020-05-08","title":"v0.3.0 - 2020-05-08","text":""},{"location":"CHANGELOG/#changed_30","title":"Changed","text":"<ul> <li>Use single values for images in CRDs instead of specifying the version   separately</li> <li>Helm: Use single values for images instead of specifying repo, name and   version separately</li> <li>Helm: Replace fixed storage pool configuration with list</li> <li>Helm: Do not create any storage pools by default</li> <li>Helm: Replace <code>operator.nodeSet.spec</code> and <code>operator.controllerSet.spec</code> by   just <code>operator.nodeSet</code> and <code>operator.controllerSet</code>.</li> </ul>"},{"location":"CHANGELOG/#v022-2020-04-24","title":"v0.2.2 - 2020-04-24","text":""},{"location":"CHANGELOG/#changed_31","title":"Changed","text":"<ul> <li>Fix reporting of errors in LinstorControllerSet status</li> </ul>"},{"location":"CHANGELOG/#v021-2020-04-14","title":"v0.2.1 - 2020-04-14","text":""},{"location":"CHANGELOG/#changed_32","title":"Changed","text":"<ul> <li>Helm: Update LINSTOR server dependencies to fix startup problems</li> </ul>"},{"location":"CHANGELOG/#v020-2020-04-10","title":"v0.2.0 - 2020-04-10","text":""},{"location":"CHANGELOG/#added_31","title":"Added","text":"<ul> <li>Helm: Allow an existing database to be used instead of always setting up   a dedicated etcd instance</li> </ul>"},{"location":"CHANGELOG/#changed_33","title":"Changed","text":"<ul> <li>Rename <code>etcdURL</code> parameter of LinstorControllerSet to <code>dbConnectionURL</code> to   reflect the fact that it can be used for any database type</li> <li>Upgrade to operator-sdk v0.16.0</li> <li>Helm: Create multiple volumes with a single <code>pv-hostchart</code> installation</li> <li>Helm: Update dependencies</li> </ul>"},{"location":"CHANGELOG/#v014-2020-03-05","title":"v0.1.4 - 2020-03-05","text":""},{"location":"CHANGELOG/#added_32","title":"Added","text":"<ul> <li>Helm: Add support for <code>hostPath</code> <code>PersistentVolume</code> persistence of etcd</li> </ul>"},{"location":"CHANGELOG/#removed_6","title":"Removed","text":"<ul> <li>Helm: Remove vendored etcd chart from repository</li> </ul>"},{"location":"CHANGELOG/#changed_34","title":"Changed","text":"<ul> <li>Rename CRDs from Piraeus to Linstor</li> <li>Make priority classes configurable</li> <li>Fix LINSTOR Controller/Satellite arguments</li> <li>Helm: Make etcd persistent by default</li> <li>Helm: Fix deployment of permissions objects into a non-default namespace</li> <li>Helm: Set default etcd size to 1Gi</li> <li>Helm: Update dependent image versions</li> <li>Docker: Change base image to Debian Buster</li> </ul>"},{"location":"CHANGELOG/#v013-2020-02-24","title":"[v0.1.3] - 2020-02-24","text":""},{"location":"CHANGELOG/#added_33","title":"Added","text":"<ul> <li>Support for kernel module injection based on shipped modules - necessary for   CoreOS support.</li> </ul>"},{"location":"CHANGELOG/#v0121-2020-02-21","title":"[v0.1.2.1] - 2020-02-21","text":""},{"location":"CHANGELOG/#added_34","title":"Added","text":"<ul> <li>/charts contains Helm v3 chart for this operator</li> </ul>"},{"location":"CHANGELOG/#changed_35","title":"Changed","text":"<ul> <li>CRDs contain additional Spec parameters that allow customizing image repo and   tag/version of the image.</li> <li>Another Spec parameter 'drbdRepoCred' can specify the name of the k8s secret   used to access the container images.</li> <li>LINSTOR Controller image now contains the LINSTOR client, away from the   Satellite images as it was previously the case. Hence, the readiness probe   is changed to use <code>curl</code> instead of <code>linstor</code> client command.</li> </ul>"},{"location":"CHANGELOG/#v010-2020-01-27","title":"[v0.1.0] - 2020-01-27","text":""},{"location":"CHANGELOG/#added_35","title":"Added","text":"<ul> <li>examples/operator-intra.yaml file to bundle all the rbac, crds, etc to run the   operator</li> <li>EtcdURL field to controllersetcontroller spec. default: etcd-piraeus:2379</li> <li>Host networking on the LINSTOR Satellite pods with DNSClusterFirstWithHostNet   DNS policy</li> <li>NodeSet service for the Satellite pods that also point to the Controller   service for LINSTOR discovery</li> </ul>"},{"location":"CHANGELOG/#removed_7","title":"Removed","text":"<ul> <li><code>ControllerEndpoint</code> and <code>DefaultController</code> from the PiraeusNodeSet spec</li> </ul>"},{"location":"CHANGELOG/#changed_36","title":"Changed","text":"<ul> <li>Controller persistence is now handled by etcd. There must be a reachable and   operable etcd cluster for this operator to work.</li> <li>Networking is now handled by a kubernetes service with the same name   as the ControllerSet. The NodeSet must have the same name as the ControllerSet   for networking to work properly.</li> <li>Opt-in node label for nodes is now <code>linstor.linbit.com/piraeus-node=true</code></li> <li>Remove requirement for <code>kube-system</code> namespace</li> <li>Naming convention for NodeSet and ControllerSet Pods</li> <li>Updated ports for LINSTOR access on NodeSet and ControllerSet pods</li> <li>Updated framework to work with Operator Framework 0.13.0</li> <li>API Versions on PriorityClass, DaemonSet, StatefulSet, and CRD kinds to reflect   K8s 1.16.0 release</li> </ul>"},{"location":"CHANGELOG/#v001-2019-07-19","title":"v0.0.1 - 2019-07-19","text":""},{"location":"CHANGELOG/#added_36","title":"Added","text":"<ul> <li>Initial public version with docs</li> </ul>"},{"location":"explanation/","title":"Understanding Piraeus Datastore","text":"<p>The following documents explain how Piraeus Datastore works, and why it works the way it does.</p>"},{"location":"explanation/#understanding-piraeus-datastore-components","title":"Understanding Piraeus Datastore Components","text":"<p>A short introduction for every component of Piraeus Datastore.</p>"},{"location":"explanation/components/","title":"Understanding Piraeus Datastore Components","text":"<p>Piraeus Datastore consists of several different components. Each component runs as a separate Deployment, DaemonSet or plain Pod.</p> <p>All Pods are labelled according to their component. You can check the Pods running in your own cluster by running the following <code>kubectl</code> command:</p> <pre><code>$ kubectl get pods '-ocustom-columns=NAME:.metadata.name,COMPONENT:.metadata.labels.app\\.kubernetes\\.io/component'\nNAME                                                   COMPONENT\nha-controller-vd82w                                    ha-controller\nlinstor-controller-6c8f8dc47-cm8hr                     linstor-controller\nlinstor-csi-controller-59b9968b86-ftl76                linstor-csi-controller\nlinstor-csi-node-hcmk9                                 linstor-csi-node\nlinstor-satellite-k8s-10.test-66687                    linstor-satellite\npiraeus-operator-controller-manager-6dcfcb4568-6jntp   piraeus-operator\npiraeus-operator-gencert-59449cb449-nzg6z              piraeus-operator-gencert\n</code></pre>"},{"location":"explanation/components/#piraeus-operator","title":"<code>piraeus-operator</code>","text":"<p>The Piraeus Operator creates and maintains the other components, except for the <code>piraeus-operator-gencert</code> component.</p> <p>Along with deploying the needed Kubernetes resources, it maintains the LINSTOR\u00ae Cluster state by:</p> <ul> <li>Registering satellites</li> <li>Creating storage pools</li> <li>Maintaining node labels</li> </ul>"},{"location":"explanation/components/#piraeus-operator-gencert","title":"<code>piraeus-operator-gencert</code>","text":"<p>The \"generate certificate\" Pod creates and maintains the TLS key and certificate used by the Piraeus Operator. The TLS secret, named <code>webhook-server-cert</code>, is needed to start the Piraeus Operator Pod. In addition, this Pod keeps the <code>ValidatingWebhookConfiguration</code> for the Piraeus Operator up-to-date.</p> <p>The Piraeus Operator needs a TLS certificate to serve the validation endpoint for the custom resources it maintains.</p> <p>Historically, TLS certificates where created by <code>cert-manager</code>. This was removed to reduce the number of dependencies for deploying Piraeus Datastore.</p>"},{"location":"explanation/components/#linstor-controller","title":"<code>linstor-controller</code>","text":"<p>The LINSTOR Controller is responsible for resource placement, resource configuration, and orchestration of any operational processes that require a view of the whole cluster. It maintains a database of all the configuration information for the whole cluster, stored as Kubernetes objects.</p> <p>The LINSTOR Controller connects to the LINSTOR Satellites and sends them instructions for achieving the desired cluster state.</p> <p>It provides an external API used by LINSTOR CSI and Piraeus Operator to change the cluster state.</p>"},{"location":"explanation/components/#linstor-satellite","title":"<code>linstor-satellite</code>","text":"<p>The LINSTOR Satellite service runs on each node. It acts as the local configuration agent for LINSTOR managed storage. It is stateless and receives all the information it needs from the LINSTOR Controller.</p> <p>Satellites are started as DaemonSets, managed by the Piraeus Operator. We deploy one DaemonSet per node, this enables having per-node configuration and customization of the Satellite Pods.</p> <p>Satellites interact with the host operating system directly and are deployed as privileged containers. Integration with the host operating system also leads to two noteworthy interactions with Linux namespaces:</p> <ul> <li>Any DRBD\u00ae device will inherit the network namespace of the Satellite Pods. Unless the Satellites are using   host networking, DRBD will not be able to replicate data without a running Satellite Pod. See the   host networking guide for more information.</li> <li>The Satellite process is spawned in a separate UTS namespace: this allows us to keep control of the hostname reported   to DRBD tools, even when the Pod is using a generated name from the DaemonSet. Thus, DRBD connections will always use   the Kubernetes node name.</li> </ul> <p>The use of separate UTS namespace should be completely transparent to users: running <code>kubectl exec ...</code> on a satellite   Pod will drop you into this namespace, enabling you to run <code>drbdadm</code> commands as expected.</p>"},{"location":"explanation/components/#linstor-csi-controller","title":"<code>linstor-csi-controller</code>","text":"<p>The LINSTOR CSI Controller Pod creates, modifies and deletes volumes and snapshots. It translates the state of Kubernetes resources (<code>StorageClass</code>, <code>PersistentVolumeClaims</code>, <code>VolumeSnapshots</code>) into their equivalent in LINSTOR.</p>"},{"location":"explanation/components/#linstor-csi-node","title":"<code>linstor-csi-node</code>","text":"<p>The LINSTOR CSI Node Pods execute mount and unmount operations. Mount and Unmount are initiated by kubelet before starting a Pod with a Piraeus volume.</p> <p>They are deployed as a DaemonSet on every node in the cluster by default. There needs to be a LINSTOR Satellite running on the same node as a CSI Node Pod.</p>"},{"location":"explanation/components/#ha-controller","title":"<code>ha-controller</code>","text":"<p>The Piraeus High Availability Controller will speed up the fail-over process for stateful workloads using Piraeus for storage.</p> <p>It is deployed on every node in the cluster and listens for DRBD\u00ae events to detect storage failures on other nodes. It evicts Pods when it detects that the storage on their node is inaccessible.</p>"},{"location":"how-to/","title":"How To","text":"<p>These guides show you how to configure a specific aspect or achieve a specific task with Piraeus Datastore.</p>"},{"location":"how-to/#advanced-deployments","title":"Advanced Deployments","text":"<ul> <li> <p>Use Piraeus Datastore with an Existing LINSTOR Cluster</p> <p> Guide</p> </li> <li> <p>Configure the DRBD Module Loader</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#securing-components","title":"Securing Components","text":"<ul> <li> <p>Configure TLS Between LINSTOR Controller and LINSTOR Satellite</p> <p> Guide</p> </li> <li> <p>Configure TLS for the LINSTOR API</p> <p> Guide</p> </li> <li> <p>Configure TLS for DRBD Replication</p> <p> Guide</p> </li> <li> <p>Load DRBD with SecureBoot Enabled</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#kubernetes-distributions","title":"Kubernetes Distributions","text":"<ul> <li> <p>Deploy Piraeus Datastore on OpenShift</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on Talos Linux</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on Flatcar Container Linux</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on MicroK8s</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on k0s</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#networking","title":"Networking","text":"<ul> <li> <p>Deploy Piraeus Datastore behind an HTTP Proxy</p> <p> Guide</p> </li> <li> <p>Deploy a NetworkPolicy for Piraeus Datastore</p> <p> Guide</p> </li> <li> <p>Use the Host Network for DRBD Replication</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#maintenance-tasks","title":"Maintenance Tasks","text":"<ul> <li> <p>Monitor Piraeus Datastore with Prometheus Operator</p> <p> Guide</p> </li> <li> <p>Keep Persistent Volume Affinity Updated with LINSTOR Affinity Controller</p> <p> Guide</p> </li> <li> <p>Restore a LINSTOR Database Backup</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/api-tls/","title":"How to Configure TLS for the LINSTOR API","text":"<p>This guide shows you how to set up TLS for the LINSTOR\u00ae API. The API, served by the LINSTOR Controller, is used by clients such as the CSI Driver and the Operator itself to control the LINSTOR Cluster.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> <li>using either cert-manager or <code>openssl</code> to create TLS certificates.</li> </ul>"},{"location":"how-to/api-tls/#provision-keys-and-certificates-using-cert-manager","title":"Provision Keys and Certificates Using cert-manager","text":"<p>This method requires a working cert-manager deployment in your cluster. For an alternative way to provision keys and certificates, see the <code>openssl</code> section below.</p> <p>When using TLS, the LINSTOR API uses client certificates for authentication. It is good practice to have a separate CA just for these certificates.</p> <pre><code>---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: ca-bootstrapper\n  namespace: piraeus-datastore\nspec:\n  selfSigned: { }\n---\napiVersion: cert-manager.io/v1\nkind: Certificate\nmetadata:\n  name: linstor-api-ca\n  namespace: piraeus-datastore\nspec:\n  commonName: linstor-api-ca\n  secretName: linstor-api-ca\n  duration: 87600h # 10 years\n  isCA: true\n  usages:\n    - signing\n    - key encipherment\n    - cert sign\n  issuerRef:\n    name: ca-bootstrapper\n    kind: Issuer\n---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: linstor-api-ca\n  namespace: piraeus-datastore\nspec:\n  ca:\n    secretName: linstor-api-ca\n</code></pre> <p>Then, configure this new issuer to let the Operator provision the needed certificates:</p> <pre><code>---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    certManager:\n      name: linstor-api-ca\n      kind: Issuer\n</code></pre> <p>This completes the necessary steps for secure the LINSTOR API with TLS using cert-manager. Skip to the last section to verify TLS is working.</p>"},{"location":"how-to/api-tls/#provision-keys-and-certificates-using-openssl","title":"Provision Keys and Certificates Using <code>openssl</code>","text":"<p>If you completed the cert-manager section above, skip directly to the verifying the configuration below.</p> <p>This method requires the <code>openssl</code> program on the command line. For an alternative way to provision keys and certificates, see the cert-manager section above.</p> <p>First, create a new Certificate Authority using a new key and a self-signed certificate, valid for 10 years:</p> <pre><code>openssl req -new -newkey rsa:4096 -days 3650 -nodes -x509 -keyout ca.key -out ca.crt -subj \"/CN=linstor-api-ca\"\n</code></pre> <p>Then, create two new keys, one for the LINSTOR API server, one for all LINSTOR API clients:</p> <pre><code>openssl genrsa -out api-server.key 4096\nopenssl genrsa -out api-client.key 4096\n</code></pre> <p>Next, we will create a certificate for the server. The clients might use different shortened service names, so we need to specify multiple subject names:</p> <pre><code>cat /etc/ssl/openssl.cnf &gt; api-csr.cnf\ncat &gt;&gt; api-csr.cnf &lt;&lt;EOF\n[ v3_req ]\nsubjectAltName = @alt_names\n[ alt_names ]\nDNS.0 = linstor-controller.piraeus-datastore.svc.cluster.local\nDNS.1 = linstor-controller.piraeus-datastore.svc\nDNS.2 = linstor-controller\nEOF\nopenssl req -new -sha256 -key api-server.key -subj \"/CN=linstor-controller\" -config api-csr.cnf -extensions v3_req -out api-server.csr\nopenssl x509 -req -in api-server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -config api-csr.cnf -extensions v3_req -out api-server.crt -days 3650 -sha256\n</code></pre> <p>For the client certificate, simply setting one subject name is enough:</p> <pre><code>openssl req -new -sha256 -key api-client.key -subj \"/CN=linstor-client\" -out api-client.csr\nopenssl x509 -req -in api-client.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out api-client.crt -days 3650 -sha256\n</code></pre> <p>Now, we create Kubernetes secrets from the created keys and certificates:</p> <pre><code>kubectl create secret generic linstor-api-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=api-server.crt --from-file=tls.key=api-server.key\nkubectl create secret generic linstor-client-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=api-client.crt --from-file=tls.key=api-client.key\n</code></pre> <p>Finally, configure the Operator resources to reference the newly created secrets. We configure the same client secret for all components for simplicity.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    apiSecretName: linstor-api-tls\n    clientSecretName: linstor-client-tls\n    csiControllerSecretName: linstor-client-tls\n    csiNodeSecretName: linstor-client-tls\n</code></pre>"},{"location":"how-to/api-tls/#verifying-tls-configuration","title":"Verifying TLS Configuration","text":"<p>You can verify that the secure API is running by manually connecting to the HTTPS endpoint using <code>curl</code></p> <pre><code>$ kubectl exec -n piraeus-datastore deploy/linstor-controller -- curl --key /etc/linstor/client/tls.key --cert /etc/linstor/client/tls.crt --cacert /etc/linstor/client/ca.crt https://linstor-controller.piraeus-datastore.svc:3371/v1/controller/version\n{\"version\":\"1.20.2\",\"git_hash\":\"58a983a5c2f49eb8d22c89b277272e6c4299457a\",\"build_time\":\"2022-12-14T14:21:28+00:00\",\"rest_api_version\":\"1.16.0\"}%\n</code></pre> <p>If the command is successful, the API is using HTTPS and clients are able to connect with their certificates.</p> <p>If you see an error, make sure that the client certificates are trusted by the API secret, and vice versa. The following script provides a quick way to verify that one TLS certificate is trusted by another:</p> <pre><code>function k8s_secret_trusted_by() {\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"tls.crt\" | base64decode }}' \"$1\" &gt; $1.tls.crt\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"ca.crt\" | base64decode }}' \"$2\" &gt; $2.ca.crt\n    openssl verify -CAfile $2.ca.crt $1.tls.crt\n}\nk8s_secret_trusted_by linstor-client-tls linstor-api-tls\n# Expected output:\n# linstor-client-tls.tls.crt: OK\n</code></pre> <p>Another issue might be the API endpoint using a Certificate not using the expected service name. A typical error message for this issue would be:</p> <pre><code>curl: (60) SSL: no alternative certificate subject name matches target host name 'linstor-controller.piraeus-datastore.svc'\n</code></pre> <p>In this case, make sure you have specified the right subject names when provisioning the certificates.</p> <p>All available options are documented in the reference for <code>LinstorCluster</code>.</p>"},{"location":"how-to/drbd-host-networking/","title":"How to Use the Host Network for DRBD Replication","text":"<p>This guide shows you how to use the host network for DRBD\u00ae replication.</p> <p>By default, DRBD will use the container network to replicate volume data. This ensures replication works on a wide range of clusters without further configuration. It also enables use of <code>NetworkPolicy</code> to block unauthorized access to DRBD traffic. Since the network interface of the Pod is tied to the lifecycle of the Pod, it also means DRBD will temporarily disrupt replication when the LINSTOR\u00ae Satellite Pod is restarted.</p> <p>In contrast, using the host network for DRBD replication will cause replication to work independent of the LINSTOR Satellite Pod. The host network might also offer better performance than the container network. As a downside, you will have to manually ensure connectivity between Nodes on the relevant ports.</p> <p>To follow the steps in this guide, you should be familiar with editing <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-container-network-to-host-network","title":"Switch from Container Network to Host Network","text":"<p>Switching from the default container network to host network is possible at any time. Existing DRBD resources will be reconfigured to use the host network interface.</p> <p>To configure the host network for the LINSTOR Satellite, apply the following configuration:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: host-network\nspec:\n  podTemplate:\n    spec:\n      hostNetwork: true\n</code></pre> <p>After the Satellite Pods are recreated, they will use the host network. Any existing DRBD resources are reconfigured to use the new IP Address instead.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-host-network-to-container-network","title":"Switch from Host Network to Container Network","text":"<p>Switching back from host network to container network involves manually resetting the configured peer addresses used by DRBD. This can either be achieved by rebooting every node, or by manually resetting the address using <code>drbdadm</code>.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-host-network-to-container-network-using-reboots","title":"Switch from Host Network to Container Network Using Reboots","text":"<p>First, you need to remove the <code>LinstorSatelliteConfiguration</code> that set <code>hostNetwork: true</code>:</p> <pre><code>$ kubectl delete linstorsatelliteconfigurations.piraeus.io host-network\nlinstorsatelliteconfiguration.piraeus.io \"host-network\" deleted\n</code></pre> <p>Then, reboot each cluster node, either one by one or multiple at once. In general, replication will not work between rebooted nodes and non-rebooted nodes. The non-rebooted nodes will continue to use the host network addresses, which are generally not reachable from the container network.</p> <p>After all nodes are rebooted, all resources are configured to use the container network, and all DRBD connections should be connected again.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-host-network-to-container-network-using-drbdadm","title":"Switch from Host Network to Container Network Using <code>drbdadm</code>","text":"<p>During this procedure, ensure no new volumes or snapshots are created: otherwise the migration to the container network might not be applied to all resources.</p> <p>First, you need to temporarily stop all replication and suspend all DRBD volumes using <code>drbdadm suspend-io all</code>. The command is executed once on each LINSTOR Satellite Pod.</p> <pre><code>$ kubectl exec ds/linstor-satellite.node1.example.com -- drbdadm suspend-io all\n$ kubectl exec ds/linstor-satellite.node2.example.com -- drbdadm suspend-io all\n$ kubectl exec ds/linstor-satellite.node3.example.com -- drbdadm suspend-io all\n</code></pre> <p>Next, you will need to disconnect all DRBD connections on all nodes.</p> <pre><code>$ kubectl exec ds/linstor-satellite.node1.example.com -- drbdadm disconnect --force all\n$ kubectl exec ds/linstor-satellite.node2.example.com -- drbdadm disconnect --force all\n$ kubectl exec ds/linstor-satellite.node3.example.com -- drbdadm disconnect --force all\n</code></pre> <p>Now, we can safely reset all DRBD connection paths, which frees the connection to be moved to the container network.</p> <pre><code>$ kubectl exec ds/linstor-satellite.node1.example.com -- drbdadm del-path all\n$ kubectl exec ds/linstor-satellite.node2.example.com -- drbdadm del-path all\n$ kubectl exec ds/linstor-satellite.node3.example.com -- drbdadm del-path all\n</code></pre> <p>Finally, removing the <code>LinstorSatelliteConfiguration</code> that set <code>hostNetwork: true</code> will trigger the creation of new LINSTOR Satellite Pods using the container network:</p> <pre><code>$ kubectl delete linstorsatelliteconfigurations.piraeus.io host-network\nlinstorsatelliteconfiguration.piraeus.io \"host-network\" deleted\n</code></pre> <p>After the Pods are recreated and the LINSTOR Satellites are <code>Online</code>, the DRBD resource will be reconfigured and resume IO.</p>"},{"location":"how-to/drbd-loader/","title":"How to Configure the DRBD Module Loader","text":"<p>This guide shows you how to configure various aspects of the DRBD\u00ae Module Loader.</p> <p>To follow the steps in this guide, you should be familiar with editing <code>LinstorSatelliteConfiguration</code> resources.</p> <p>DRBD Module Loader is the component responsible for making the DRBD kernel module available, as well as loading other useful kernel modules for Piraeus.</p> <p>The following modules are loaded if available:</p> Module Purpose <code>libcrc32c</code> dependency for DRBD <code>nvmet_rdma</code>, <code>nvme_rdma</code> LINSTOR NVME layer <code>loop</code> LINSTOR when using loop devices as backing disks <code>dm_writecache</code> LINSTOR writecache layer <code>dm_cache</code> LINSTOR cache layer <code>dm_thin_pool</code> LINSTOR thin-provisioned storage <code>dm_snapshot</code> LINSTOR Snapshots <code>dm_crypt</code> LINSTOR encrypted volumes"},{"location":"how-to/drbd-loader/#disable-the-drbd-module-loader","title":"Disable the DRBD Module Loader","text":"<p>In some circumstances it might be necessary to disable the DRBD Module Loader entirely. For example, you are using an immutable operating system, and DRBD and other modules are loaded as part of the host configuration.</p> <p>To disable the DRBD Module Loader completely, use the following configuration:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: no-loader\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          $patch: delete\n</code></pre>"},{"location":"how-to/drbd-loader/#select-a-different-drbd-loader-version","title":"Select a Different DRBD Loader Version","text":"<p>By default, the Operator will try to find a DRBD Module Loader matching the host operating system. The host distribution is determined by inspecting the <code>.status.nodeInfo.osImage</code> field of the Kubernetes Node resource. A user-defined image can be used if the automatic mapping does not succeed or if you have different module loading requirements.</p> <p>This configuration overrides the chosen DRBD Module Loader image with a user-defined image <code>example.com/drbd-loader:v9</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: custom-drbd-module-loader-image\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          image: example.com/drbd-loader:v9\n</code></pre> <p>Piraeus maintains the following images:</p> Image Distribution <code>quay.io/piraeusdatastore/drbd9-almalinux9</code> RedHat Enterprise Linux 9 rebuilds <code>quay.io/piraeusdatastore/drbd9-almalinux8</code> RedHat Enterprise Linux 8 rebuilds <code>quay.io/piraeusdatastore/drbd9-centos7</code> RedHat Enterprise Linux 7 rebuilds <code>quay.io/piraeusdatastore/drbd9-jammy</code> Ubuntu 22.04 <code>quay.io/piraeusdatastore/drbd9-focal</code> Ubuntu 20.04 <code>quay.io/piraeusdatastore/drbd9-bionic</code> Ubuntu 18.04 <code>quay.io/piraeusdatastore/drbd9-bookworm</code> Debian 12 <code>quay.io/piraeusdatastore/drbd9-bullseye</code> Debian 11 <code>quay.io/piraeusdatastore/drbd9-buster</code> Debian 10 <p>You can create a loader image for your own distribution using the Piraeus sources as reference.</p>"},{"location":"how-to/drbd-loader/#change-the-way-drbd-module-loader-loads-the-drbd-module","title":"Change the Way DRBD Module Loader Loads the DRBD Module","text":"<p>By default, DRBD Module Loader will try to build the kernel module from source. The loader can also be configured to load the module from a Debian or RPM package included in the image, or skip loading DRBD entirely.</p> <p>To change the behaviour of the DRBD Loader, set the <code>LB_HOW</code> environment variable:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: no-drbd-module-loader\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          env:\n            - name: LB_HOW\n              value: deps_only\n</code></pre> <code>LB_HOW</code> Loader behaviour <code>compile</code> The default. Build the DRBD module from source and try to load all optional modules from the host. <code>shipped_modules</code> Searches for <code>.rpm</code> or <code>.deb</code> packages at  <code>/pkgs</code> and inserts contained the DRBD modules. Optional modules are loaded from the host if available. <code>deps_only</code> Only try loading the optional modules. No DRBD module will be loaded."},{"location":"how-to/drbd-tls/","title":"How to Use Transport Layer Security for DRBD Replication","text":"<p>This guide shows you how to use Transport Layer Security (TLS) for DRBD\u00ae replication.</p> <p>TLS is a protocol designed to provide security, including privacy, integrity and authentication for network communications. Starting with DRBD 9.2.6, replication traffic in DRBD can be encrypted using TLS, using the Linux kernel TLS Upper Layer Protocol.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code> resources.</li> <li>configuring TLS certificates for internal traffic.</li> </ul>"},{"location":"how-to/drbd-tls/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install Piraeus Operator &gt;= 2.3.0. The following command shows the deployed version, in this case v2.3.0:   <pre><code>$ kubectl get pods -l app.kubernetes.io/component=piraeus-operator -ojsonpath='{.items[*].spec.containers[?(@.name==\"manager\")].image}{\"\\n\"}'\nquay.io/piraeusdatastore/piraeus-operator:v2.3.0\n</code></pre></li> <li>Use a host operating system with kernel TLS offload enabled. TLS offload was added in Linux 4.19. The following   distributions are known to have TLS offload enabled:</li> <li>RHEL &gt;= 8.2</li> <li>Ubuntu &gt;= 22.04</li> <li>Debian &gt;= 12</li> <li>Have DRBD 9.2.6 or newer loaded. The following script shows the currently loaded DRBD version on all nodes:   <pre><code>for SATELLITE in $(kubectl get pods -l app.kubernetes.io/component=linstor-satellite -ojsonpath='{range .items[*]}{.metadata.name}{\"\\n\"}{end}'); do\n  echo \"$SATELLITE: $(kubectl exec $SATELLITE -- head -1 /proc/drbd)\"\ndone\n</code></pre></li> </ul>"},{"location":"how-to/drbd-tls/#configure-tls-between-linstor-controller-and-linstor-satellite","title":"Configure TLS Between LINSTOR Controller and LINSTOR Satellite","text":"<p>This step is covered in a dedicated guide. Follow the steps in the guide, but set the <code>tlsHandshakeDaemon</code> field in the <code>LinstorSatelliteConfiguration</code> resource:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: internal-tls\nspec:\n  internalTLS:\n    tlsHandshakeDaemon: true\n    # ...\n</code></pre> <p>This change will cause the Piraeus Operator to deploy an additional container named <code>ktls-utils</code> on the Satellite Pod.</p> <pre><code>$ kubectl logs -l app.kubernetes.io/component=linstor-satellite -c ktls-utils\ntlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06\ntlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06\ntlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06\n</code></pre>"},{"location":"how-to/drbd-tls/#configure-tls-for-drbd","title":"Configure TLS for DRBD","text":"<p>To instruct LINSTOR\u00ae to configure TLS for DRBD, the <code>DrbdOptions/Net/tls</code> property needs to be set to <code>yes</code>. This can be done directly on the <code>LinstorCluster</code> resource, so it automatically applies to all resources, or as part of the parameters in a StorageClass.</p> <p>To apply the property cluster-wide, add the following property entry to your <code>LinstorCluster</code> resource:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  properties:\n    - name: DrbdOptions/Net/tls\n      value: \"yes\"\n</code></pre> <p>To apply the property only for certain StorageClasses, add the following parameter to the selected StorageClasses:</p> <pre><code>apiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: example\nprovisioner: linstor.csi.linbit.com\nparameters:\n  property.linstor.csi.linbit.com/DrbdOptions/Net/tls: \"yes\"\n  # ...\n</code></pre>"},{"location":"how-to/drbd-tls/#switch-existing-resources-to-tls","title":"Switch Existing Resources to TLS","text":"<p>DRBD does not support online reconfiguration to use DRBD. To switch existing resources to use TLS, for example by setting the property on the <code>LinstorCluster</code> resource, you need to perform the following steps on all nodes:</p> <p>First, you need to temporarily stop all replication and suspend all DRBD volumes using <code>drbdadm suspend-io all</code>. The command is executed once on each LINSTOR Satellite Pod.</p> <pre><code>$ kubectl exec node1.example.com -- drbdadm suspend-io all\n$ kubectl exec node2.example.com -- drbdadm suspend-io all\n$ kubectl exec node3.example.com -- drbdadm suspend-io all\n</code></pre> <p>Next, you will need to disconnect all DRBD connections on all nodes.</p> <pre><code>$ kubectl exec node1.example.com -- drbdadm disconnect --force all\n$ kubectl exec node2.example.com -- drbdadm disconnect --force all\n$ kubectl exec node3.example.com -- drbdadm disconnect --force all\n</code></pre> <p>Now, we can safely reconnect DRBD connection paths, which configures the TLS connection parameters.</p> <pre><code>$ kubectl exec node1.example.com -- drbdadm adjust all\n$ kubectl exec node2.example.com -- drbdadm adjust all\n$ kubectl exec node3.example.com -- drbdadm adjust all\n</code></pre>"},{"location":"how-to/drbd-tls/#confirm-drbd-uses-tls","title":"Confirm DRBD Uses TLS","text":"<p>To confirm that DRBD is using TLS for replication, check the following resources.</p> <p>First, confirm that the <code>ktls-utils</code> container performed the expected handshakes:</p> <pre><code>$ kubectl logs -l app.kubernetes.io/component=linstor-satellite -c ktls-utils\n...\nHandshake with node2.example.com (10.127.183.183) was successful\nHandshake with node2.example.com (10.127.183.183) was successful\n...\nHandshake with node3.example.com (10.125.97.42) was successful\nHandshake with node3.example.com (10.125.97.42) was successful\n...\n</code></pre> <p>[!NOTE] The following messages are expected when running <code>ktls-utils</code> in a container and can be safely ignored: <pre><code>File /etc/tlshd.d/tls.key: expected mode 600\nadd_key: Bad message\n</code></pre></p> <p>Next, check the statistics on TLS sessions controlled by the kernel on each node. You should see an equal, nonzero number of <code>TlsRxSw</code> and <code>TlsRxSw</code>.</p> <pre><code>$ kubectl exec node1.example.com -- cat /proc/net/tls_stat\nTlsCurrTxSw                         4\nTlsCurrRxSw                         4\nTlsCurrTxDevice                     0\nTlsCurrRxDevice                     0\nTlsTxSw                             4\nTlsRxSw                             4\nTlsTxDevice                         0\nTlsRxDevice                         0\nTlsDecryptError                     0\nTlsRxDeviceResync                   0\nTlsDecryptRetry                     0\nTlsRxNoPadViolation                 0\n</code></pre> <p>[!NOTE] If your network card supports TLS offloading, you might see <code>TlsTxDevice</code> and <code>TlsRxDevice</code> being nonzero instead.</p>"},{"location":"how-to/external-controller/","title":"How to Use an Existing LINSTOR Cluster","text":"<p>This guide shows you how to connect Piraeus with an existing LINSTOR\u00ae Cluster, managed outside Kubernetes.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> </ul>"},{"location":"how-to/external-controller/#configure-the-piraeus-resources","title":"Configure the Piraeus Resources","text":"<p>To use an externally managed LINSTOR Cluster, specify the URL of the LINSTOR Controller in the <code>LinstorCluster</code> resource. In the following example, the Controller is reachable at <code>http://linstor-controller.example.com:3370</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  externalController:\n    url: http://linstor-controller.example.com:3370\n</code></pre> <p>After applying the <code>LinstorCluster</code>, Piraeus will make the following changes to the default deployment:</p> <ul> <li>The <code>linstor-controller</code> Deployment is removed</li> <li>The <code>linstor-csi-controller</code> and <code>linstor-csi-node</code> resources will reference the external controller.</li> </ul>"},{"location":"how-to/external-controller/#configuring-host-networking-for-linstor-satellites","title":"Configuring Host Networking for LINSTOR Satellites","text":"<p>Normally the Pod network is not reachable from outside the Kubernetes Cluster. In this case the existing LINSTOR Controller won't be able to communicate with the Satellites in the Kubernetes cluster. So you should configure your Satellites to use host networking.</p> <p>To use host networking, apply the following configuration resource:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: host-network\nspec:\n  podTemplate:\n    spec:\n      hostNetwork: true\n</code></pre>"},{"location":"how-to/external-controller/#verifying-the-configuration","title":"Verifying the Configuration","text":"<p>To verify that the external LINSTOR Controller is configured, check:</p> <ul> <li>The <code>Available</code> condition on the <code>LinstorCluster</code> resource reports the expected Controller URL:   <pre><code>$ kubectl get LinstorCluster -ojsonpath='{.items[].status.conditions[?(@.type==\"Available\")].message}{\"\\n\"}'\nController 1.20.3 (API: 1.16.0, Git: 8d19a891df018f6e3d40538d809904f024bfe361) reachable at 'http://linstor-controller.example.com:3370'\n</code></pre></li> <li>The <code>linstor-csi-controller</code> Deployment uses the expected URL:   <pre><code>$ kubectl get -n piraeus-datastore deployment linstor-csi-controller -ojsonpath='{.spec.template.spec.containers[?(@.name==\"linstor-csi\")].env[?(@.name==\"LS_CONTROLLERS\")].value}{\"\\n\"}'\nhttp://linstor-controller.example.com:3370\n</code></pre></li> <li>The <code>linstor-csi-node</code> Deployment uses the expected URL:   <pre><code>$ kubectl get -n piraeus-datastore daemonset linstor-csi-node -ojsonpath='{.spec.template.spec.containers[?(@.name==\"linstor-csi\")].env[?(@.name==\"LS_CONTROLLERS\")].value}{\"\\n\"}'\nhttp://linstor-controller.example.com:3370\n</code></pre></li> <li>The Kubernetes nodes are registered as Satellite nodes on the LINSTOR Controller:   <pre><code>$ kubectl get nodes -owide\nNAME               STATUS   ROLES           AGE   VERSION   INTERNAL-IP      EXTERNAL-IP   OS-IMAGE                    KERNEL-VERSION                 CONTAINER-RUNTIME\nk8s-1-26-10.test   Ready    control-plane   22m   v1.26.3   192.168.122.10   &lt;none&gt;        AlmaLinux 9.1 (Lime Lynx)   5.14.0-162.22.2.el9_1.x86_64   containerd://1.6.20\n...\n$ linstor node list\n\u256d\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u256e\n\u250a Node             \u250a NodeType  \u250a Addresses                   \u250a State  \u250a\n\u255e\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2561\n\u250a k8s-1-26-10.test \u250a SATELLITE \u250a 192.168.122.10:3366 (PLAIN) \u250a Online \u250a\n...\n</code></pre></li> </ul>"},{"location":"how-to/flatcar/","title":"How to Load DRBD on Flatcar Container Linux","text":"<p>This guide shows you how to set up the DRBD\u00ae Module Loader when using Flatcar Container Linux.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> </ul>"},{"location":"how-to/flatcar/#configure-the-drbd-module-loader","title":"Configure the DRBD Module Loader","text":"<p>Flatcar Container Linux uses a read-only <code>/usr</code> file system. For building DRBD from source on Flatcar Container Linux, the default bind mount for the not existing <code>/usr/src</code> directory needs to be disabled for the <code>drbd-module-loader</code> init container.</p> <p>To change the configuration for the <code>drbd-module-loader</code> container, apply the following <code>LinstorSatelliteConfiguration</code>:</p> <pre><code>---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: no-usr-src-mount\nspec:\n  podTemplate:\n    spec:\n      volumes:\n        - name: usr-src\n          $patch: delete\n      initContainers:\n        - name: drbd-module-loader\n          volumeMounts:\n            - mountPath: /usr/src\n              name: usr-src\n              $patch: delete\n</code></pre>"},{"location":"how-to/http-proxy/","title":"How to Use Piraeus Datastore with an HTTP Proxy","text":"<p>This guide shows you how to configure the DRBD\u00ae Module Loader when using a HTTP Proxy.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li> </ul>"},{"location":"how-to/http-proxy/#configuration","title":"Configuration","text":"<p>We will use environment variables to configure the proxy, this tells the drbd-module-loader component to use the proxy for outgoing communication.</p> <p>Configure the sample below according to your environment and apply the configuration using <code>kubectl apply -f filename.yml</code>.</p> <p>This sample configuration assumes that a HTTP proxy is reacheable at <code>http://10.0.0.1:3128</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: http-proxy\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          env:\n            - name: HTTP_PROXY\n              value: http://10.0.0.1:3128 # Add your proxy connection here\n            - name: HTTPS_PROXY\n              value: http://10.0.0.1:3128 # Add your proxy connection here\n            - name: NO_PROXY\n              value: localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12 # Add internal IP ranges and domains here\n</code></pre>"},{"location":"how-to/install-kernel-headers/","title":"Installing Linux Kernel Headers","text":"<p>Piraeus Datastore uses DRBD\u00ae to mirror your volume data to one or more nodes. This document aims to describe the way to install the necessary files for common Linux distributions.</p> <p>To check if your nodes already have the necessary files installed, try running:</p> <pre><code>$ test -d /lib/modules/$(uname -r)/build/ &amp;&amp; echo found headers\n</code></pre> <p>If the command prints <code>found headers</code>, your nodes are good to go.</p>"},{"location":"how-to/install-kernel-headers/#installing-on-ubuntu","title":"Installing on Ubuntu","text":"<p>Installation of Linux Kernel headers on Ubuntu can be done through the <code>apt</code> package manager:</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-$(uname -r)\n</code></pre> <p>In addition, you can install the <code>linux-headers-virtual</code> package. This causes <code>apt upgrade</code> to install the headers matching any newly installed kernel versions.</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-virtual\n</code></pre>"},{"location":"how-to/install-kernel-headers/#installing-on-debian","title":"Installing on Debian","text":"<p>Installation of Linux Kernel headers on Debian can be done through the <code>apt</code> package manager:</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-$(uname -r)\n</code></pre> <p>In addition, you can install an additional package, that causes <code>apt</code> to also install Kernel headers on upgrade:</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-$(dpkg --print-architecture)\n</code></pre>"},{"location":"how-to/install-kernel-headers/#installing-on-redhat-enterprise-linux","title":"Installing on RedHat Enterprise Linux","text":"<p>Installing on RedHat Enterprise Linux or compatible distributions, such as AlmaLinux or Rocky Linux can be done through the <code>dnf</code> package manager:</p> <pre><code>$ sudo dnf install -y kernel-devel-$(uname -r)\n</code></pre> <p>In addition, you can install an additional package, that causes <code>yum</code> to also install Kernel headers on upgrade:</p> <pre><code>$ sudo dnf install -y kernel-devel\n</code></pre>"},{"location":"how-to/internal-tls/","title":"How to Configure TLS Between LINSTOR Controller and LINSTOR Satellite","text":"<p>This guide shows you how to set up TLS between LINSTOR\u00ae Controller and LINSTOR Satellite.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the LINSTOR client to verify success.</li> <li>using either cert-manager or <code>openssl</code> to create TLS certificates.</li> </ul>"},{"location":"how-to/internal-tls/#provision-keys-and-certificates-using-cert-manager","title":"Provision Keys and Certificates Using cert-manager","text":"<p>This method requires a working cert-manager deployment in your cluster. For an alternative way to provision keys and certificates, see the <code>openssl</code> section below.</p> <p>LINSTOR Controller and Satellite only need to trust each other, so it is good practice to have a CA only for those components. Apply the following YAML to create a new Issuer:</p> <pre><code>---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: ca-bootstrapper\n  namespace: piraeus-datastore\nspec:\n  selfSigned: { }\n---\napiVersion: cert-manager.io/v1\nkind: Certificate\nmetadata:\n  name: linstor-internal-ca\n  namespace: piraeus-datastore\nspec:\n  commonName: linstor-internal-ca\n  secretName: linstor-internal-ca\n  duration: 87600h # 10 years\n  isCA: true\n  usages:\n    - signing\n    - key encipherment\n    - cert sign\n  issuerRef:\n    name: ca-bootstrapper\n    kind: Issuer\n---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: linstor-internal-ca\n  namespace: piraeus-datastore\nspec:\n  ca:\n    secretName: linstor-internal-ca\n</code></pre> <p>Then, configure this new issuer to let the Operator provision the needed certificates:</p> <pre><code>---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    certManager:\n      name: linstor-internal-ca\n      kind: Issuer\n---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: internal-tls\nspec:\n  internalTLS:\n    certManager:\n      name: linstor-internal-ca\n      kind: Issuer\n</code></pre> <p>This completes the necessary steps for secure TLS connections between LINSTOR Controller and Satellite using cert-manager. Skip to the last section to verify TLS is working.</p>"},{"location":"how-to/internal-tls/#provision-keys-and-certificates-using-openssl","title":"Provision Keys and Certificates Using <code>openssl</code>","text":"<p>If you completed the cert-manager section above, skip directly to the verifying the configuration below.</p> <p>This method requires the <code>openssl</code> program on the command line. For an alternative way to provision keys and certificates, see the cert-manager section above.</p> <p>First, create a new Certificate Authority using a new key and a self-signed certificate, valid for 10 years:</p> <pre><code>openssl req -new -newkey rsa:4096 -days 3650 -nodes -x509 -keyout ca.key -out ca.crt -subj \"/CN=linstor-internal-ca\"\n</code></pre> <p>Then, create two new keys, one for the LINSTOR Controller, one for all Satellites:</p> <pre><code>openssl genrsa -out controller.key 4096\nopenssl genrsa -out satellite.key 4096\n</code></pre> <p>Next, we will create a certificate for each key, valid for 10 years, signed by the Certificate Authority:</p> <pre><code>openssl req -new -sha256 -key controller.key -subj \"/CN=linstor-controller\" -out controller.csr\nopenssl req -new -sha256 -key satellite.key -subj \"/CN=linstor-satellite\" -out satellite.csr\nopenssl x509 -req -in controller.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out controller.crt -days 3650 -sha256\nopenssl x509 -req -in satellite.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out satellite.crt -days 3650 -sha256\n</code></pre> <p>Now, we create Kubernetes secrets from the created keys and certificates:</p> <pre><code>kubectl create secret generic linstor-controller-internal-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=controller.crt --from-file=tls.key=controller.key\nkubectl create secret generic linstor-satellite-internal-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=satellite.crt --from-file=tls.key=satellite.key\n</code></pre> <p>Finally, configure the Operator resources to reference the newly created secrets:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    secretName: linstor-controller-internal-tls\n---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: internal-tls\nspec:\n  internalTLS:\n    secretName: linstor-satellite-internal-tls\n</code></pre>"},{"location":"how-to/internal-tls/#verifying-tls-configuration","title":"Verifying TLS Configuration","text":"<p>You can verify the secure TLS connection between LINSTOR Controller and Satellite by checking the output of the <code>linstor node list</code> command. If TLS is enabled, you will see <code>(SSL)</code> next to the active satellite address:</p> <pre><code>$ kubectl exec -n piraeus-datastore deploy/linstor-controller -- linstor node list\n+---------------------------------------------------------------------+\n| Node               | NodeType  | Addresses                 | State  |\n|=====================================================================|\n| node01.example.com | SATELLITE | 10.116.72.142:3367 (SSL)  | Online |\n| node02.example.com | SATELLITE | 10.127.183.140:3367 (SSL) | Online |\n| node03.example.com | SATELLITE | 10.125.97.50:3367 (SSL)   | Online |\n+---------------------------------------------------------------------+\n</code></pre> <p>If you see <code>(PLAIN)</code> instead, this indicates that the TLS configuration was not applied successfully. Check the status of the <code>LinstorCluster</code> and <code>LinstorSatellite</code> resource.</p> <p>If you see <code>(SSL)</code>, but the node remains offline, this usually indicates that a certificate is not trusted by the other party. Verify that the Controller's <code>tls.crt</code> is trusted by the Satellite's <code>ca.crt</code> and vice versa. The following script provides a quick way to verify that one TLS certificate is trusted by another:</p> <pre><code>function k8s_secret_trusted_by() {\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"tls.crt\" | base64decode }}' \"$1\" &gt; $1.tls.crt\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"ca.crt\" | base64decode }}' \"$2\" &gt; $2.ca.crt\n    openssl verify -CAfile $2.ca.crt $1.tls.crt\n}\nk8s_secret_trusted_by satellite-tls controller-tls\n# Expected output:\n# satellite-tls.tls.crt: OK\n</code></pre> <p>All available options are documented in the reference for <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code>.</p>"},{"location":"how-to/k0s/","title":"How to Configure Piraeus Datastore on k0s","text":"<p>This guide shows you how to configure Piraeus Datastore when using k0s.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> </ul>"},{"location":"how-to/k0s/#configure-the-csi-driver","title":"Configure the CSI Driver","text":"<p>Because k0s store their state in a separate directory (<code>/var/lib/k0s</code>) the LINSTOR CSI Driver needs to be updated to use a new path for mounting volumes.</p> <p>To change the LINSTOR CSI Driver, so that it uses the k0s state paths, apply the following <code>LinstorCluster</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  csiNode:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-csi\n            volumeMounts:\n            - mountPath: /var/lib/k0s/kubelet\n              name: publish-dir\n              mountPropagation: Bidirectional\n          - name: csi-node-driver-registrar\n            args:\n            - --v=5\n            - --csi-address=/csi/csi.sock\n            - --kubelet-registration-path=/var/lib/k0s/kubelet/plugins/linstor.csi.linbit.com/csi.sock\n            - --health-port=9809\n        volumes:\n         - name: publish-dir\n           hostPath:\n             path: /var/lib/k0s/kubelet\n         - name: registration-dir\n           hostPath:\n             path: /var/lib/k0s/kubelet/plugins_registry\n         - name: plugin-dir\n           hostPath:\n              path: /var/lib/k0s/kubelet/plugins/linstor.csi.linbit.com\n</code></pre>"},{"location":"how-to/linstor-affinity-controller/","title":"How to Deploy the LINSTOR Affinity Controller","text":"<p>This guide shows you how to deploy the LINSTOR Affinity Controller for Piraeus Datastore.</p> <p>The LINSTOR Affinity Controller keeps the affinity of your volumes in sync between Kubernetes and LINSTOR.</p> <p>When using a strict volume affinity setting, such as <code>allowRemoteVolumeAccess: false</code>, the Persistent Volume (PV) resource created by Piraeus Datastore will have a fixed affinity. When the volume is moved to a different node, for example because one of the existing replicas is being evacuated, the PV is not updated automatically.</p> <p>The LINSTOR Affinity controller watches PVs and LINSTOR resource and keeps the affinity up-to-date.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>Deploying workloads in Kubernetes using <code>helm</code></li> </ul>"},{"location":"how-to/linstor-affinity-controller/#add-the-piraeus-datastore-chart-repository","title":"Add the Piraeus Datastore Chart Repository","text":"<p>Piraeus Datastore maintains a helm chart repository for commonly deployed components, including the LINSTOR Affinity Controller. To add the repository to your helm configuration, run:</p> <pre><code>$ helm repo add piraeus-charts https://piraeus.io/helm-charts/\n</code></pre>"},{"location":"how-to/linstor-affinity-controller/#deploy-the-linstor-affinity-controller","title":"Deploy the LINSTOR Affinity Controller","text":"<p>After adding the repository, deploy the LINSTOR Affinity Controller:</p> <pre><code>$ helm install linstor-affinity-controller piraeus-charts/linstor-affinity-controller\nNAME: linstor-affinity-controller\nLAST DEPLOYED: Mon Dec  4 09:14:07 2023\nNAMESPACE: piraeus-datastore\nSTATUS: deployed\nREVISION: 1\nTEST SUITE: None\nNOTES:\nLINSTOR Affinity Controller deployed.\n\nUsed LINSTOR URL: http://linstor-controller.piraeus-datastore.svc:3370\n</code></pre> <p>If you deploy the LINSTOR Affinity Controller to the same namespace as the Piraeus Operator, the deployment will automatically determine the necessary parameters for connecting to LINSTOR.</p> <p>In some cases, helm may not be able to determine the connection parameters. In this case, you need to manually provide the following values:</p> <pre><code>linstor:\n  # The URL of the LINSTOR Controller API. This example contains the default value.\n  endpoint: http://linstor-controller.piraeus-datastore.svc:3370\n  # This is the default URL when using TLS for securing the API\n  #endpoint: https://linstor-controller.piraeus-datastore.svc:3371\n  # This is the name of the secret containing TLS key and certificates for connecting to the LINSTOR API with TLS.\n  clientSecret: \"\"\noptions:\n  # This is the namespace used by Piraeus Operator to sync Kubernetes Node labels with LINSTOR node properties.\n  # For Piraeus Operator, this needs to be set to the following value:\n  propertyNamespace: Aux/topology\n</code></pre>"},{"location":"how-to/microk8s/","title":"How to Configure Piraeus Datastore on MicroK8s","text":"<p>This guide shows you how to configure Piraeus Datastore when using MicroK8s.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> </ul>"},{"location":"how-to/microk8s/#configure-the-csi-driver","title":"Configure the CSI Driver","text":"<p>MicroK8s is distributed as a Snap. Because Snaps store their state in a separate directory (<code>/var/snap</code>) the LINSTOR CSI Driver needs to be updated to use a new path for mounting volumes.</p> <p>To change the LINSTOR CSI Driver, so that it uses the MicroK8s state paths, apply the following <code>LinstorCluster</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  patches:\n    - target:\n        name: linstor-csi-node\n        kind: DaemonSet\n      patch: |\n        apiVersion: apps/v1\n        kind: DaemonSet\n        metadata:\n          name: linstor-csi-node\n        spec:\n          template:\n            spec:\n              containers:\n              - name: linstor-csi\n                volumeMounts:\n                - mountPath: /var/lib/kubelet\n                  name: publish-dir\n                  $patch: delete\n                - mountPath: /var/snap/microk8s/common/var/lib/kubelet\n                  name: publish-dir\n                  mountPropagation: Bidirectional\n</code></pre>"},{"location":"how-to/monitoring/","title":"How to Deploy Monitoring with Prometheus Operator","text":"<p>Piraeus Datastore offers integration with the Prometheus monitoring stack.</p> <p>The integration configures:</p> <ul> <li>Metrics scraping for the LINSTOR and DRBD state.</li> <li>Alerts based on the cluster state</li> <li>A Grafana dashboard</li> </ul> <p>To complete this guide, you should be familiar with:</p> <ul> <li>Deploying workloads in Kubernetes using <code>helm</code></li> <li>Deploying resources using <code>kubectl</code></li> </ul>"},{"location":"how-to/monitoring/#deploying-prometheus-operator","title":"Deploying Prometheus Operator","text":"<p>\ud83d\uddd2\ufe0f NOTE: If you already have a working Prometheus Operator deployment, skip this step.</p> <p>First deploy the Prometheus Operator. A simple way to deploy it, is to use the helm chart provided by the Prometheus Community.</p> <p>First, add the helm chart repository to your local helm configuration:</p> <pre><code>$ helm repo add prometheus-community https://prometheus-community.github.io/helm-charts\n</code></pre> <p>Then, deploy the <code>kube-prometheus-stack</code> chart. This chart will set up Prometheus, AlertManager and Grafana for your cluster. Configure it to search for monitoring and alerting rules in all namespaces:</p> <pre><code>$ helm install --create-namespace -n monitoring prometheus prometheus-community/kube-prometheus-stack \\\n  --set prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues=false \\\n  --set prometheus.prometheusSpec.podMonitorSelectorNilUsesHelmValues=false \\\n  --set prometheus.prometheusSpec.ruleSelectorNilUsesHelmValues=false\n</code></pre> <p>\ud83d\uddd2\ufe0f NOTE: By default, the deployment will only monitor resources in the <code>kube-system</code> and its own namespace. Piraeus Datastore is usually deployed in a different namespace, so Prometheus needs to be configured to watch this namespace. In the example above, this is achieved by setting the various <code>*NilUsesHelmValues</code> parameters to <code>false</code>.</p>"},{"location":"how-to/monitoring/#deploying-monitoring-and-alerting-rules-for-piraeus-datastore","title":"Deploying Monitoring and Alerting Rules for Piraeus Datastore","text":"<p>After creating a Prometheus Operator deployment and configuring it to watch all namespaces, apply the monitoring and alerting resources for Piraeus Datastore:</p> <pre><code>$ kubectl apply --server-side -n piraeus-datastore -k \"https://github.com/piraeusdatastore/piraeus-operator//config/extras/monitoring?ref=v2\"\n</code></pre>"},{"location":"how-to/monitoring/#verify-monitoring","title":"Verify Monitoring","text":"<p>Verify that the monitoring configuration is working by checking the prometheus console. First, get access to the prometheus console from your local browser by forwarding it to local port 9090:</p> <pre><code>$ kubectl port-forward -n monitoring services/prometheus-kube-prometheus-prometheus 9090:9090\n</code></pre> <p>Now, open http://localhost:9090/graph and display the <code>linstor_info</code> and <code>drbd_version</code> metrics:</p> <p> </p> <p>To view the dashboard, forward the grafana service to local port 3000:</p> <pre><code>$ kubectl port-forward -n monitoring services/prometheus-grafana 3000:http-web\n</code></pre> <p>Now, open http://localhost:3000 and log in. If using the example deployment from above, use username <code>admin</code> and password <code>prom-operator</code> to gain access. Then, select \"Piraeus Datastore\" from the available dashboards:</p> <p></p>"},{"location":"how-to/network-policy/","title":"How to Deploy a NetworkPolicy for Piraeus Datastore","text":"<p>Network Policies offer a way to restrict network access of specific pods. They can be used to block undesired network connections to specific Pods.</p> <p>Piraeus Datastore provides basic Network Policies that configure restricted access to the LINSTOR Satellites. The provided policy restricts incoming network connections to LINSTOR Satellite to only the following sources:</p> <ul> <li>Other LINSTOR Satellite Pods to allow for DRBD replication</li> <li>The LINSTOR Controller Pod, to facilitate LINSTOR Cluster operations</li> <li>Metrics collection from DRBD Reactor.</li> </ul> <p>To deploy the Network Policy, apply the following remote resource:</p> <pre><code>$ kubectl apply --server-side -k \"https://github.com/piraeusdatastore/piraeus-operator//config/extras/network-policy?ref=v2\"\nnetworkpolicy.networking.k8s.io/satellite serverside-applied\n</code></pre>"},{"location":"how-to/openshift/","title":"How to Load DRBD on OpenShift","text":"<p>This guide shows you how to set the DRBD\u00ae Module Loader when using OpenShift.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the <code>oc</code> command line tool to access the OpenShift cluster.</li> </ul>"},{"location":"how-to/openshift/#find-the-driver-toolkit-image","title":"Find the Driver Toolkit Image","text":"<p>The Driver Toolkit image contains the necessary files for building DRBD. Every OpenShift release includes a version of the Driver Toolkit image matching the operating system version of the release. You can use <code>oc</code> to print the correct image version:</p> <pre><code>$ oc adm release info --image-for=driver-toolkit\nquay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709\n</code></pre>"},{"location":"how-to/openshift/#configure-the-drbd-module-loader","title":"Configure the DRBD Module Loader","text":"<p>By default, the DRBD Module Loader will try to find the necessary header files to build DRBD from source on the host system. In OpenShift, these header files are not included in the host system. Instead, they are included in the Driver Toolkit image.</p> <p>To change the DRBD Module Loader, so that it uses the header files included in the Driver Toolkit image, apply the following <code>LinstorSatelliteConfiguration</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: openshift-loader-override\nspec:\n  podTemplate:\n    spec:\n      volumes:\n        - name: usr-src\n          emptyDir: { }\n          hostPath:\n            $patch: delete\n      initContainers:\n        - name: kernel-header-copy\n          image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709\n          args:\n            - cp\n            - -avt\n            - /container/usr/src\n            - /usr/src/kernels\n          volumeMounts:\n            - name: usr-src\n              mountPath: /container/usr/src\n          securityContext:\n            privileged: true\n        - name: drbd-module-loader\n          securityContext:\n            privileged: true\n</code></pre> <p>NOTE: Replace the <code>image</code> of the <code>kernel-header-copy</code> container with the image returned by <code>oc adm release info</code>.</p> <p>After the automatic restart of the LINSTOR\u00ae Satellite Pods, DRBD will be built from source, using the correct header files.</p>"},{"location":"how-to/openshift/#openshift-update-considerations","title":"OpenShift Update Considerations","text":"<p>OpenShift updates also update the host operating system. Since every node will be rebooted during the update, the DRBD Module loader needs to rebuild DRBD once after the restart for the new host operating system.</p> <p>To ensure that the DRBD rebuild is successful, you need to update the image in the <code>openshift-loader-override</code> configuration before starting the upgrade process. You can extract the Driver Toolkit image for the new OpenShift version before starting the upgrade like this:</p> <pre><code>$ oc adm release info 4.12.2 --image-for=driver-toolkit\nquay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709\n</code></pre>"},{"location":"how-to/restore-linstor-db/","title":"How to Restore a LINSTOR Database Backup","text":"<p>This guide shows you how to restore a LINSTOR\u00ae Controller from a database backup. A backup is created automatically on every database migration of the default <code>k8s</code> database.</p> <p>[!CAUTION] Restoring from a backup means all changes made to the Cluster state after the backup was taken are lost. This includes information about Persistent Volumes and Volume Snapshots that where created after the backup.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li> </ul>"},{"location":"how-to/restore-linstor-db/#find-the-latest-backup","title":"Find the Latest Backup","text":"<p>The backup is stored in Kubernetes Secrets. List all backups by using the following command:</p> <pre><code>$ kubectl get secrets --field-selector type=piraeus.io/linstor-backup --sort-by .metadata.creationTimestamp -ocustom-columns=\"NAME:.metadata.name,CREATED-AT:metadata.creationTimestamp,VERSION:.metadata.annotations.piraeus\\.io/linstor-version\"\nNAME                                                     CREATED-AT             VERSION\nlinstor-backup-for-linstor-controller-db7fbfd95-zsfmm    2024-11-04T07:54:29Z   LINSTOR Controller 1.27.0\nlinstor-backup-for-linstor-controller-745d54bf99-544hf   2024-11-04T08:03:59Z   LINSTOR Controller 1.29.1\n</code></pre> <p>Select the backup you want to restore, making note of the name. For example, to restore the LINSTOR 1.27.0 version, we set:</p> <pre><code>$ BACKUP_NAME=linstor-backup-for-linstor-controller-db7fbfd95-zsfmm\n</code></pre>"},{"location":"how-to/restore-linstor-db/#temporarily-stop-the-linstor-controller-deployment","title":"Temporarily stop the LINSTOR Controller Deployment","text":"<p>To safely restore the database, ensure that the LINSTOR Controller is shut down by scaling the Piraeus Operator and LINSTOR Controller deployment to 0 replicas:</p> <pre><code>$ kubectl scale deployment piraeus-operator-controller-manager --replicas 0\ndeployment.apps/piraeus-operator-controller-manager scaled\n$ kubectl scale deployment linstor-controller --replicas 0\ndeployment.apps/linstor-controller scaled\n</code></pre>"},{"location":"how-to/restore-linstor-db/#create-a-new-backup-of-the-current-cluster-state","title":"Create a New Backup of the Current Cluster State","text":"<p>Since the restore process is destructive, first create a backup of the current database:</p> <pre><code>$ mkdir backup\n$ cd backup\n$ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty kubectl get crds -oyaml &gt; crds.yaml\n$ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty -I {} sh -c 'kubectl get {} -oyaml &gt; {}.yaml'\n</code></pre>"},{"location":"how-to/restore-linstor-db/#restore-the-database","title":"Restore the Database","text":"<p>Copy and unpack the selected backup to a local directory by using the following commands:</p> <pre><code>$ mkdir restore\n$ cd restore\n# Replace $BACKUP_NAME with your selected backup name\n$ kubectl get secrets --sort-by=.metadata.name -l piraeus.io/backup=$BACKUP_NAME -ogo-template='{{range .items}}{{index .data \"backup.tar.gz\" | base64decode}}{{end}}' &gt; backup.tar.gz\n$ tar -xvf backup.tar.gz\ncrds.yaml\n[...]\n</code></pre> <p>Then, replace the current database with the database from the backup:</p> <pre><code>$ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty kubectl delete crds\n$ kubectl create -f .\n</code></pre>"},{"location":"how-to/restore-linstor-db/#restart-the-linstor-controller-deployment","title":"Restart the LINSTOR Controller Deployment","text":"<p>Now we can safely restart the Piraeus Operator and LINSTOR Controller Deployment.</p> <pre><code>$ kubectl scale deployment piraeus-operator-controller-manager --replicas 1\ndeployment.apps/piraeus-operator-controller-manager scaled\n$ kubectl scale deployment linstor-controller --replicas 1\ndeployment.apps/linstor-controller scaled\n$ kubectl rollout status deployment piraeus-operator-controller-manager\nWaiting for deployment \"piraeus-operator-controller-manager\" rollout to finish: 0 of 1 updated replicas are available...\ndeployment \"piraeus-operator-controller-manager\" successfully rolled out\n$ kubectl rollout status deployment linstor-controller\nWaiting for deployment \"linstor-controller\" rollout to finish: 0 of 1 updated replicas are available...\ndeployment \"linstor-controller\" successfully rolled out\n</code></pre>"},{"location":"how-to/secure-boot/","title":"How to Load DRBD with SecureBoot Enabled","text":"<p>This guide shows you how to use the DRBD\u00ae Module Loader on machines with SecureBoot enabled.</p> <p>When SecureBoot is enabled the Linux Kernel refuses to load unsigned kernel modules. Since the DRBD modules are built from source, they do not have a valid signature by default. To load them, they need to be signed, and the signing key needs to be inserted into the machine's trust store.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>generating key material with <code>openssl</code>.</li> <li>managing machine owner keys with <code>mokutil</code>.</li> <li>creating and protecting Kubernetes Secret resources.</li> </ul>"},{"location":"how-to/secure-boot/#prerequisites","title":"Prerequisites","text":"<ul> <li>A Kubernetes node running with SecureBoot enabled. This can be checked by running the following command on each node:   <pre><code># mokutil --sb-state\nSecureBoot enabled\n</code></pre></li> <li>Console access to the machine during early boot, or permissions to update the EFI platform keys another way.</li> </ul>"},{"location":"how-to/secure-boot/#generate-key-material","title":"Generate Key Material","text":"<p>Create a private key and self-signed certificate using the <code>openssl</code> command line utility. The following command will create a new private key named <code>signing_key.pem</code> and a certificate named <code>signing_key.x509</code>, valid for 10 years, in the appropriate format:</p> <pre><code>$ openssl req -x509 -new -nodes -utf8 -sha256 -days 36500 -batch -outform DER \\\n    -out signing_key.x509 -keyout signing_key.pem -config - &lt;&lt;EOF\n[ req ]\ndefault_bits = 4096\ndistinguished_name = req_distinguished_name\nprompt = no\nstring_mask = utf8only\nx509_extensions = myexts\n\n[ req_distinguished_name ]\nO = Piraeus Datastore\nCN = Piraeus Datastore kernel module signing key\nemailAddress = piraeus-signing-key@example.com\n\n[ myexts ]\nbasicConstraints=critical,CA:FALSE\nkeyUsage=digitalSignature\nsubjectKeyIdentifier=hash\nauthorityKeyIdentifier=keyid\nEOF\n</code></pre>"},{"location":"how-to/secure-boot/#enroll-the-certificate-in-the-machine-trust-store","title":"Enroll the Certificate in the Machine Trust Store","text":"<p>The generated certificate needs to be added to the machine's trust store. This step depends on the machine platform you are using. The instructions here apply to any system where you have console access during early boot, such as bare-metal or most virtualization platforms.</p> <p>First, distribute the generated certificate <code>signing_key.x509</code> to all nodes. Then, use the following command to add the certificate to the machine owner keys (MOK) using a password of your choice:</p> <pre><code># mokutil --import signing_key.x509\ninput password:\ninput password again:\n</code></pre> <p>To enable the keys, start a console session on the machine, either by directly attching a keyboard and monitor, attaching a virtual console using the machines BMC, or using tools of your virtualization platform such as virt-viewer or VNC.</p> <p>Then, reboot the machine, chosing to \"Perform MOK management\" when promted. Now: * Select \"Enroll MOK\":</p> <p> * Continue enrollment of the key:</p> <p> * Enter the password chosen when running <code>mokutil --import</code>:</p> <p> * Reboot the machine:</p> <p></p>"},{"location":"how-to/secure-boot/#sign-the-drbd-module-using-the-created-key-material","title":"Sign the DRBD Module Using the Created Key Material","text":"<p>Create a Kubernetes Secret resource containing the generated key material. The following command creates a secret named <code>drbd-signing-keys</code>:</p> <pre><code>$ kubectl create secret generic drbd-signing-keys --type piraeus.io/signing-key \\\n    --from-file=signing_key.pem --from-file=signing_key.x509\nsecret/drbd-signing-keys created\n</code></pre> <p>Now, configure the <code>drbd-module-loader</code> to use the key material to sign the kernel modules. The following <code>LinstorSatelliteConfiguration</code> resource makes the key available in the <code>drbd-module-loader</code> container available and sets the <code>LB_SIGN</code> environment variable to start signing the modules:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: drbd-module-signing\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n      - name: drbd-module-loader\n        env:\n        - name: LB_SIGN\n          value: /signing-key\n        volumeMounts:\n        - name: signing-key\n          mountPath: /signing-key\n          readOnly: true\n      volumes:\n      - name: signing-key\n        secret:\n          secretName: drbd-signing-keys\n</code></pre>"},{"location":"how-to/secure-boot/#verifying-success","title":"Verifying Success","text":"<p>When everything is configured correctly, the <code>drbd-module-loader</code> init container will be able to insert the DRBD modules.</p> <pre><code>$ kubectl logs ds/linstor-satellite.node1.example.com drbd-module-loader\n...\nDRBD version loaded:\nversion: 9.2.8 (api:2/proto:86-122)\nGIT-hash: e163b05a76254c0f51f999970e861d72bb16409a build by @linstor-satellite.k8s-21.test-zskzl, 2024-04-03 09:04:15\nTransports (api:20): tcp (9.2.8) lb-tcp (9.2.8) rdma (9.2.8)\n</code></pre> <p>If the modules are not signed, or the signature is not trusted, the <code>drbd-module-loader</code> container will crash with one of the following error messages:</p> <pre><code>insmod: ERROR: could not insert module ./drbd.ko: Operation not permitted\ninsmod: ERROR: could not insert module ./drbd_transport_tcp.ko: Operation not permitted\ninsmod: ERROR: could not insert module ./drbd_transport_lb-tcp.ko: Operation not permitted\n\nCould not load DRBD kernel modules\n</code></pre> <pre><code>insmod: ERROR: could not insert module ./drbd.ko: Key was rejected by service\ninsmod: ERROR: could not insert module ./drbd_transport_tcp.ko: Key was rejected by service\ninsmod: ERROR: could not insert module ./drbd_transport_lb-tcp.ko: Key was rejected by service\n\nCould not load DRBD kernel modules\n</code></pre> <pre><code>insmod: ERROR: could not insert module ./drbd.ko: Required key not available\ninsmod: ERROR: could not insert module ./drbd_transport_tcp.ko: Required key not available\ninsmod: ERROR: could not insert module ./drbd_transport_lb-tcp.ko: Required key not available\n\nCould not load DRBD kernel modules\n</code></pre> <p>Additional information is available in the kernel logs:</p> <pre><code>$ dmesg\n...\n# The module is not signed. Check that the LB_SIGN environment variable is set in the container.\nLockdown: insmod: unsigned module loading is restricted; see man kernel_lockdown.7\n# The module is signed, but the signing key is not in the machine's trust store.\n# Check the enrolled keys using \"mokutil --list-enrolled\".\nPKCS#7 signature not signed with a trusted key\n</code></pre>"},{"location":"how-to/talos/","title":"How to Load DRBD on Talos Linux","text":"<p>This guide shows you how to set the DRBD\u00ae Module Loader when using Talos Linux.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the <code>talosctl</code> command line to to access Talos Linux nodes.</li> <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li> </ul>"},{"location":"how-to/talos/#configure-talos-system-extension-for-drbd","title":"Configure Talos system extension for DRBD","text":"<p>By default, the DRBD Module Loader will try to find the necessary header files to build DRBD from source on the host system. In Talos Linux these header files are not included in the host system. Instead, the Kernel modules is packed into a system extension.</p> <p>Ensure Talos has the correct <code>drbd</code> system extension loaded for the running Kernel.</p> <p>This is done by building a install image from the talos factory with drbd included</p> <p>You will also need to update the machine config to set the following kernel module parameters:</p> <pre><code>machine:\n  kernel:\n    modules:\n      - name: drbd\n        parameters:\n          - usermode_helper=disabled\n      - name: drbd_transport_tcp\n</code></pre> <p>Validate <code>drbd</code> module is loaded: <pre><code>$ talosctl -n &lt;NODE_IP&gt; read /proc/modules\ndrbd_transport_tcp 28672 - - Live 0xffffffffc046c000 (O)\ndrbd 643072 - - Live 0xffffffffc03b9000 (O)\n</code></pre></p> <p>Validate <code>drbd</code> module parameter <code>usermode_helper</code> is set to <code>disabled</code>: <pre><code>$ talosctl -n &lt;NODE_IP&gt; read /sys/module/drbd/parameters/usermode_helper\ndisabled\n</code></pre></p>"},{"location":"how-to/talos/#configure-the-drbd-module-loader","title":"Configure the DRBD Module Loader","text":"<p>To change the DRBD Module Loader, so that it uses the modules provided by system extension, apply the following <code>LinstorSatelliteConfiguration</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: talos-loader-override\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-shutdown-guard\n          $patch: delete\n        - name: drbd-module-loader\n          $patch: delete\n      volumes:\n        - name: run-systemd-system\n          $patch: delete\n        - name: run-drbd-shutdown-guard\n          $patch: delete\n        - name: systemd-bus-socket\n          $patch: delete\n        - name: lib-modules\n          $patch: delete\n        - name: usr-src\n          $patch: delete\n        - name: etc-lvm-backup\n          hostPath:\n            path: /var/etc/lvm/backup\n            type: DirectoryOrCreate\n        - name: etc-lvm-archive\n          hostPath:\n            path: /var/etc/lvm/archive\n            type: DirectoryOrCreate\n</code></pre> <p>Explanation:</p> <ul> <li><code>/etc/lvm/*</code> is read-only in Talos and therefore can't be used. Let's use <code>/var/etc/lvm/*</code> instead.</li> <li>Talos does not ship with Systemd, so everything Systemd related needs to be removed</li> <li><code>/usr/lib/modules</code> and <code>/usr/src</code> are not needed as the Kernel module is already compiled and needs just to be used.</li> </ul>"},{"location":"how-to/upgrade/","title":"Upgrading Piraeus Operator from Version 1 to Version 2","text":"<p>The following document guides you through the upgrade process for Piraeus Operator from version 1 (\"v1\") to version 2 (\"v2\").</p> <p>Piraeus Operator v2 offers improved convenience and customization. This however made it necessary to make significant changes to the way Piraeus Operator manages Piraeus Datastore. As such, upgrading from v1 to v2 is a procedure requiring manual oversight.</p> <p>Upgrading Piraeus Operator is done in four steps:</p> <ul> <li>Step 1: (Optional) Migrate the LINSTOR database to use the <code>k8s</code> backend.</li> <li>Step 2: Collect information about the current deployment.</li> <li>Step 3: Remove the Piraeus Operator v1 deployment, keeping existing volumes untouched.</li> <li>Step 4: Deploy Piraeus Operator v2 using the information gathered in step 2.</li> </ul>"},{"location":"how-to/upgrade/#prerequisites","title":"Prerequisites","text":"<p>This guide assumes:</p> <ul> <li>You used Helm to create the original deployment and are familiar with upgrading Helm deployments.</li> <li>Your Piraeus Datastore deployment is up-to-date with the latest v1 release. Check the releases here.</li> <li>You have the following command line tools available:</li> <li><code>kubectl</code></li> <li><code>helm</code></li> <li><code>jq</code></li> <li>You are familiar with the <code>linstor</code> command line utility, specifically to verify the cluster state.</li> </ul>"},{"location":"how-to/upgrade/#key-changes-between-operator-v1-and-v2","title":"Key Changes Between Operator V1 and V2","text":""},{"location":"how-to/upgrade/#administrative-changes","title":"Administrative Changes","text":"<ul> <li>The resources <code>LinstorController</code>, <code>LinstorSatelliteSet</code> and <code>LinstorCSIDriver</code> have been replaced by   <code>LinstorCluster</code> and   <code>LinstorSatelliteConfgiuration</code>.</li> <li>The default deployment runs the LINSTOR Satellite in the container network.   The migration script will propose changing to the host network.</li> </ul>"},{"location":"how-to/upgrade/#operational-changes","title":"Operational Changes","text":"<ul> <li>In Operator v1, all labels on the Kubernetes node resource were replicated on the satellite, making them usable in the   <code>replicasOnSame</code> and <code>replicasOnDifferent</code> parameters on the storage class. In Operator v2, only the following   labels are automatically synchronized.</li> <li><code>kubernetes.io/hostname</code></li> <li><code>topology.kubernetes.io/region</code></li> <li><code>topology.kubernetes.io/zone</code>   Use <code>LinstorSatelliteConfiguration.spec.properties</code>   to synchronize additional labels.</li> <li>The following settings are applied by Operator v2 cluster-wide:</li> <li>DrbdOptions/Net/rr-conflict: retry-connect</li> <li>DrbdOptions/Resource/on-suspended-primary-outdated: force-secondary</li> <li>DrbdOptions/Resource/on-no-data-accessible: suspend-io</li> <li>DrbdOptions/auto-quorum: suspend-io</li> <li>Operator v2 also includes a High-Availability Controller   deployment to prevent stuck nodes caused by suspended DRBD devices.</li> </ul>"},{"location":"how-to/upgrade/1-migrate-database/","title":"Migrating the LINSTOR Controller Database to Use the <code>k8s</code> Backend","text":"<p>This document guides you through the process of migrating an existing LINSTOR\u00ae Cluster to use the <code>k8s</code> database backend.</p> <p>This is the optional first step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"how-to/upgrade/1-migrate-database/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> </ul>"},{"location":"how-to/upgrade/1-migrate-database/#when-to-migrate-the-linstor-controller-database-to-the-k8s-backend","title":"When to Migrate the LINSTOR Controller Database to the <code>k8s</code> Backend","text":"<p>LINSTOR can use different database backends to store important state, such as the available volumes and where they are deployed. The available backends are:</p> <ul> <li>An H2 database stored in a local file on the controller.</li> <li>A compatible database server, such as MySQL or PostgreSQL.</li> <li>An etcd cluster.</li> <li>An <code>k8s</code> backend, using Custom Resources to store the cluster state directly in the Kubernetes API.</li> </ul> <p>Of these backends, only the <code>k8s</code> backend works without any additional components when running in the Kubernetes cluster.</p> <p>Because the Piraeus Operator v1 is older than the LINSTOR <code>k8s</code> backend, the default for a long time was the use of a separate etcd cluster, deployed by default when using Piraeus Operator v1. Since then, etcd proved to be difficult to maintain, often requiring manual intervention.</p> <p>Because of this, consider migrating away from separate etcd cluster to using the <code>k8s</code> backend.</p> <p>If you already use one of the other backends, no migration is necessary. You can check the currently used backend of your LINSTOR cluster by running the following command:</p> <pre><code>$ kubectl exec deploy/piraeus-op-cs-controller -- cat /etc/linstor/linstor.toml\n[db]\n  connection_url = \"etcd://piraeus-op-etcd:2379\"\n</code></pre> <p>If the <code>connection_url</code> value starts with <code>etcd://</code> you are using the etcd backend and should consider migrating.</p>"},{"location":"how-to/upgrade/1-migrate-database/#migrating-the-linstor-controller-database","title":"Migrating the LINSTOR Controller Database","text":"<p>During the migration, the LINSTOR Controller needs to be stopped. This means that provisioning and deletion of volumes will not work for the duration of the migration. Existing volumes will continue working normally.</p>"},{"location":"how-to/upgrade/1-migrate-database/#1-stop-the-linstor-controller","title":"1. Stop the LINSTOR Controller","text":"<p>To prevent unwanted modifications to the database during the migration, you need to stop the LINSTOR Controller. To stop the LINSTOR Controller, set the expected replicas for the controller to zero.</p> <p>First, find the currently deployed Piraeus Datastore release. For this guide, it is 1.10.8:</p> <pre><code>$ helm list\nNAME        NAMESPACE          REVISION  UPDATED                                 STATUS    CHART           APP VERSION\npiraeus-op  piraeus-datastore  1         2023-11-07 10:30:44.184389038 +0100 CET deployed  piraeus-1.10.8  1.10.8\n</code></pre> <p>Then change the deployment to deploy no replicas for the LINSTOR Controller. Ensure to check out the chart version currently deployed, so that no accidental upgrade happens:</p> <pre><code>$ git checkout v1.10.8\n$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set operator.controller.replicas=0\n$ kubectl rollout status deploy/piraeus-op-cs-controller -w\ndeployment \"piraeus-op-cs-controller\" successfully rolled out\n</code></pre>"},{"location":"how-to/upgrade/1-migrate-database/#2-prepare-a-pod-for-running-the-migration","title":"2. Prepare a Pod for Running the Migration","text":"<p>To run the migration, you need access to the <code>linstor-database</code> tool, which comes preinstalled with the LINSTOR Controller image. The following command displays the LINSTOR Controller image, the name of the ConfigMap storing the LINSTOR Configuration, and the service account for LINSTOR Controller. Take note of them, as they will be used for the migration Pod.</p> <pre><code>$ kubectl get deploy/piraeus-op-cs-controller --output=jsonpath='IMAGE={$.spec.template.spec.containers[?(@.name==\"linstor-controller\")].image}{\"\\n\"}CONFIG_MAP={$.spec.template.spec.volumes[?(@.name==\"linstor-conf\")].configMap.name}{\"\\n\"}SERVICE_ACCOUNT={$.spec.template.spec.serviceAccountName}{\"\\n\"}'\nIMAGE=quay.io/piraeusdatastore/piraeus-server:v1.24.2\nCONFIG_MAP=piraeus-op-cs-controller-config\nSERVICE_ACCOUNT=linstor-controller\n</code></pre> <p>Using the information from the LINSTOR Controller deployment, create a Pod used during the migration process. Replace <code>$IMAGE</code>, <code>$CONFIG_MAP</code> and <code>$SERVICE_ACCOUNT</code> with the appropriate values.</p> <pre><code>apiVersion: v1\nkind: Pod\nmetadata:\n  name: linstor-database-migration\nspec:\n  serviceAccountName: $SERVICE_ACCOUNT\n  containers:\n    - name: backup\n      image: $IMAGE\n      command:\n        - /bin/bash\n        - -c\n        - \"sleep infinity\"\n      volumeMounts:\n        - name: linstor-conf\n          mountPath: /etc/linstor\n          readOnly: true\n        - name: backup\n          mountPath: /backup\n        - name: logs\n          mountPath: /logs\n  volumes:\n    - name: backup\n      emptyDir: {}\n    - name: logs\n      emptyDir: {}\n    - name: linstor-conf\n      configMap:\n        name: $CONFIG_MAP\n</code></pre>"},{"location":"how-to/upgrade/1-migrate-database/#3-create-a-database-backup","title":"3. Create a Database Backup","text":"<p>Using the newly created migration Pod, create a database backup using the <code>linstor-database</code> tool.</p> <pre><code>$ kubectl exec linstor-database-migration -- /usr/share/linstor-server/bin/linstor-database export-db -c /etc/linstor /backup/backup-before-migration.json\nLoading configuration file \"/etc/linstor/linstor.toml\"\n15:22:55.684 [main] INFO LINSTOR/linstor-db -- SYSTEM - ErrorReporter DB first time init.\n15:22:55.685 [main] INFO LINSTOR/linstor-db -- SYSTEM - Log directory set to: './logs'\n15:22:56.417 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\"\n15:22:56.418 [main] INFO LINSTOR/linstor-db -- SYSTEM - Extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\" is not installed\n15:22:56.418 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\"\n15:22:56.426 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\" was successful\n15:22:56.427 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\"\n15:22:56.429 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\" was successful\n15:22:57.666 [main] INFO LINSTOR/linstor-db -- SYSTEM - Initializing the etcd database\n15:22:57.667 [main] INFO LINSTOR/linstor-db -- SYSTEM - etcd connection URL is \"etcd://piraeus-op-etcd:2379\"\n15:22:59.480 [main] INFO LINSTOR/linstor-db -- SYSTEM - Export finished\n</code></pre> <p>Then, copy the just created backup to permanent storage, so that it is not lost should the migration pod restart:</p> <pre><code>$ kubectl cp linstor-database-migration:/backup/backup-before-migration.json backup-before-migration.json\n</code></pre>"},{"location":"how-to/upgrade/1-migrate-database/#4-update-the-linstor-configuration-to-point-to-the-new-database-backend","title":"4. Update the LINSTOR Configuration to Point to the New Database Backend","text":"<p>After creating and storing the backup it is safe to change the LINSTOR configuration. This is done by running another <code>helm upgrade</code>, changing the database configuration for the LINSTOR Controller. Once again, ensure that you apply the chart version currently deployed, so that no accidental upgrade happens:</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set operator.controller.dbConnectionURL=k8s\n</code></pre> <p>This will also change the configuration in the <code>linstor-database-migration</code> Pod, but it might need some time to propagate. Eventually, you will see the <code>k8s</code> database connection:</p> <pre><code>$ kubectl exec linstor-database-migration -- cat /etc/linstor/linstor.toml\n[db]\n  connection_url = \"k8s\"\n</code></pre>"},{"location":"how-to/upgrade/1-migrate-database/#5-import-the-database-from-the-backup","title":"5. Import the Database from the Backup","text":"<p>After changing the configuration, you can again use the <code>linstor-database</code> tool to restore the database backup to the new backend.</p> <pre><code>$ kubectl exec linstor-database-migration -- /usr/share/linstor-server/bin/linstor-database import-db -c /etc/linstor /backup/backup-before-migration.json\nLoading configuration file \"/etc/linstor/linstor.toml\"\n15:39:41.270 [main] INFO LINSTOR/linstor-db -- SYSTEM - ErrorReporter DB version 1 found.\n15:39:41.272 [main] INFO LINSTOR/linstor-db -- SYSTEM - Log directory set to: './logs'\n15:39:41.848 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\"\n15:39:41.849 [main] INFO LINSTOR/linstor-db -- SYSTEM - Extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\" is not installed\n15:39:41.850 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\"\n15:39:41.858 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\" was successful\n15:39:41.859 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\"\n15:39:41.860 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\" was successful\n15:39:43.307 [main] INFO LINSTOR/linstor-db -- SYSTEM - Initializing the k8s crd database connector\n15:39:43.307 [main] INFO LINSTOR/linstor-db -- SYSTEM - Kubernetes-CRD connection URL is \"k8s\"\n15:40:22.418 [main] INFO LINSTOR/linstor-db -- SYSTEM - Import finished\n</code></pre>"},{"location":"how-to/upgrade/1-migrate-database/#6-start-the-linstor-controller","title":"6. Start the LINSTOR Controller","text":"<p>Now that the new database backend is initialized, it is safe to start the LINSTOR Controller again. Simply change the number of replicas for the LINSTOR Controller back to the original value before starting the migration. Once again, ensure that you apply the chart version currently deployed, so that no accidental upgrade happens:</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set operator.controller.replicas=1\ndeployment \"piraeus-op-cs-controller\" successfully rolled out\n</code></pre> <p>Once the LINSTOR Controller is up and running, verify the state of your cluster: check all nodes and resource are in the expected state:</p> <pre><code>$ kubectl exec deploy/piraeus-op-cs-controller -- linstor node list\n$ kubectl exec deploy/piraeus-op-cs-controller -- linstor storage-pool list\n$ kubectl exec deploy/piraeus-op-cs-controller -- linstor resource list-volumes\n$ kubectl exec deploy/piraeus-op-cs-controller -- linstor error-reports list\n</code></pre>"},{"location":"how-to/upgrade/1-migrate-database/#7-clean-up-migration-resources","title":"7. Clean up Migration Resources","text":"<p>After successful migration, you can clean up left over resources.</p> <p>First, you can remove the <code>linstor-database-migration</code> Pod:</p> <pre><code>$ kubectl delete pod linstor-database-migration\n</code></pre> <p>Then, you can also remove the etcd deployment by upgrading the helm deployment, setting <code>etcd.enabled=false</code>:</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set etcd.enabled=false\n</code></pre>"},{"location":"how-to/upgrade/2-collect-information/","title":"Collect Information before Performing the Upgrade","text":"<p>Before performing the upgrade and removing the old deployment, collect information on the state of your cluster. This ensures the upgraded deployment will have a compatible configuration.</p> <p>This is the second step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"how-to/upgrade/2-collect-information/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> <li>Install <code>jq</code></li> </ul>"},{"location":"how-to/upgrade/2-collect-information/#run-the-data-collection-script","title":"Run the Data Collection Script","text":"<p>To collect the necessary information for the migration, run the script provided at <code>docs/how-to/upgrade/collect-operator-v1-information.sh</code>. You can run the script either from a checked out repository, or directly from GitHub:</p> <pre><code>$ curl --proto '=https' --tlsv1.2 -sSf \\\n  https://raw.githubusercontent.com/piraeusdatastore/piraeus-operator/v2/docs/how-to/upgrade/collect-operator-v1-information.sh \\\n  | bash -s\n</code></pre> <p>The script will ask you if you want to keep modifications made with the deployed Piraeus Operator. For each modification, the script will show you the proposed change to the deployed resources and ask for confirmation.</p> <p>In addition, it will also inform you about values that cannot automatically be migrated, along with recommended actions should you need to keep the modification. The output looks like this:</p> <pre><code>Using kubectl context: kubernetes-admin@kubernetes\nFound LinstorControllers: [\"piraeus-cs\"]\nFound LinstorSatelliteSets: [\"piraeus-ns\"]\nFound LinstorCSIDrivers: [\"piraeus\"]\nFound additional environment variables passed to LINSTOR Controller\n--- Default resource\n+++ Updated resource\n@@ -143,6 +143,12 @@ kind: Deployment\n       - args:\n         - startController\n         env:\n+        - name: FOO\n+          value: bar\n+        - name: EXAMPLE\n+          valueFrom:\n+            fieldRef:\n+              fieldPath: status.podIP\n         - name: JAVA_OPTS\n           value: -Djdk.tls.acknowledgeCloseNotify=true\n         - name: K8S_AWAIT_ELECTION_ENABLED\nApply the patch (Y/n)? y\n...\n---------------------------------------------------------------------------------------------\n| After upgrading, apply the following resources. They have been saved to v2-resources.yaml |\n---------------------------------------------------------------------------------------------\n\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  linstorPassphraseSecret: piraeus-passphrase\n  patches: []\n...\n</code></pre> <p>A copy of the identified resources is saved at <code>v2-resources.yaml</code>.</p>"},{"location":"how-to/upgrade/2-collect-information/#collect-helm-generated-secrets","title":"Collect Helm-Generated Secrets","text":"<p>Helm automatically generates a passphrase for LINSTOR. Once LINSTOR is initialized with the passphrase, the LINSTOR Controller will not be able fully start without supplying the passphrase.</p> <p>To migrate the generated passphrase to Piraeus Operator v2, create a backup of the secret:</p> <pre><code>$ kubectl get secrets piraeus-op-passphrase -ogo-template='{{.data.MASTER_PASSPHRASE}}{{\"\\n\"}}'\nZVRxanl1cVBscXV1ZTk1cmEwVTk5b0ptd0F4OGFmWlVPUVA0NWNnUw==\n</code></pre> <p>Save the generated passphrase for later use.</p>"},{"location":"how-to/upgrade/3-remove-operator-v1/","title":"Remove the Piraeus Operator v1 Deployment","text":"<p>Migrating to the new Piraeus Operator deployment requires temporarily removing the existing deployment.</p> <p>After this step no new volumes can be created and no existing volume can be attached or detached, until the new deployment is rolled out.</p> <p>This is the third step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"how-to/upgrade/3-remove-operator-v1/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> </ul>"},{"location":"how-to/upgrade/3-remove-operator-v1/#scale-down-the-operator-deployment","title":"Scale Down the Operator Deployment","text":"<p>To prevent modification of the existing cluster, scale down the existing Piraeus Operator deployment.</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --set operator.replicas=0\n$ kubectl rollout status -w deploy/piraeus-op-operator\ndeployment \"piraeus-op-operator\" successfully rolled out\n</code></pre>"},{"location":"how-to/upgrade/3-remove-operator-v1/#remove-the-finalizers-from-the-piraeus-resources","title":"Remove the Finalizers from the Piraeus Resources","text":"<p>The Operator sets Finalizers on the resource it controls. This prevents the deletion of these resources when the Operator is not running. Remove the Finalizers by applying a patch:</p> <pre><code>$ kubectl patch linstorsatellitesets piraeus-op-ns --type merge --patch '{\"metadata\": {\"finalizers\": []}}'\nlinstorsatelliteset.piraeus.linbit.com/piraeus-op-ns patched\n$ kubectl patch linstorcontrollers piraeus-op-cs --type merge --patch '{\"metadata\": {\"finalizers\": []}}'\nlinstorcontroller.piraeus.linbit.com/piraeus-op-cs patched\n</code></pre>"},{"location":"how-to/upgrade/3-remove-operator-v1/#remove-the-piraeus-resources","title":"Remove the Piraeus Resources","text":"<p>Having removed the Finalizers, you can delete the Piraeus Resources. This will stop the LINSTOR Cluster, and no new volumes can be created, and existing volumes will not attach or detach. Volumes already attached to a Pod will continue to replicate.</p> <pre><code>$ kubectl delete linstorcsidrivers/piraeus-op\n$ kubectl delete linstorsatellitesets/piraeus-op-ns\n$ kubectl delete linstorcontrollers/piraeus-op-cs\n</code></pre>"},{"location":"how-to/upgrade/3-remove-operator-v1/#remove-the-piraeus-deployment","title":"Remove the Piraeus Deployment","text":"<p>As a last step, you can completely remove the helm deployment, deleting additional resources such as service accounts and RBAC resources. In addition, also clean up the Custom Resource Definitions:</p> <pre><code>$ helm uninstall piraeus-op\n$ kubectl delete crds linstorcsidrivers.piraeus.linbit.com linstorsatellitesets.piraeus.linbit.com linstorcontrollers.piraeus.linbit.com\n</code></pre>"},{"location":"how-to/upgrade/3-remove-operator-v1/#optional-remove-additional-piraeus-components","title":"Optional: Remove additional Piraeus Components","text":"<p>If you have deployed additional components from Piraeus, such as the HA Controller or LINSTOR Affinity Controller, you will need to remove them, too. After completing the migration, you can install them again, if needed.</p> <pre><code>$ helm uninstall piraeus-ha-controller\n$ helm uninstall linstor-affinity-controller\n</code></pre>"},{"location":"how-to/upgrade/4-install-operator-v2/","title":"Install Piraeus Operator v2","text":"<p>After removing the Piraeus Operator v1 deployment, you can install Piraeus Operator v2.</p> <p>You can either use the <code>kubectl</code> method to deploy Piraeus Operator, or alternatively deploy the Operator using Helm.</p> <p>This is the last step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"how-to/upgrade/4-install-operator-v2/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> </ul>"},{"location":"how-to/upgrade/4-install-operator-v2/#deploy-piraeus-operator-v2-using-kubectl","title":"Deploy Piraeus Operator v2 Using <code>kubectl</code>","text":"<p>You can use <code>kubectl</code> and the built-in <code>kustomize</code> feature to deploy Piraeus Operator v2.</p> <p>First, create a file named <code>kustomization.yaml</code>, referencing the latest Piraeus Operator release, and the namespace you which to deploy the Piraeus Operator in. The latest releases are available  on the release page.</p> <p>In the example below, the version is <code>v2.3.0</code>, and the namespace is <code>piraeus-datastore</code>.</p> <pre><code>apiVersion: kustomize.config.k8s.io/v1beta1\nkind: Kustomization\nresources:\n  - https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.3.0 # Change the version here\nnamespace: piraeus-datastore # Change the namespace here\n</code></pre> <p>Then, deploy the Operator using <code>kubectl</code> and wait for the deployment to complete:</p> <pre><code>$ kubectl apply -k . --server-side\n$ kubectl rollout status -n piraeus-datastore -w deploy/piraeus-operator-controller-manager\n</code></pre>"},{"location":"how-to/upgrade/4-install-operator-v2/#deploy-piraeus-operator-v2-using-helm","title":"Deploy Piraeus Operator v2 Using Helm","text":"<p>To deploy Piraeus Operator v2 using Helm, clone the latest v2 release of Piraeus. The latest releases are available on the release page.</p> <p>To also install the necessary Custom Resource Definitions for Piraeus, set <code>installCRDs</code> to <code>true</code>.</p> <pre><code>$ git clone -b v2.3.0 https://github.com/piraeusdatastore/piraeus-operator.git\n$ cd piraeus-operator\n$ helm install piraeus-operator charts/piraeus --set installCRDs=true\n</code></pre>"},{"location":"how-to/upgrade/4-install-operator-v2/#deploy-the-piraeus-datastore-cluster","title":"Deploy the Piraeus Datastore Cluster","text":"<p>Once the Operator is deployed, deploy the Cluster using the generated resources from step 2.</p> <p>First, create the secret used for the LINSTOR passphrase collected at the end of step 2.</p> <pre><code>$ cat &lt;&lt;-EOF | kubectl apply -f - --server-side\napiVersion: v1\nkind: Secret\nmetadata:\n  name: piraeus-op-passphrase\n  namespace: piraeus-datastore # Change the namespace here\ndata:\n  MASTER_PASSPHRASE: ZVRxanl1cVBscXV1ZTk1cmEwVTk5b0ptd0F4OGFmWlVPUVA0NWNnUw==\nEOF\n</code></pre> <p>Then, apply the resource generated by the script from step 2:</p> <pre><code>$ kubectl apply -f v2-resources.yaml --server-side\nlinstorcluster.piraeus.io/linstorcluster created\nlinstorsatelliteconfiguration.piraeus.io/host-networking created\nlinstorsatelliteconfiguration.piraeus.io/piraeus-op-ns created\n</code></pre> <p>Now the cluster will come up, using the existing data to restore the cluster state.</p>"},{"location":"how-to/upgrade/4-install-operator-v2/#verifying-cluster-state","title":"Verifying Cluster State","text":"<p>You can check the Cluster state by using the <code>linstor</code> command line client:</p> <pre><code>$ kubectl exec deploy/linstor-controller -- linstor node list\n$ kubectl exec deploy/linstor-controller -- linstor storage-pool list\n$ kubectl exec deploy/linstor-controller -- linstor resource list-volumes\n$ kubectl exec deploy/linstor-controller -- linstor error-reports list\n</code></pre> <p>You can also provision new volumes, to verify that the cluster is operational.</p>"},{"location":"how-to/upgrade/UPGRADE/","title":"General notes","text":"<p>During the upgrade process, provisioning of volumes and attach/detach operations might not work. Existing volumes and volumes already in use by a pod will continue to work without interruption.</p> <p>To upgrade, apply the resource of the latest release. Use the same method that was used to create the initial deployment (<code>kubectl</code> vs <code>helm</code>). There is no need to change existing <code>LinstorCluster</code>, <code>LinstorSatelliteConfiguration</code> or <code>LinstorNodeConnection</code> resources.</p> <p>To upgrade to the latest release using <code>kubectl</code>, run the following commands:</p> <pre><code>$ kubectl apply --server-side -k \"https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.7.1\"\n$ kubectl wait pod --for=condition=Ready -n piraeus-datastore --all\n</code></pre>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v26-to-v27","title":"Upgrades from v2.6 to v2.7","text":"<p>Generally, no special steps required.</p> <p>LINSTOR Satellites now try to automatically detect the LVM configuration on the host. Any patch targeting the Satellites /etc/lvm/lvm.conf file may need to be adapted.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v25-to-v26","title":"Upgrades from v2.5 to v2.6","text":"<p>No special steps required.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v24-to-v25","title":"Upgrades from v2.4 to v2.5","text":"<p>No special steps required.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v23-to-v24","title":"Upgrades from v2.3 to v2.4","text":"<p>Generally, no special steps required.</p> <p>LINSTOR Satellites are now managed via DaemonSet resources. Any patch targeting a <code>satellite</code> Pod resources is automatically converted to the equivalent DaemonSet resource patch. In the Pod list, you will see these Pods using a new <code>linstor-satellite</code> prefix.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v22-to-v23","title":"Upgrades from v2.2 to v2.3","text":"<p>Removed the <code>NetworkPolicy</code> resource from default deployment. It can be reapplied as a separate step.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v21-to-v22","title":"Upgrades from v2.1 to v2.2","text":"<p>Removed the dependency on cert-manager for the initial deployment. To clean up an existing <code>Certificate</code> resource, run the following commands:</p> <pre><code>$ kubectl delete certificate -n piraeus-datastore piraeus-operator-serving-cert\n</code></pre>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v20-to-v21","title":"Upgrades from v2.0 to v2.1","text":"<p>No special steps required.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrades-from-v1-to-v2","title":"Upgrades from v1 to v2","text":"<p>Please follow the specialized upgrade guides.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v19-to-v110","title":"Upgrade from v1.9 to v1.10","text":"<p>If you want to share DRBD configuration directories with the host, please update the CRDs before upgrading using helm:</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v18-to-v19","title":"Upgrade from v1.8 to v1.9","text":"<p>If you want to protect metrics endpoints, take a look on guide on enabling rbac-proxy sidecars.</p> <p>We've also disabled the <code>haController</code> component in our chart. The replacement is available from artifacthub.io, containing much needed improvements in robustness and fail-over speed. If you want to still use the old version, set <code>haController.enabled=true</code>.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v17-to-v18","title":"Upgrade from v1.7 to v1.8","text":"<p>If you need to set the number of worker threads, or you need to set the log level of LINSTOR components, please update the CRDs before upgrading using helm:</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre> <p>In case if you have SSL enabled installation, you need to regenerate your certificates in PEM format. Read the guide on securing the deployment and repeat the described steps.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v16-to-v17","title":"Upgrade from v1.6 to v1.7","text":"<p>Node labels are now automatically applied to LINSTOR satellites as \"Auxiliary Properties\". That means you can reuse your existing Kubernetes Topology information (for example <code>topology.kubernetes.io/zone</code> labels) when scheduling volumes using the <code>replicasOnSame</code> and <code>replicasOnDifferent</code> settings. However, this also means that the Operator will delete any existing auxiliary properties that were already applied. To apply auxiliary properties to satellites, you have to apply a label to the Kubernetes node object.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v15-to-v16","title":"Upgrade from v1.5 to v1.6","text":"<p>The <code>csi-snapshotter</code> subchart was removed from this repository. Users who relied on it for their snapshot support should switch to the seperate charts provided by the Piraeus team on artifacthub.io The new charts also include notes on how to upgrade to newer CRD versions.</p> <p>To support the new <code>csi.kubeletPath</code> option an update to the LinstorCSIDriver CRD is required:</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v14-to-v15","title":"Upgrade from v1.4 to v1.5","text":"<p>To make use of the new <code>monitoringImage</code> value in the LinstorSatelliteSet CRD, you need to replace the existing CRDs before running the upgrade. If the CRDs are not upgraded, the operator will not deploy the monitoring container alongside the satellites.</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre> <p>Then run the upgrade:</p> <pre><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;\n</code></pre>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v13-to-v14","title":"Upgrade from v1.3 to v1.4","text":"<p>No special steps required, unless using the newly introduced <code>additionalEnv</code> and <code>additionalProperties</code> overrides.</p> <p>If you plan to use the new overrides, replace the CustomResourceDefinitions before running the upgrade</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre> <p>Then run the upgrade:</p> <pre><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;\n</code></pre>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v12-to-v13","title":"Upgrade from v1.2 to v1.3","text":"<p>No special steps required. After checking out the new repo, run a simple helm upgrade:</p> <pre><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;\n</code></pre>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v11-to-v12","title":"Upgrade from v1.1 to v1.2","text":"<p>Piraeus v1.2 is supported on Kubernetes 1.17+. If you are using an older Kubernetes distribution, you may need to change the default settings (for example the CSI provisioner)</p> <p>To start the upgrade process, ensure you have a backup of the LINSTOR Controller database. If you are using the etcd deployment included in Piraeus, you can create a backup using:</p> <pre><code>kubectl exec piraeus-op-etcd-0 -- etcdctl snapshot save /tmp/save.db\nkubectl cp piraeus-op-etcd-0:/tmp/save.db save.db\n</code></pre> <p>Now you can start the upgrade process. Simply run <code>helm upgrade piraeus-op ./charts/piraeus</code>. If you installed Piraeus with customization, pass the same options you used for <code>helm install</code> to <code>helm upgrade</code>. This will cause the operator pod to be re-created and shortly after all other Piraeus pods.</p> <p>There is a known issue when updating the CSI components: the pods will not be updated to the newest image and the <code>errors</code> section of the LinstorCSIDrivers resource shows an error updating the DaemonSet. In this case, manually delete <code>deployment/piraeus-op-csi-controller</code> and <code>daemonset/piraeus-op-csi-node</code>. They will be re-created by the operator.</p> <p>After a short wait, all pods should be running and ready. Check that no errors are listed in the status section of LinstorControllers, LinstorSatelliteSets and LinstorCSIDrivers.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-from-v10-to-v11","title":"Upgrade from v1.0 to v1.1","text":"<ul> <li>The LINSTOR controller image given in <code>operator.controller.controllerImage</code> has to have   its entrypoint set to <code>k8s-await-election v0.2.0</code>   or newer. All images starting with <code>piraeus-server:v1.8.0</code> meet this requirement.</li> </ul> <p>Older images will not work, as the <code>Service</code> will not automatically pick up on the active pod.</p> <p>To upgrade, first update the deployed LINSTOR image to a compatible version, then upgrade the   operator.</p>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-to-v10","title":"Upgrade to v1.0","text":"<p>Upgrades from v0.* versions to v1.0 are best-effort only. The following guide assumes an upgrade from v0.5.0.</p> <ul> <li> <p>CRDs have been updated and set to version <code>v1</code>. You need to replace any existing CRDs with these new ones:   <pre><code>kubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcontrollers_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcsidrivers_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorsatellitesets_crd.yaml\n</code></pre></p> </li> <li> <p>Renamed <code>LinstorNodeSet</code> to <code>LinstorSatelliteSet</code>. This brings the operator in line with other LINSTOR resources.   Existing <code>LinstorNodeSet</code> resources will automatically be migrated to <code>LinstorSatelliteSet</code>. The old resources will   not be deleted. You can verify that migration was successful by running the following command:   <pre><code>$ kubectl get linstornodesets.piraeus.linbit.com -o=jsonpath='{range .items[*]}{.metadata.name}{\"\\t\"}{.status.ResourceMigrated}{\"\\t\"}{.status.DependantsMigrated}{\"\\n\"}{end}'\npiraeus-op-ns true    true\n</code></pre>   If both values are <code>true</code>, migration was successful. The old resource can be removed after migration.</p> </li> <li> <p>Renamed <code>LinstorControllerSet</code> to <code>LinstorController</code>. The old name implied the existence of multiple (separate)   controllers. Existing <code>LinstorControllerSet</code> resources will automatically be migrated to <code>LinstorController</code>. The old   resources will not be deleted. You can verify that migration was successful by running the following command:   <pre><code>$ kubectl get linstorcontrollersets.piraeus.linbit.com -o=jsonpath='{range .items[*]}{.metadata.name}{\"\\t\"}{.status.ResourceMigrated}{\"\\t\"}{.status.DependantsMigrated}{\"\\n\"}{end}'\npiraeus-op-cs true    true\n</code></pre>   If both values are <code>true</code>, migration was successful. The old resource can be removed after migration.</p> </li> <li> <p>Along with the CRDs, Helm settings changed too:</p> <ul> <li><code>operator.controllerSet</code> to <code>operator.controller</code></li> <li><code>operator.nodeSet</code> to <code>operator.satelliteSet</code>   If old settings are used, Helm will return an error.</li> </ul> </li> <li> <p>Node scheduling no longer relies on <code>linstor.linbit.com/piraeus-node</code> labels. Instead, all CRDs support   setting pod affinity and tolerations.   In detail:</p> <ul> <li><code>linstorcsidrivers</code> gained 4 new resource keys, with no change in default behaviour:<ul> <li><code>nodeAffinity</code> affinity passed to the csi nodes</li> <li><code>nodeTolerations</code> tolerations passed to the csi nodes</li> <li><code>controllerAffinity</code> affinity passed to the csi controller</li> <li><code>controllerTolerations</code> tolerations passed to the csi controller</li> </ul> </li> <li><code>linstorcontrollerset</code> gained 2 new resource keys, with no change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> <li><code>linstornodeset</code> gained 2 new resource keys, with change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> </ul> <p>Previously, linstor satellite pods required nodes marked with <code>linstor.linbit.com/piraeus-node=true</code>. The new   default value does not place this restriction on nodes. To restore the old behaviour, set the following affinity:   <pre><code>affinity:\n  nodeAffinity:\n    requiredDuringSchedulingIgnoredDuringExecution:\n      nodeSelectorTerms:\n      - matchExpressions:\n        - key: linstor.linbit.com/piraeus-node\n          operator: In\n          values:\n          - \"true\"\n</code></pre></p> </li> <li> <p>Other changed helm settings:   <code>drbdKernelModuleInjectionMode</code>: renamed to <code>kernelModuleInjectionMode</code> <code>kernelModImage</code>: renamed to <code>kernelModuleInjectionImage</code>   If old settings are used, Helm will return an error.</p> </li> </ul>"},{"location":"how-to/upgrade/UPGRADE/#upgrade-between-v0-versions","title":"Upgrade between v0.* versions","text":"<p>While the API version was <code>v1alpha1</code>, this project did not maintain stability of or provide conversion of the Custom Resource Definitions.</p> <p>If you are using the Helm deployment, you may find that upgrades fail with errors similar to the following:</p> <pre><code>UPGRADE FAILED: cannot patch \"piraeus-op-cs\" with kind LinstorController: LinstorController.piraeus.linbit.com \"piraeus-op-cs\" is invalid: spec.etcdURL: Required value\n</code></pre> <p>The simplest solution in this case is to manually replace the CRD:</p> <pre><code>kubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcsidrivers_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorsatellitesets_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcontrollers_crd.yaml\n</code></pre> <p>Then continue with the Helm upgrade. Values that are lost during the replacement will be set again by Helm.</p>"},{"location":"reference/","title":"API Reference","text":"<p>This is the API Reference for Piraeus Operator. A user may make modifications to these resources to change the cluster state (<code>LinstorCluster</code> or <code>LinstorSatelliteConfiguration</code>) or check the status of a resource (<code>LinstorSatellite</code>).</p> <ul> <li> <p>LinstorCluster</p> <p>This resource controls the state of the LINSTOR\u00ae cluster and integration with Kubernetes.</p> <p> Reference</p> </li> <li> <p>LinstorSatelliteConfiguration</p> <p>This resource controls the state of the LINSTOR Satellites, optionally applying it to only a subset of nodes.</p> <p> Reference</p> </li> <li> <p>LinstorNodeConnection</p> <p>This resource controls the state of the LINSTOR\u00ae node connections.</p> <p> Reference</p> </li> <li> <p>LinstorSatellite</p> <p>This resource controls the state of a single LINSTOR Satellite. This resource is not intended to be changed directly, instead it is created by the Piraeus Operator by merging all matching <code>LinstorSatelliteConfiguration</code> resources.</p> <p> Reference</p> </li> </ul>"},{"location":"reference/linstorcluster/","title":"<code>LinstorCluster</code>","text":"<p>This resource controls the state of the LINSTOR\u00ae cluster and integration with Kubernetes. In particular, it controls:</p> <ul> <li>LINSTOR Controller</li> <li>LINSTOR CSI Driver</li> <li><code>LinstorSatellite</code>, configured through <code>LinstorSatelliteConfiguration</code> resources.</li> </ul>"},{"location":"reference/linstorcluster/#spec","title":"<code>.spec</code>","text":"<p>Configures the desired state of the cluster.</p>"},{"location":"reference/linstorcluster/#specnodeselector","title":"<code>.spec.nodeSelector</code>","text":"<p>Selects on which nodes Piraeus Datastore should be deployed. Nodes that are excluded by the selector will not be able to run any workload using a Piraeus volume.</p> <p>If empty (the default), Piraeus will be deployed on all nodes in the cluster.</p> <p>When this is used together with <code>.spec.nodeAffinity</code>, both need to match in order for a node to run Piraeus.</p>"},{"location":"reference/linstorcluster/#example","title":"Example","text":"<p>This example restricts Piraeus Datastore to nodes matching <code>example.com/storage: \"yes\"</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  nodeSelector:\n    example.com/storage: \"yes\"\n</code></pre>"},{"location":"reference/linstorcluster/#specnodeaffinity","title":"<code>.spec.nodeAffinity</code>","text":"<p>Selects on which nodes Piraeus Datastore should be deployed. Nodes that are excluded by the affinity will not be able to run any workload using a Piraeus volume.</p> <p>If empty (the default), Piraeus will be deployed on all nodes in the cluster.</p> <p>When this is used together with <code>.spec.nodeSelector</code>, both need to match in order for a node to run Piraeus.</p>"},{"location":"reference/linstorcluster/#example_1","title":"Example","text":"<p>This example restricts Piraeus Datastore to nodes in zones <code>a</code> and <code>b</code>, but not on <code>control-plane</code> nodes:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  nodeAffinity:\n    nodeSelectorTerms:\n      - matchExpressions:\n          - key: topology.kubernetes.io/zone\n            operator: In\n            values:\n              - a\n              - b\n          - key: node-role.kubernetes.io/control-plane\n            operator: DoesNotExist\n</code></pre>"},{"location":"reference/linstorcluster/#specrepository","title":"<code>.spec.repository</code>","text":"<p>Sets the default image registry to use for all Piraeus images. The full image name is created by appending an image identifier and tag.</p> <p>If empty (the default), Piraeus will use <code>quay.io/piraeusdatastore</code>.</p> <p>The current list of default images is available here.</p>"},{"location":"reference/linstorcluster/#example_2","title":"Example","text":"<p>This example pulls all Piraeus images from <code>registry.example.com/piraeus-mirror</code> rather than <code>quay.io/piraeusdatastore</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  repository: registry.example.com/piraeus-mirror\n</code></pre>"},{"location":"reference/linstorcluster/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Sets the given properties on the LINSTOR Controller level, applying them to the whole Cluster.</p>"},{"location":"reference/linstorcluster/#example_3","title":"Example","text":"<p>This example sets the port range used for DRBD\u00ae volumes to <code>10000-20000</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  properties:\n    - name: TcpPortAutoRange\n      value: \"10000-20000\"\n</code></pre>"},{"location":"reference/linstorcluster/#speclinstorpassphrasesecret","title":"<code>.spec.linstorPassphraseSecret</code>","text":"<p>Configures the LINSTOR passphrase, used by LINSTOR when creating encrypted volumes and storing access credentials for backups.</p> <p>The referenced secret must exist in the same namespace as the operator (by default <code>piraeus-datastore</code>), and have a <code>MASTER_PASSPHRASE</code> entry.</p>"},{"location":"reference/linstorcluster/#example_4","title":"Example","text":"<p>This example configures a passphrase <code>example-passphrase</code>. Please choose a different passphrase for your deployment.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: linstor-passphrase\n  namespace: piraeus-datastore\ndata:\n  # CHANGE THIS TO USE YOUR OWN PASSPHRASE!\n  # Created by: echo -n \"example-passphrase\" | base64\n  MASTER_PASSPHRASE: ZXhhbXBsZS1wYXNzcGhyYXNl\n---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  linstorPassphraseSecret: linstor-passphrase\n</code></pre>"},{"location":"reference/linstorcluster/#specpatches","title":"<code>.spec.patches</code>","text":"<p>The given patches will be applied to all resources controlled by the operator. The patches are forwarded to <code>kustomize</code> internally, and take the same format.</p> <p>The unpatched resources are available in the subdirectories of the <code>pkg/resources</code> directory.</p>"},{"location":"reference/linstorcluster/#warning","title":"Warning","text":"<p>No checks are run on the result of user-supplied patches: the resources are applied as-is. Patching some fundamental aspect, such as removing a specific volume from a container may lead to a degraded cluster.</p>"},{"location":"reference/linstorcluster/#example_5","title":"Example","text":"<p>This example sets a CPU limit of <code>10m</code> on the CSI Node init container and changes the LINSTOR Controller service to run in <code>SingleStack</code> mode.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  patches:\n    - target:\n        kind: Daemonset\n        name: csi-node\n      patch: |-\n        - op: add\n          path: /spec/template/spec/initContainers/0/resources\n          value:\n            limits:\n               cpu: 10m\n    - target:\n        kind: Service\n        name: linstor-controller\n      patch: |-\n        apiVersion: v1\n        kind: service\n        metadata:\n          name: linstor-controller\n        spec:\n          ipFamilyPolicy: SingleStack\n</code></pre>"},{"location":"reference/linstorcluster/#specexternalcontroller","title":"<code>.spec.externalController</code>","text":"<p>Configures the Operator to use an external controller instead of deploying one in the Cluster.</p>"},{"location":"reference/linstorcluster/#example_6","title":"Example","text":"<p>This examples instructs the Operator to use the external LINSTOR Controller reachable at <code>http://linstor.example.com:3370</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  externalController:\n    url: http://linstor.example.com:3370\n</code></pre>"},{"location":"reference/linstorcluster/#speccontroller","title":"<code>.spec.controller</code>","text":"<p>Controls the LINSTOR Controller Deployment: * Setting <code>enabled: false</code> disables the controller deployment entirely. See also <code>.spec.externalController</code>. * Setting a <code>podTemplate:</code> allows for simple modification of the LINSTOR Controller Deployment.</p>"},{"location":"reference/linstorcluster/#example_7","title":"Example","text":"<p>This example configures a resource request of <code>memory: 1Gi</code> for the LINSTOR Controller Deployment:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  controller:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-controller\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#speccsicontroller","title":"<code>.spec.csiController</code>","text":"<p>Controls the CSI Controller Deployment: * Setting <code>enabled: false</code> disables the deployment entirely. * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Controller Deployment.</p>"},{"location":"reference/linstorcluster/#example_8","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Controller Deployment:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  csiController:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-csi\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#speccsinode","title":"<code>.spec.csiNode</code>","text":"<p>Controls the CSI Node DaemonSet: * Setting <code>enabled: false</code> disables the deployment entirely. * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Node DaemonSet.</p>"},{"location":"reference/linstorcluster/#example_9","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Node DaemonSet:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  csiNode:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-csi\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#spechighavailabilitycontroller","title":"<code>.spec.highAvailabilityController</code>","text":"<p>Controls the High Availability Controller DaemonSet: * Setting <code>enabled: false</code> disables the deployment entirely. * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Node Deployment.</p>"},{"location":"reference/linstorcluster/#example_10","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Node Deployment:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  highAvailabilityController:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: ha-controller\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#specinternaltls","title":"<code>.spec.internalTLS</code>","text":"<p>Configures a TLS secret used by the LINSTOR Controller to: * Validate the certificate of the LINSTOR Satellites, that is the Satellites must have certificates signed by <code>ca.crt</code>. * Provide a client certificate for authentication with LINSTOR Satellites, that is <code>tls.key</code> and <code>tls.crt</code> must be accepted by the Satellites.</p> <p>To configure TLS communication between Satellite and Controller, <code>LinstorSatelliteConfiguration.spec.internalTLS</code> must be set accordingly.</p> <p>Setting a <code>secretName</code> is optional, it will default to <code>linstor-controller-internal-tls</code>.</p> <p>Optional, a reference to a cert-manager <code>Issuer</code> can be provided to let the operator create the required secret.</p> <p>If the referenced secret does not contain a <code>ca.crt</code> certificate of a certificate authority, a <code>caReference</code> pointing to a secondary <code>Secret</code> or <code>ConfigMap</code> resource can be configured.</p>"},{"location":"reference/linstorcluster/#example_11","title":"Example","text":"<p>This example creates a manually provisioned TLS secret and references it in the LinstorCluster configuration.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-linstor-controller-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    secretName: my-linstor-controller-tls\n</code></pre>"},{"location":"reference/linstorcluster/#example_12","title":"Example","text":"<p>This example sets up automatic creation of the LINSTOR Controller TLS secret using a cert-manager issuer named <code>piraeus-root</code>. The certificates will be validated against the certificate in the <code>trust-root</code> ConfigMap.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    certManager:\n      kind: Issuer\n      name: piraeus-root\n    caReference:\n      name: trust-root\n      kind: ConfigMap\n      key: root.crt\n</code></pre>"},{"location":"reference/linstorcluster/#specapitls","title":"<code>.spec.apiTLS</code>","text":"<p>Configures the TLS secrets used to secure the LINSTOR API. There are four different secrets to configure:</p> <ul> <li><code>apiSecretName</code>: sets the name of the secret used by the LINSTOR Controller to enable HTTPS. Defaults to   <code>linstor-api-tls</code>. All clients of the API must have certificates signed by the <code>ca.crt</code> of this secret.</li> <li><code>clientSecretName</code>: sets the name of the secret used by the Operator to connect to the LINSTOR API. Defaults to   <code>linstor-client-tls</code>. Must be trusted by <code>ca.crt</code> in the API Secret. Also used by the LINSTOR Controller to configure   the included LINSTOR CLI.</li> <li><code>csiControllerSecretName</code> sets the name of the secret used by the CSI Controller. Defaults to   <code>linstor-csi-controller-tls</code>. Must be trusted by <code>ca.crt</code> in the API Secret.</li> <li><code>csiNodeSecretName</code> sets the name of the secret used by the CSI Controller. Defaults to <code>linstor-csi-node-tls</code>.   Must be trusted by <code>ca.crt</code> in the API Secret.</li> </ul> <p>Optional, a reference to a cert-manager <code>Issuer</code> can be provided to let the operator create the required secrets.</p> <p>If the referenced secret does not contain a <code>ca.crt</code> certificate of a certificate authority, a <code>caReference</code> pointing to a secondary <code>Secret</code> or <code>ConfigMap</code> resource can be configured.</p>"},{"location":"reference/linstorcluster/#example_13","title":"Example","text":"<p>This example creates a manually provisioned TLS secret and references it in the LinstorCluster configuration. It uses the same secret for all clients of the LINSTOR API.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-linstor-api-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-linstor-client-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    apiSecretName: my-linstor-api-tls\n    clientSecretName: my-linstor-client-tls\n    csiControllerSecretName: my-linstor-client-tls\n    csiNodeSecretName: my-linstor-client-tls\n</code></pre>"},{"location":"reference/linstorcluster/#example_14","title":"Example","text":"<p>This example sets up automatic creation of the LINSTOR API and LINSTOR Client TLS secret using a cert-manager issuer named <code>piraeus-root</code>. The certificates will be validated against the certificate in the <code>trust-root</code> Secret.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    certManager:\n      kind: Issuer\n      name: piraeus-root\n    caReference:\n      name: trust-root\n      kind: Secret\n      key: root.crt\n</code></pre>"},{"location":"reference/linstorcluster/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the cluster.</p>"},{"location":"reference/linstorcluster/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the Cluster through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Applied</code> All Kubernetes resources controlled by the Operator are applied and up to date. <code>Available</code> The LINSTOR Controller is deployed and reponding to requests. <code>Configured</code> The LINSTOR Controller is configured with the properties from <code>.spec.properties</code>"},{"location":"reference/linstornodeconnection/","title":"<code>LinstorNodeConnection</code>","text":"<p>This resource controls the state of the LINSTOR\u00ae node connections.</p> <p>Node connections control the DRBD options set on a particular path, such as which protocol and network interface to use.</p>"},{"location":"reference/linstornodeconnection/#spec","title":"<code>.spec</code>","text":"<p>Configures the desired state of the node connections.</p>"},{"location":"reference/linstornodeconnection/#specselector","title":"<code>.spec.selector</code>","text":"<p>Selects which connections the resource should apply to. By default, a <code>LinstorNodeConnection</code> resource applies to every possible connection in the cluster.</p> <p>A resource applies to a connection if one of the provided selectors match. A selector itself can contain multiple expressions. If multiple expressions are specified in a selector, the connection must match all of them.</p> <p>Every expression requires a label name (<code>key</code>) on which it operates and an operator <code>op</code>. Depending on the operator, you can also specify specific values for the node label.</p> <p>The following operators are available:</p> <ul> <li><code>Exists</code>, the label specified in <code>key</code> is present on both nodes of the connection, with any value. This is the   default.</li> <li><code>DoesNotExist</code>, the label specified in <code>key</code> is not present on the nodes in the connections.</li> <li><code>In</code>, the label specified in <code>key</code> matches any of the provided <code>values</code> for the nodes in the connection.</li> <li><code>NotIn</code> the label specified in <code>key</code> does not match any of the provided <code>values</code> for the nodes in the connection.</li> <li><code>Same</code> the label specified in <code>key</code> has the same value for the nodes in the connection.</li> <li><code>NotSame</code> the label specified in <code>key</code> has different values for the nodes in the connection.</li> </ul>"},{"location":"reference/linstornodeconnection/#example","title":"Example","text":"<p>This example restricts the resource to connections between nodes matching <code>example.com/storage: \"yes\"</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: selector\nspec:\n  selector:\n    - matchLabels:\n        - key: example.com/storage\n          op: In\n          values:\n            - yes\n</code></pre>"},{"location":"reference/linstornodeconnection/#example_1","title":"Example","text":"<p>This example restricts the resource to connections between nodes in the same region, but different zones.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: selector\nspec:\n  selector:\n    - matchLabels:\n        - key: topology.kubernetes.io/region\n          op: Same\n        - key: topology.kubernetes.io/zone\n          op: NotSame\n</code></pre>"},{"location":"reference/linstornodeconnection/#specpaths","title":"<code>.spec.paths</code>","text":"<p>Paths configure one or more network connections between nodes. If a path is configured, LINSTOR will use the given network interface to configure DRBD replication. The network interfaces have to be registered with LINSTOR first, using <code>linstor node interface create ...</code>.</p>"},{"location":"reference/linstornodeconnection/#example_2","title":"Example","text":"<p>This example configures all nodes to use the \"data-nic\" network interface instead of the default interface.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: network-paths\nspec:\n  paths:\n    - name: path1\n      interface: data-nic\n</code></pre>"},{"location":"reference/linstornodeconnection/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Sets the given properties on the LINSTOR Node Connection level.</p>"},{"location":"reference/linstornodeconnection/#example_3","title":"Example","text":"<p>This example sets the DRBD\u00ae protocol to <code>C</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: drbd-options\nspec:\n  properties:\n    - name: DrbdOptions/Net/protocol\n      value: C\n</code></pre>"},{"location":"reference/linstornodeconnection/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the connections.</p>"},{"location":"reference/linstornodeconnection/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the LINSTOR Node Connection through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Configured</code> The LINSTOR Node Connection is applied to all matching pairs of nodes."},{"location":"reference/linstorsatellite/","title":"<code>LinstorSatellite</code>","text":"<p>This resource controls the state of a LINSTOR\u00ae satellite.</p> <p>NOTE: This resource is not intended to be changed directly, instead it is created by the Piraeus Operator by merging all matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#spec","title":"<code>.spec</code>","text":"<p>Holds the desired state the satellite.</p>"},{"location":"reference/linstorsatellite/#specrepository","title":"<code>.spec.repository</code>","text":"<p>Holds the default image registry to use for all Piraeus images. Inherited from <code>LinstorCluster</code>.</p> <p>If empty (the default), the operator will use <code>quay.io/piraeusdatastore</code>.</p>"},{"location":"reference/linstorsatellite/#specclusterref","title":"<code>.spec.clusterRef</code>","text":"<p>Holds a reference to the <code>LinstorCluster</code> that controls this satellite.</p>"},{"location":"reference/linstorsatellite/#specstoragepools","title":"<code>.spec.storagePools</code>","text":"<p>Holds the storage pools to configure on the node. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Holds the properties which should be set on the node level. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#specinternaltls","title":"<code>.spec.internalTLS</code>","text":"<p>Configures a TLS secret used by the LINSTOR Satellite. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#specpatches","title":"<code>.spec.patches</code>","text":"<p>Holds patches to apply to the Kubernetes resources. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the satellite.</p>"},{"location":"reference/linstorsatellite/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the LINSTOR Satellite through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Applied</code> All Kubernetes resources were applied. <code>Available</code> The LINSTOR Satellite is connected to the LINSTOR Controller <code>Configured</code> Storage Pools and Properties are configured on the Satellite <code>EvacuationCompleted</code> Only available when the Satellite is being deleted: Indicates progress of the eviction of resources."},{"location":"reference/linstorsatelliteconfiguration/","title":"<code>LinstorSatelliteConfiguration</code>","text":"<p>This resource controls the state of one or more LINSTOR\u00ae satellites.</p>"},{"location":"reference/linstorsatelliteconfiguration/#spec","title":"<code>.spec</code>","text":"<p>Configures the desired state of satellites.</p>"},{"location":"reference/linstorsatelliteconfiguration/#specnodeselector","title":"<code>.spec.nodeSelector</code>","text":"<p>Selects which nodes the LinstorSatelliteConfiguration should apply to. If empty, the configuration applies to all nodes.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example","title":"Example","text":"<p>This example sets the <code>AutoplaceTarget</code> property to <code>no</code> on all nodes labelled <code>piraeus.io/autoplace: \"no\"</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: disabled-nodes\nspec:\n  nodeSelector:\n    piraeus.io/autplace: \"no\"\n  properties:\n    - name: AutoplaceTarget\n      value: \"no\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specnodeaffinity","title":"<code>.spec.nodeAffinity</code>","text":"<p>Selects which nodes the LinstorSatelliteConfiguration should apply to. If empty, the configuration applies to all nodes.</p> <p>When this is used together with <code>.spec.nodeSelector</code>, both need to match in order for the configuration to apply to a node.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_1","title":"Example","text":"<p>This example sets the <code>AutoplaceTarget</code> property to <code>no</code> on all non-worker nodes:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: disabled-nodes\nspec:\n  nodeAffinity:\n    nodeSelectorTerms:\n      - matchExpressions:\n          - key: node-role.kubernetes.io/control-plane\n            operator: Exists\n  properties:\n    - name: AutoplaceTarget\n      value: \"no\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Sets the given properties on the LINSTOR Satellite level.</p> <p>The property value can either be set directly using <code>value</code>, inherited from the Kubernetes Node's metadata using <code>valueFrom</code>, or expanded from Kubernetes Node's metadata using <code>expandFrom</code>. Metadata fields are specified using the same syntax as the Downward API for Pods.</p> <p>Using <code>expandFrom</code> allows for using field references matching more than one field. Either specify a field that is already a map (<code>metadata.labels</code> or <code>metadata.annotations</code>), or select a subset by using <code>*</code> at the end of a key. Using <code>*</code> will select the keys and values matching the prefix up to the <code>*</code> character. There are two ways to use <code>expandFrom</code>:</p> <ul> <li>Setting a <code>nameTemplate</code> will create one property per matched field. The property name is generated by taking   the <code>name</code> field and appending the expanded <code>nameTemplate</code>. <code>nameTemplate</code> supports the following expansions:</li> <li><code>$1</code> is replaced with the field key, i.e. the part matched by the <code>+</code> character.</li> <li><code>$2</code> is replaced with the value of the matched field.</li> </ul> <p>The <code>valueTemplate</code> is expanded using the same replacements, and sets the property value. * Setting no <code>nameTemplate</code> will create one property using <code>name</code>. The value of the property is the   joined expansion of the <code>valueTemplate</code> field for every matched field. See above for supported expansions. The result   is joined using the optional <code>delimiter</code> value.</p> <p>In addition, setting <code>optional</code> to true means the property is only applied if the value is not empty. This is useful in case the property value should be inherited from the node's metadata</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_2","title":"Example","text":"<p>This examples sets the following Properties on every satellite: * <code>PrefNic</code> (the preferred network interface) is always set to <code>default-ipv6</code> * <code>Aux/example-property</code> (an auxiliary property, unused by LINSTOR itself) takes the value from the <code>piraeus.io/example</code>   label of the Kubernetes Node. If a node has no <code>piraeus.io/example</code> label, the property value will be <code>\"\"</code>. * <code>AutoplaceTarget</code> (if set to <code>no</code>, will exclude the node from LINSTOR's Autoplacer) takes the value from the   <code>piraeus.io/autoplace</code> annotation of the Kubernetes Node. If a node has no <code>piraeus.io/autoplace</code> annotation, the   property will not be set. * <code>Aux/role/</code> copies all <code>node-role.kubernetes.io/*</code> label keys and values. For example, a worker node with the   <code>node-role.kubernetes.io/worker: \"true\"</code> label will have <code>Aux/role/worker</code> set to <code>\"true\"</code>. * <code>Aux/features</code> copies the names of all <code>feature.example.com/*</code> label keys to the value, joined by <code>,</code>. For example,   a node with <code>feature.example.com/gpu</code> and <code>feature.example.com/storage</code> will have <code>Aux/features</code> set to   <code>\"gpu,storage\"</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: ipv6-nodes\nspec:\n  properties:\n    - name: PrefNic\n      value: \"default-ipv6\"\n    - name: Aux/example-property\n      valueFrom:\n        nodeFieldRef: metadata.labels['piraeus.io/example']\n    - name: AutoplaceTarget\n      valueFrom:\n        nodeFieldRef: metadata.annotations['piraeus.io/autoplace']\n      optional: yes\n    - name: Aux/role/\n      expandFrom:\n        nodeFieldRef: metadata.labels['node-role.kubernetes.io/*']\n        nameTemplate: \"$1\"\n        valueTemplate: \"$2\"\n    - name: Aux/features\n      expandFrom:\n        nodeFieldRef: metadata.labels['feature.example.com/*']\n        valueTemplate: \"$1\"\n        delimiter: \",\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specstoragepools","title":"<code>.spec.storagePools</code>","text":"<p>Configures LINSTOR Storage Pools.</p> <p>Every Storage Pool needs at least a <code>name</code>, and a type. Types are specified by setting a (potentially empty) value on the matching key. Available types are:</p> <ul> <li><code>lvmPool</code>: Configures a LVM Volume Group as storage   pool. Defaults to using the storage pool name as the VG name. Can be overridden by setting <code>volumeGroup</code>.</li> <li><code>lvmThinPool</code>: Configures a LVM Thin Pool as storage pool.   Defaults to using the storage pool name as name for the thin pool volume and the storage pool name prefixed by   <code>linstor_</code> as the VG name. Can be overridden by setting <code>thinPool</code> and <code>volumeGroup</code>.</li> <li><code>filePool</code>: Configures a file system based storage pool. Configures a host directory as location for the volume files.   Defaults to using the <code>/var/lib/linstor-pools/&lt;storage pool name&gt;</code> directory.</li> <li><code>fileThinPool</code>: Configures a file system based storage pool. Behaves the same as <code>filePool</code>, except the files will   be thinly allocated on file systems that support sparse files.</li> <li><code>zfsPool</code>: Configure a ZFS ZPool as storage pool. Defaults to using the storage   pool name as name for the zpool. Can be overriden by setting <code>zPool</code>.</li> <li><code>zfsThinPool</code>: Configure a ZFS ZPool as storage pool. Behaves the same as   <code>zfsPool</code>, except the contained zVol will be created using sparse reservation.</li> </ul> <p>Optionally, you can configure LINSTOR to automatically create the backing pools. <code>source.hostDevices</code> takes a list of raw block devices, which LINSTOR will prepare as the chosen backing pool.</p> <p>All storage pools also can also be configured with <code>properties</code>. Properties are set on the Storage Pool level. The configuration values have the same form as Satellite Properties.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_3","title":"Example","text":"<p>This example configures these LINSTOR Storage Pools on all satellites: * A LVM Pool named <code>vg1</code>. It will use the VG <code>vg1</code>, which needs to exist on the nodes already. * A LVM Thin Pool named <code>vg1-thin</code>. It will use the thin pool <code>vg1/thin</code>, which also needs to exist on the nodes. * A LVM Pool named <code>vg2-from-raw-devices</code>. It will use the VG <code>vg2</code>, which will be created on demand from the raw   devices <code>/dev/sdb</code> and <code>/dev/sdc</code> if it does not exist already. In addition, it sets the <code>StorDriver/LvcreateOptions</code>   property to <code>-i 2</code>, which causes every created LV to be striped across 2 PVs. * A File System Pool named <code>fs1</code>. It will use the <code>/var/lib/linstor-pools/fs1</code> directory on the host, creating the   directory if necessary. * A File System Pool named <code>fs2</code>, using sparse files. It will use the custom <code>/mnt/data</code> directory on the host. * A ZFS Pool named <code>zfs1</code>. It will use ZPool <code>zfs1</code>, which needs to exist on the nodes already. * A ZFS Thin Pool named <code>zfs2</code>. It will use ZPool <code>zfs-thin2</code>, which will be created on demand from the raw device   <code>/dev/sdd</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: storage-satellites\nspec:\n  storagePools:\n    - name: vg1\n      lvmPool: {}\n    - name: vg1-thin\n      lvmThinPool:\n        volumeGroup: vg1\n        thinPool: thin\n    - name: vg2-from-raw-devices\n      lvmPool:\n        volumeGroup: vg2\n      source:\n        hostDevices:\n          - /dev/sdb\n          - /dev/sdc\n      properties:\n        - name: StorDriver/LvcreateOptions\n          value: '-i 2'\n    - name: fs1\n      filePool: {}\n    - name: fs2\n      fileThinPool:\n        directory: /mnt/data\n    - name: zfs1\n      zfsPool: {}\n    - name: zfs2\n      zfsThinPool:\n        zPool: zfs-thin2\n      source:\n        hostDevices:\n        - /dev/sdd\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specinternaltls","title":"<code>.spec.internalTLS</code>","text":"<p>Configures a TLS secret used by the LINSTOR Satellites to: * Validate the certificate of the LINSTOR Controller, that is the Controller must have certificates signed by <code>ca.crt</code>. * Provide a server certificate for authentication by the LINSTOR Controller, that is <code>tls.key</code> and <code>tls.crt</code> must be accepted by the Controller.</p> <p>To configure TLS communication between Satellite and Controller, <code>LinstorCluster.spec.internalTLS</code> must be set accordingly.</p> <p>Setting a <code>secretName</code> is optional, it will default to <code>&lt;node-name&gt;-tls</code>, where <code>&lt;node-name&gt;</code> is replaced with the name of the Kubernetes Node.</p> <p>Optional, a reference to a cert-manager <code>Issuer</code> can be provided to let the operator create the required secret.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_4","title":"Example","text":"<p>This example creates a manually provisioned TLS secret and references it in the LinstorSatelliteConfiguration, setting it for all nodes.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-node-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: satellite-tls\nspec:\n  internalTLS:\n    secretName: my-node-tls\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#example_5","title":"Example","text":"<p>This example sets up automatic creation of the LINSTOR Satellite TLS secrets using a cert-manager issuer named <code>piraeus-root</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: satellite-tls\nspec:\n  internalTLS:\n    certManager:\n      kind: Issuer\n      name: piraeus-root\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specipfamilies","title":"<code>.spec.ipFamilies</code>","text":"<p>Configures the IP Family (IPv4 or IPv6) to use to connect to the LINSTOR Satellite.</p> <p>If unset, the LINSTOR Controller will attempt to reach the LINSTOR Satellite via all recognized addresses in the Satellite Pods' Status. If set, the LINSTOR Controller will only attempt to reach the LINSTOR Satellite via all addresses matching the listed IP Families.</p> <p>Valid values are <code>IPv4</code> and <code>IPv6</code>.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_6","title":"Example","text":"<p>This example configures the LINSTOR Controller to only use IPv4, even in a dual stack cluster.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: ipv4-only\nspec:\n  ipFamilies:\n  - IPv4\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specpodtemplate","title":"<code>.spec.podTemplate</code>","text":"<p>Configures the Pod used to run the LINSTOR Satellite.</p> <p>The template is applied as a patch (see <code>.spec.patches</code>) to the default resources, so it can be \"sparse\".</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_7","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 100m</code> on the satellite, and also enables host networking.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: resource-and-host-network\nspec:\n  podTemplate:\n    spec:\n      hostNetwork: true\n      containers:\n        - name: linstor-satellite\n          resources:\n            requests:\n              cpu: 100m\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specpatches","title":"<code>.spec.patches</code>","text":"<p>The given patches will be applied to all resources controlled by the operator. The patches are forwarded to <code>kustomize</code> internally, and take the same format.</p> <p>The unpatched resources are available in the subdirectories of the <code>pkg/resources/satellite</code> directory.</p>"},{"location":"reference/linstorsatelliteconfiguration/#warning","title":"Warning","text":"<p>No checks are run on the result of user-supplied patches: the resources are applied as-is. Patching some fundamental aspect, such as removing a specific volume from a container may lead to a degraded cluster.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_8","title":"Example","text":"<p>This example configures the LINSTOR Satellite to use the \"TRACE\" log level, creating very verbose output.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: all-satellites\nspec:\n  patches:\n    - target:\n        kind: ConfigMap\n        name: satellite-config\n      patch: |-\n        apiVersion: v1\n        kind: ConfigMap\n        metadata:\n          name: satellite-config\n        data:\n          linstor_satellite.toml: |\n            [logging]\n              linstor_level = \"TRACE\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the cluster.</p>"},{"location":"reference/linstorsatelliteconfiguration/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the Satellite Configuration through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Applied</code> The given configuration was applied to all <code>LinstorSatellite</code> resources."},{"location":"tutorial/","title":"Tutorials","text":"<p>These tutorials help you get started with Piraeus Datastore</p>"},{"location":"tutorial/#get-started","title":"Get Started","text":"<p>Get started with Piraeus Datastore by deploying Piraeus Operator and provisioning your first volume.</p>"},{"location":"tutorial/#creating-replicated-volumes","title":"Creating Replicated Volumes","text":"<p>Create replicated volumes, making your data accessible on any cluster node.</p>"},{"location":"tutorial/#creating-and-restoring-from-snapshots","title":"Creating and Restoring from Snapshots","text":"<p>Create snapshots and restore a volume, safeguarding data against accidental deletion.</p>"},{"location":"tutorial/get-started/","title":"Get Started","text":"<p>Learn about the ways to get started with Piraeus Datastore by deploying Piraeus Operator and provisioning your first volume.</p>"},{"location":"tutorial/get-started/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install the Linux kernel headers on the hosts.</li> <li>Install <code>kubectl</code> version <code>&gt;= 1.22</code></li> </ul>"},{"location":"tutorial/get-started/#install-piraeus-operator","title":"Install Piraeus Operator","text":"<p>In this tutorial we will be using <code>kubectl</code> with the built-in <code>kustomize</code> feature to deploy Piraeus Operator. All resources needed to run Piraeus Operator are included in a single Kustomization.</p> <p>Install Piraeus Operator by running:</p> <pre><code>$ kubectl apply --server-side -k \"https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.7.1\"\nnamespace/piraeus-datastore configured\n...\n</code></pre> <p>The Piraeus Operator will be installed in a new namespace <code>piraeus-datastore</code>. After a short wait the operator will be ready. The following command waits until the Operator is ready:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -n piraeus-datastore -l app.kubernetes.io/component=piraeus-operator\npod/piraeus-operator-controller-manager-dd898f48c-bhbtv condition met\n</code></pre>"},{"location":"tutorial/get-started/#deploy-piraeus-datastore","title":"Deploy Piraeus Datastore","text":"<p>Now, we will deploy Piraeus Datastore using a new resource managed by Piraeus Operator. We create a <code>LinstorCluster</code>, which creates all the necessary resources (Deployments, Pods, and so on...) for our Datastore:</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec: {}\nEOF\n</code></pre> <p>Again, all workloads will be deployed to the <code>piraeus-datastore</code> namespace. After a short wait the Datastore will ready:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -n piraeus-datastore -l app.kubernetes.io/name=piraeus-datastore\npod/linstor-controller-65cbbc74db-9vm9n condition met\npod/linstor-csi-controller-5ccb7d84cd-tvd9h condition met\npod/linstor-csi-node-2lkpd condition met\npod/linstor-csi-node-hbcvv condition met\npod/linstor-csi-node-hmrd7 condition met\npod/n1.example.com condition met\npod/n2.example.com condition met\npod/n3.example.com condition met\npod/piraeus-operator-controller-manager-dd898f48c-bhbtv condition met\n</code></pre> <p>We can now inspect the state of the deployed LINSTOR\u00ae Cluster using the <code>linstor</code> client:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor node list\n+-------------------------------------------------------------------+\n| Node           | NodeType  | Addresses                   | State  |\n|===================================================================|\n| n1.example.com | SATELLITE | 10.116.72.166:3366 (PLAIN)  | Online |\n| n2.example.com | SATELLITE | 10.127.183.190:3366 (PLAIN) | Online |\n| n3.example.com | SATELLITE | 10.125.97.33:3366 (PLAIN)   | Online |\n+-------------------------------------------------------------------+\n</code></pre>"},{"location":"tutorial/get-started/#configuring-storage","title":"Configuring Storage","text":"<p>We have not yet configured any storage location for our volumes. This can be accomplished by creating a new <code>LinstorSatelliteConfiguration</code> resource. We will create a storage pool of type <code>fileThinPool</code> on each node. We chose <code>fileThinPool</code> as it does not require further configuration on the host.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: storage-pool\nspec:\n  storagePools:\n    - name: pool1\n      fileThinPool:\n        directory: /var/lib/piraeus-datastore/pool1\nEOF\n</code></pre> <p>This will cause some Pods to be recreated. While this occurs <code>linstor node list</code> will temporarily show offline nodes:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor node list\n+--------------------------------------------------------------------+\n| Node           | NodeType  | Addresses                   | State   |\n|====================================================================|\n| n1.example.com | SATELLITE | 10.116.72.166:3366 (PLAIN)  | OFFLINE |\n| n2.example.com | SATELLITE | 10.127.183.190:3366 (PLAIN) | OFFLINE |\n| n3.example.com | SATELLITE | 10.125.97.33:3366 (PLAIN)   | OFFLINE |\n+--------------------------------------------------------------------+\n</code></pre> <p>Waiting a bit longer, the nodes will be <code>Online</code> again. Once the nodes are connected again, we can verify that the storage pools were configured:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor storage-pool list\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n| StoragePool          | Node           | Driver    | PoolName                         | FreeCapacity | TotalCapacity | CanSnapshots | State | SharedName |\n|=========================================================================================================================================================|\n| DfltDisklessStorPool | n1.example.com | DISKLESS  |                                  |              |               | False        | Ok    |            |\n| DfltDisklessStorPool | n2.example.com | DISKLESS  |                                  |              |               | False        | Ok    |            |\n| DfltDisklessStorPool | n3.example.com | DISKLESS  |                                  |              |               | False        | Ok    |            |\n| pool1                | n1.example.com | FILE_THIN | /var/lib/piraeus-datastore/pool1 |    24.54 GiB |     49.30 GiB | True         | Ok    |            |\n| pool1                | n2.example.com | FILE_THIN | /var/lib/piraeus-datastore/pool1 |    23.03 GiB |     49.30 GiB | True         | Ok    |            |\n| pool1                | n3.example.com | FILE_THIN | /var/lib/piraeus-datastore/pool1 |    26.54 GiB |     49.30 GiB | True         | Ok    |            |\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre>"},{"location":"tutorial/get-started/#using-piraeus-datastore","title":"Using Piraeus Datastore","text":"<p>We now have successfully deployed and configured Piraeus Datastore, and are ready to create our first <code>PersistentVolume</code> in Kubernetes.</p> <p>First, we will set up a new <code>StorageClass</code> for our volumes. In the <code>StorageClass</code>, we specify the storage pool from above:</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: piraeus-storage\nprovisioner: linstor.csi.linbit.com\nallowVolumeExpansion: true\nvolumeBindingMode: WaitForFirstConsumer\nparameters:\n  linstor.csi.linbit.com/storagePool: pool1\nEOF\n</code></pre> <p>Next, we will create a <code>PersistentVolumeClaim</code>, requesting 1G of storage from our newly created <code>StorageClass</code>.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: data-volume\nspec:\n  storageClassName: piraeus-storage\n  resources:\n    requests:\n      storage: 1Gi\n  accessModes:\n    - ReadWriteOnce\nEOF\n</code></pre> <p>When we check the created PersistentVolumeClaim, we can see that it remains in <code>Pending</code> state.</p> <pre><code>$ kubectl get persistentvolumeclaim\nNAME          STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS      AGE\ndata-volume   Pending                                      piraeus-storage   14s\n</code></pre> <p>We first need to create a \"consumer\", which in this case is just a <code>Pod</code>. For our consumer, we will create a Deployment for a simple web server, serving files from our volume.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: web-server\nspec:\n  selector:\n    matchLabels:\n      app.kubernetes.io/name: web-server\n  template:\n    metadata:\n      labels:\n        app.kubernetes.io/name: web-server\n    spec:\n      containers:\n        - name: web-server\n          image: nginx\n          volumeMounts:\n            - mountPath: /usr/share/nginx/html\n              name: data\n      volumes:\n        - name: data\n          persistentVolumeClaim:\n            claimName: data-volume\nEOF\n</code></pre> <p>After a short wait, the Pod is <code>Running</code>, and our <code>PersistentVolumeClaim</code> is now <code>Bound</code>:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=web-server\npod/web-server-84867b5449-hgdzx condition met\n$ kubectl get persistentvolumeclaim\nNAME          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE\ndata-volume   Bound    pvc-9e1149e7-33db-47a7-8fc6-172514422143   1Gi        RWO            piraeus-storage   1m\n</code></pre> <p>Checking the running container, we see that the volume is mounted where we expected it:</p> <pre><code>$ kubectl exec deploy/web-server -- df -h /usr/share/nginx/html\nFilesystem      Size  Used Avail Use% Mounted on\n/dev/drbd1000   973M   24K  906M   1% /usr/share/nginx/html\n</code></pre> <p>Taking a look with the <code>linstor</code> client, we can see that the volume is listed in LINSTOR and marked as <code>InUse</code> by the Pod.</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor resource list-volumes\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n| Node           | Resource                                 | StoragePool | VolNr | MinorNr | DeviceName    | Allocated | InUse  |    State |\n|===========================================================================================================================================|\n| n1.example.com | pvc-9e1149e7-33db-47a7-8fc6-172514422143 | pool1       |     0 |    1000 | /dev/drbd1000 | 16.91 MiB | InUse  | UpToDate |\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre> <p>We have now successfully set up Piraeus Datastore and used it to provision a Persistent Volume in a Kubernetes cluster.</p>"},{"location":"tutorial/replicated-volumes/","title":"Creating Replicated Volumes","text":"<p>Learn about creating replicated volumes, making your data accessible on any cluster node.</p> <p>In this tutorial you will learn how to create a replicated volume, and verify that the data stays accessible when moving Pods from one node to another.</p>"},{"location":"tutorial/replicated-volumes/#prerequisites","title":"Prerequisites","text":"<ul> <li>A Kubernetes Cluster with at least two nodes.</li> <li>An installed and configured Piraeus Datastore. Learn how to get started in our introduction tutorial</li> </ul>"},{"location":"tutorial/replicated-volumes/#creating-the-volume","title":"Creating the Volume","text":"<p>First, we will create a new <code>StorageClass</code> for our replicated volumes. We will be using the <code>pool1</code> storage pool from the Get Started tutorial, but this time also set the <code>placementCount</code> to 2, telling LINSTOR\u00ae to store the volume data on two nodes.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: piraeus-storage-replicated\nprovisioner: linstor.csi.linbit.com\nallowVolumeExpansion: true\nvolumeBindingMode: WaitForFirstConsumer\nparameters:\n  linstor.csi.linbit.com/storagePool: pool1\n  linstor.csi.linbit.com/placementCount: \"2\"\nEOF\n</code></pre> <p>Next, we will again create a <code>PersistentVolumeClaim</code>, requesting a 1G replicated volume from our newly created <code>StorageClass</code>.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: replicated-volume\nspec:\n  storageClassName: piraeus-storage-replicated\n  resources:\n    requests:\n      storage: 1Gi\n  accessModes:\n    - ReadWriteOnce\nEOF\n</code></pre> <p>For our workload, we will create a Pod which will use the replicated volume to log its name, the current date, and the node it is running on.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: volume-logger\nspec:\n  selector:\n    matchLabels:\n      app.kubernetes.io/name: volume-logger\n  strategy:\n    type: Recreate\n  template:\n    metadata:\n      labels:\n        app.kubernetes.io/name: volume-logger\n    spec:\n      terminationGracePeriodSeconds: 0\n      containers:\n        - name: volume-logger\n          image: busybox\n          args:\n            - sh\n            - -c\n            - |\n              echo \"Hello from \\$HOSTNAME, running on \\$NODENAME, started at \\$(date)\" &gt;&gt; /volume/hello\n              # We use this to keep the Pod running\n              tail -f /dev/null\n          env:\n            - name: NODENAME\n              valueFrom:\n                fieldRef:\n                  fieldPath: spec.nodeName\n          volumeMounts:\n            - mountPath: /volume\n              name: replicated-volume\n      volumes:\n        - name: replicated-volume\n          persistentVolumeClaim:\n            claimName: replicated-volume\nEOF\n</code></pre> <p>After a short wait, the Pod is <code>Running</code>, our <code>PersistentVolumeClaim</code> is now <code>Bound</code>, and we can see that LINSTOR placed the volume on two nodes:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-84dd47f4cb-trh4l\n$ kubectl get persistentvolumeclaim\nNAME                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                 AGE\nreplicated-volume   Bound    pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d   1Gi        RWO            piraeus-storage-replicated   1m\n$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor resource list-volumes\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n| Node           | Resource                                 | StoragePool | VolNr | MinorNr | DeviceName    | Allocated | InUse  |    State |\n|===========================================================================================================================================|\n| n1.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 | 16.91 MiB | InUse  | UpToDate |\n| n2.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 |   876 KiB | Unused | UpToDate |\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre> <p>NOTE: If your cluster has three or more nodes, you will actually see a third volume, marked as <code>TieBreaker</code>. This is intentional and improves the behaviour should one of the cluster nodes become unavailable.</p> <p>Now, we can check that our Pod actually logged the expected information by reading <code>/volume/hello</code> in the Pod:</p> <pre><code>$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-84dd47f4cb-trh4l, running on n1.example.com, started at Fri Feb  3 08:53:47 UTC 2023\n</code></pre>"},{"location":"tutorial/replicated-volumes/#testing-replication","title":"Testing Replication","text":"<p>Now, we will verify that when we move the Pod to another node, we still have access to the same data.</p> <p>To test this, we will disable scheduling on the node the Pod is currently running on. This forces Kubernetes to move the Pod to another node once we trigger a restart. In our examples, the Hello message tells us that the Pod was started on <code>n1.example.com</code>, so this is the node we disable. Replace the name with your own node name.</p> <pre><code>$ kubectl cordon n1.example.com\nnode/n1.example.com cordoned\n</code></pre> <p>Now, we can trigger a new rollout of the deployment. Since we disabled scheduling <code>n1.example.com</code>, another node will have to take over our Pod.</p> <pre><code>$ kubectl rollout restart deploy/volume-logger\ndeployment.apps/volume-logger restarted\n$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-5db9dd7b87-lps2f condition met\n$ kubectl get pods -owide\nNAME                             READY   STATUS    RESTARTS   AGE   IP            NODE             NOMINATED NODE   READINESS GATES\nvolume-logger-5db9dd7b87-lps2f   1/1     Running   0          26s   10.125.97.9   n2.example.com   &lt;none&gt;           &lt;none&gt;\n</code></pre> <p>As expected, the Pod is now running on a different node, in this case on <code>n2.example.com</code>.</p> <p>Now, we can verify that the message from the original pod is still present:</p> <pre><code>$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-84dd47f4cb-trh4l, running on n1.example.com, started at Fri Feb  3 08:53:47 UTC 2023\nHello from volume-logger-5db9dd7b87-lps2f, running on n2.example.com, started at Fri Feb  3 08:55:42 UTC 2023\n</code></pre> <p>As expected, we still see the message from <code>n1.example.com</code>, as well as the message from the new Pod on <code>n2.example.com</code>.</p> <p>We can also see that LINSTOR now shows the volume as <code>InUse</code> on the new node:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor resource list-volumes\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n| Node           | Resource                                 | StoragePool | VolNr | MinorNr | DeviceName    | Allocated | InUse  |    State |\n|===========================================================================================================================================|\n| n1.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 | 16.91 MiB | Unused | UpToDate |\n| n2.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 |   952 KiB | InUse  | UpToDate |\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre> <p>You have now successfully created a replicated volume and verified that the data is accessible from multiple nodes.</p>"},{"location":"tutorial/replicated-volumes/#resetting-the-disabled-node","title":"Resetting the Disabled Node","text":"<p>Now that we have verified replication works, we can reset the disabled node:</p> <pre><code>$ kubectl uncordon n1.example.com\nnode/n1.example.com uncordoned\n</code></pre>"},{"location":"tutorial/snapshots/","title":"Creating and Restoring From Snapshots","text":"<p>Learn how to create snapshots of your data, and how you can restore the data in a snapshot.</p> <p>Snapshots create a copy of the volume content at a particular point in time. This copy remains untouched when you make modifications to the volume content. This, for example, enables you to create backups of your data before performing modifications or deletion on your data.</p> <p>Since a backup is useless, unless you have a way to restore it, this tutorial will teach you both how to create a snapshot, and how to restore in the case of accidental deletion of your data.</p>"},{"location":"tutorial/snapshots/#prerequisites","title":"Prerequisites","text":"<ul> <li>An installed and configured Piraeus Datastore. Learn how to get started in our introduction tutorial</li> <li>A storage pool supporting snapshots. LINSTOR supports snapshots for <code>LVM_THIN</code>, <code>FILE_THIN</code>, <code>ZFS</code> and <code>ZFS_THIN</code> pools.   If you followed the introduction tutorial, you are using the supported <code>FILE_THIN</code> pool.</li> <li>A cluster with <code>snapshot-controller</code> deployed. To check if   it is already deployed, try running:   <pre><code>$ kubectl api-resources --api-group=snapshot.storage.k8s.io -oname\nvolumesnapshotclasses.snapshot.storage.k8s.io\nvolumesnapshotcontents.snapshot.storage.k8s.io\nvolumesnapshots.snapshot.storage.k8s.io\n</code></pre>   If your output looks like above, you are good to go.   If your output is empty, you should deploy a snapshot controller. You can quickly deploy it by using:   <pre><code>kubectl apply -k https://github.com/kubernetes-csi/external-snapshotter//client/config/crd\nkubectl apply -k https://github.com/kubernetes-csi/external-snapshotter//deploy/kubernetes/snapshot-controller\n</code></pre></li> </ul>"},{"location":"tutorial/snapshots/#creating-an-example-workload","title":"Creating an Example Workload","text":"<p>We will be using the same workload as in the replicated volumes tutorial. This workload will save the Pods name, the node it is running on, and a timestamp to our volume. By logging this information to our volume, we can easily keep track of our data.</p> <p>First, we create our <code>StorageClass</code>, <code>PersistentVolumeClaim</code> and <code>Deployment</code>:</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\n---\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: piraeus-storage\nprovisioner: linstor.csi.linbit.com\nallowVolumeExpansion: true\nvolumeBindingMode: WaitForFirstConsumer\nparameters:\n  linstor.csi.linbit.com/storagePool: pool1\n---\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: data-volume\nspec:\n  storageClassName: piraeus-storage\n  resources:\n    requests:\n      storage: 1Gi\n  accessModes:\n    - ReadWriteOnce\n---\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: volume-logger\nspec:\n  selector:\n    matchLabels:\n      app.kubernetes.io/name: volume-logger\n  strategy:\n    type: Recreate\n  template:\n    metadata:\n      labels:\n        app.kubernetes.io/name: volume-logger\n    spec:\n      terminationGracePeriodSeconds: 0\n      containers:\n        - name: volume-logger\n          image: busybox\n          args:\n            - sh\n            - -c\n            - |\n              echo \"Hello from \\$HOSTNAME, running on \\$NODENAME, started at \\$(date)\" &gt;&gt; /volume/hello\n              # We use this to keep the Pod running\n              tail -f /dev/null\n          env:\n            - name: NODENAME\n              valueFrom:\n                fieldRef:\n                  fieldPath: spec.nodeName\n          volumeMounts:\n            - mountPath: /volume\n              name: data-volume\n      volumes:\n        - name: data-volume\n          persistentVolumeClaim:\n            claimName: data-volume\nEOF\n</code></pre> <p>Then, we wait for the Pod to start, and verify that the expected information was logged to our volume:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-cbcd897b7-jrmks condition met\n$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-cbcd897b7-jrmks, running on n3.example.com, started at Mon Feb 13 15:32:46 UTC 2023\n</code></pre>"},{"location":"tutorial/snapshots/#creating-a-snapshot","title":"Creating a Snapshot","text":"<p>Creating a snapshot requires the creation of a <code>SnapshotClass</code> first. The <code>SnapshotClass</code> specifies our <code>linstor.csi.linbit.com</code> provisioner, and sets the clean-up policy for our snapshots to <code>Delete</code>, meaning deleting the Kubernetes resources will also delete the snapshots in LINSTOR\u00ae.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: snapshot.storage.k8s.io/v1\nkind: VolumeSnapshotClass\nmetadata:\n  name: piraeus-snapshots\ndriver: linstor.csi.linbit.com\ndeletionPolicy: Delete\nEOF\n</code></pre> <p>Next, we will request the creation of a snapshot using a <code>VolumeSnapshot</code> resource. The <code>VolumeSnapshot</code> resource references the <code>PersistentVolumeClaim</code> resource we created initially, as well as our newly created <code>VolumeSnapshotClass</code>.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: snapshot.storage.k8s.io/v1\nkind: VolumeSnapshot\nmetadata:\n  name: data-volume-snapshot-1\nspec:\n  volumeSnapshotClassName: piraeus-snapshots\n  source:\n    persistentVolumeClaimName: data-volume\nEOF\n</code></pre> <p>Now, we need to wait for the snapshot to be created. We can then also verify its creation in LINSTOR:</p> <pre><code>$ kubectl wait volumesnapshot --for=jsonpath='{.status.readyToUse}'=true data-volume-snapshot-1\nvolumesnapshot.snapshot.storage.k8s.io/data-volume-snapshot-1 condition met\n$ kubectl get volumesnapshot data-volume-snapshot-1\nNAME                     READYTOUSE   SOURCEPVC     SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS       SNAPSHOTCONTENT                                    CREATIONTIME   AGE\ndata-volume-snapshot-1   true         data-volume                           1Gi           piraeus-snapshots   snapcontent-a8757c1d-cd37-42d2-9557-a24b1222d118   15s            15s\n$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor snapshot list\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n| ResourceName                             | SnapshotName                                  | NodeNames      | Volumes  | CreatedOn           | State      |\n|=========================================================================================================================================================|\n| pvc-9c04b307-d22d-454f-8f24-ed5837fe4426 | snapshot-a8757c1d-cd37-42d2-9557-a24b1222d118 | n3.example.com | 0: 1 GiB | 2023-02-13 15:36:18 | Successful |\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre>"},{"location":"tutorial/snapshots/#modifying-the-data","title":"Modifying the Data","text":"<p>Now we want to simulate a situation where we accidentally delete some important data. The important data in our example workload is the log of Pod name, Node name and timestamp. We will manually delete the file on the volume to simulate accidental removal of an important file on a persistent volume:</p> <pre><code>$ kubectl exec deploy/volume-logger -- rm /volume/hello\n$ kubectl exec deploy/volume-logger -- cat /volume/hello\ncat: can't open '/volume/hello': No such file or directory\ncommand terminated with exit code 1\n</code></pre>"},{"location":"tutorial/snapshots/#restoring-from-a-snapshot","title":"Restoring From a Snapshot","text":"<p>This is the exact situation where snapshots can come in handy. Since we created a snapshot before we made removed the file, we can create a new volume to recover our data. We will be replacing the existing <code>data-volume</code> with a new version based on the snapshot.</p> <p>First, we will stop the Deployment by scaling it down to zero Pods, so that it does not interfere with our next steps:</p> <pre><code>$ kubectl scale deploy/volume-logger --replicas=0\ndeployment.apps \"volume-logger\" deleted\n$ kubectl rollout status deploy/volume-logger\ndeployment \"volume-logger\" successfully rolled out\n</code></pre> <p>Next, we will also remove the <code>PersistentVolumeClaim</code>. We still have the snapshot which contains the data we want to restore, so we can safely remove the volume.</p> <pre><code>$ kubectl delete pvc/data-volume\npersistentvolumeclaim \"data-volume\" deleted\n</code></pre> <p>Now, we will create a new <code>PersistentVolumeClaim</code>, referencing our snapshot. This will create a volume, using the data from the snapshot.</p> <pre><code>kubectl apply -f - &lt;&lt;EOF\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: data-volume\nspec:\n  storageClassName: piraeus-storage\n  resources:\n    requests:\n      storage: 1Gi\n  dataSource:\n    apiGroup: snapshot.storage.k8s.io\n    kind: VolumeSnapshot\n    name: data-volume-snapshot-1\n  accessModes:\n    - ReadWriteOnce\nEOF\n</code></pre> <p>Since we named this new volume <code>data-volume</code>, we can just scale up our Deployment again, and the new Pod will start using the restored volume:</p> <pre><code>$ kubectl scale deploy/volume-logger --replicas=1\ndeployment.apps/volume-logger scaled\n</code></pre> <p>After the Pod started, we can once again verify the content of our volume:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-cbcd897b7-5qjbz condition met\n$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-cbcd897b7-jrmks, running on n3.example.com, started at Mon Feb 13 15:32:46 UTC 2023\nHello from volume-logger-cbcd897b7-gr6hh, running on n3.example.com, started at Mon Feb 13 15:42:17 UTC 2023\n</code></pre> <p>You have now successfully created a snapshot, and used it to back up and restore a volume after accidental deletion.</p>"}]}
\ No newline at end of file
+{"config":{"lang":["en"],"separator":"[\\s\\-]+","pipeline":["stopWordFilter"]},"docs":[{"location":"","title":"Piraeus Datastore","text":"<p>Piraeus is a cloud-native storage system that empowers Kubernetes Local Persistent Volumes with dynamic provisioning, resource management, and high-availability. It deploys and scales out automatically within Kubernetes nodes. With Piraeus, Kubernetes workloads can now consume high performance local storage using the same volume APIs that app developers have become accustomed to.</p> <ul> <li> <p> Tutorials</p> <p>Get started with Piraeus Datastore. These tutorials will guide you through the basics of setting up Piraeus Datastore.</p> <p> Tutorials</p> </li> <li> <p> How-To Guides</p> <p>How-To Guides show you how to configure a specific aspect or achieve a specific task with Piraeus Datastore.</p> <p> How-To Guides</p> </li> <li> <p> Upgrades</p> <p>Read how to upgrade a Piraeus Datastore deployment</p> <p> Upgrades</p> </li> <li> <p> Understanding Piraeus Datastore</p> <p>Read how Piraeus Datastore and it's components work, and why they work the way they do.</p> <p> Understanding Piraeus</p> </li> <li> <p> Reference</p> <p>The API Reference for the Piraeus Operator. Contains documentation of the LINSTOR related resources that the user can modify or observe.</p> <p> Reference</p> </li> </ul>"},{"location":"CHANGELOG/","title":"Changelog","text":"<p>All notable changes to this project will be documented in this file.</p> <p>The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.</p>"},{"location":"CHANGELOG/#unreleased","title":"Unreleased","text":""},{"location":"CHANGELOG/#v271-2024-11-25","title":"v2.7.1 - 2024-11-25","text":""},{"location":"CHANGELOG/#changed","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>DRBD 9.2.12</li> <li>DRBD Reactor 1.6.0</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v270-2024-11-11","title":"v2.7.0 - 2024-11-11","text":""},{"location":"CHANGELOG/#added","title":"Added","text":"<ul> <li>Option to select IP Family to use for LINSTOR control traffic.</li> </ul>"},{"location":"CHANGELOG/#changed_1","title":"Changed","text":"<ul> <li>Reconciliation of a Satellites network interfaces now also deletes unneeded interfaces.</li> <li>Satellites try to detect the LVM configuration on the host, reusing locks and udev rules if available.</li> <li>Updated images:<ul> <li>LINSTOR 1.29.2</li> <li>LINSTOR CSI 1.6.4</li> <li>DRBD Reactor 1.5.0</li> <li>LINSTOR HA Controller 1.2.2</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v260-2024-09-04","title":"v2.6.0 - 2024-09-04","text":""},{"location":"CHANGELOG/#added_1","title":"Added","text":"<ul> <li>Support wildcard patterns when referencing property values from node labels and annotations.</li> </ul>"},{"location":"CHANGELOG/#changed_2","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>LINSTOR 1.29.0</li> <li>DRBD 9.2.11</li> <li>Latest CSI Sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v252-2024-07-17","title":"v2.5.2 - 2024-07-17","text":""},{"location":"CHANGELOG/#added_2","title":"Added","text":"<ul> <li>Option to specify custom CA certificate resources for TLS configuration.</li> <li>Ensure all Certificate resources have <code>dnsNames</code> set.</li> </ul>"},{"location":"CHANGELOG/#changed_3","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>LINSTOR 1.28.0</li> <li>LINSTOR CSI 1.6.3</li> <li>DRBD 9.2.10</li> <li>DRBD Reactor 1.4.1</li> <li>kTLS-utils 0.11</li> <li>Latest CSI sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed","title":"Fixed","text":"<ul> <li>The operator will no longer restart reconciliation on every change to <code>ServiceAccount</code> resources.</li> </ul>"},{"location":"CHANGELOG/#v251-2024-05-02","title":"v2.5.1 - 2024-05-02","text":""},{"location":"CHANGELOG/#added_3","title":"Added","text":"<ul> <li>Default PriorityClasses for all components</li> </ul>"},{"location":"CHANGELOG/#changed_4","title":"Changed","text":"<ul> <li>New DRBD loader detection for:<ul> <li>Ubuntu Noble Numbat (24.04)</li> </ul> </li> <li>Updated images:<ul> <li>LINSTOR 1.27.1</li> <li>LINSTOR CSI 1.6.0</li> <li>DRBD 9.2.9</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v250-2024-04-03","title":"v2.5.0 - 2024-04-03","text":""},{"location":"CHANGELOG/#added_4","title":"Added","text":"<ul> <li>Support for managing ZFS Storage Pools using <code>LinstorSatelliteConfiguration</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_5","title":"Changed","text":"<ul> <li>Updated images:<ul> <li>LINSTOR 1.27.0</li> <li>LINSTOR CSI 1.5.0</li> <li>High Availability Controller 1.2.1</li> <li>Latest CSI sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v241-2024-03-06","title":"v2.4.1 - 2024-03-06","text":""},{"location":"CHANGELOG/#added_5","title":"Added","text":"<ul> <li>New DRBD loader detection for:<ul> <li>Debian 12 (Bookworm)</li> <li>Rocky Linux 8 &amp; 9</li> </ul> </li> <li>Report <code>seLinuxMount</code> capability for the CSI Driver, speeding up volume mounts with SELinux   relabelling enabled.</li> <li>Alerts for offline LINSTOR Controller and Satellites.</li> </ul>"},{"location":"CHANGELOG/#changed_6","title":"Changed","text":"<ul> <li>Use node label instead of pod name for Prometheus alerting descriptions.</li> <li>Updated images:<ul> <li>LINSTOR 1.26.2</li> <li>DRBD 9.2.8</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v240-2024-01-30","title":"v2.4.0 - 2024-01-30","text":""},{"location":"CHANGELOG/#added_6","title":"Added","text":"<ul> <li>Validating Webhook for Piraeus StorageClasses.</li> </ul>"},{"location":"CHANGELOG/#breaking","title":"Breaking","text":"<ul> <li>Use DaemonSet to manage Satellite resources instead of bare Pods. This enables better integration with   common administrative tasks such as node draining. This change should be transparent for users, any patches   applied on the satellite Pods are internally converted to work on the new DaemonSet instead.</li> </ul>"},{"location":"CHANGELOG/#changed_7","title":"Changed","text":"<ul> <li>Change default monitoring address for DRBD Reactor to support systems with IPv6 completely disabled.</li> <li>Updated images:<ul> <li>LINSTOR 1.26.1</li> <li>LINSTOR CSI 1.4.0</li> <li>DRBD 9.2.7</li> <li>High Availability Controller 1.2.0</li> <li>Latest CSI sidecars</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v230-2023-12-05","title":"v2.3.0 - 2023-12-05","text":""},{"location":"CHANGELOG/#added_7","title":"Added","text":"<ul> <li>Add a new option <code>.spec.internalTLS.tlsHandshakeDaemon</code> to enable deployment of <code>tlshd</code> alongside the LINSTOR   Satellite.</li> <li>Shortcuts to configure specific components. Components can be disabled by setting <code>enabled: false</code>, and the deployed   workload can be influenced using the <code>podTemplate</code> value. Available components:<ul> <li><code>LinstorCluster.spec.controller</code></li> <li><code>LinstorCluster.spec.csiController</code></li> <li><code>LinstorCluster.spec.csiNode</code></li> <li><code>LinstorCluster.spec.highAvailabilityController</code></li> </ul> </li> <li>Shortcut to modify the pod of a satellite by adding a <code>LinstorSatelliteConfiguration.spec.podTemplate</code>, which is   a shortcut for creating a <code>.spec.patches</code> patch.</li> </ul>"},{"location":"CHANGELOG/#changed_8","title":"Changed","text":"<ul> <li>Fixed service resources relying on default protocol version.</li> <li>Moved NetworkPolicy for DRBD out of default deployed resources.</li> <li>Updated images:<ul> <li>LINSTOR 1.25.1</li> <li>LINSTOR CSI 1.3.0</li> <li>DRBD Reactor 1.4.0</li> <li>Latest CSI sidecars</li> </ul> </li> <li>Add a default toleration for the HA Controller taints to the operator.</li> </ul>"},{"location":"CHANGELOG/#v220-2023-08-31","title":"v2.2.0 - 2023-08-31","text":""},{"location":"CHANGELOG/#added_8","title":"Added","text":"<ul> <li>A new <code>LinstorNodeConnection</code> resource, used to configure the LINSTOR Node Connection feature in a Kubernetes way.</li> <li>Allow image configuration to be customized by adding additional items to the config map. Items using a \"greater\" key   take precedence when referencing the same images.</li> <li>Add image configuration for CSI sidecars.</li> <li>Check kernel module parameters for DRBD on load.</li> <li>Automatically set SELinux labels when loading kernel modules.</li> <li>Allow more complex node selection by adding <code>LinstorCluster.spec.nodeAffinity</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_9","title":"Changed","text":"<ul> <li>Upgrade to operator-sdk 1.29</li> <li>Upgrade to kubebuilder v4 layout</li> <li>Updated images:<ul> <li>LINSTOR 1.24.2</li> <li>LINSTOR CSI 1.2.3</li> <li>DRBD 9.2.5</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#removed","title":"Removed","text":"<ul> <li>Disable operator metrics by default. This removes a dependency on an external container.</li> <li>Dependency on cert-manager for initial deployment.</li> </ul>"},{"location":"CHANGELOG/#fixed_1","title":"Fixed","text":"<ul> <li>A crash caused by insufficient permissions on the LINSTOR Controller.</li> <li>Satellite will now restart if the Pods terminated for unexpected reasons.</li> </ul>"},{"location":"CHANGELOG/#v211-2023-05-24","title":"v2.1.1 - 2023-05-24","text":""},{"location":"CHANGELOG/#added_9","title":"Added","text":"<ul> <li>LINSTOR Controller deployment now runs DB migrations as a separate init container, creating   a backup of current DB state if needed.</li> <li>Apply global rate limit to LINSTOR API, defaulting to 100 qps.</li> </ul>"},{"location":"CHANGELOG/#changed_10","title":"Changed","text":"<ul> <li>Store LINSTOR Satellite logs on the host.</li> <li>Updated images:<ul> <li>LINSTOR 1.23.0</li> <li>LINSTOR CSI 1.1.0</li> <li>DRBD Reactor 1.2.0</li> <li>HA Controller 1.1.4</li> <li>external CSI images upgraded to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_2","title":"Fixed","text":"<ul> <li>Fixed a bug where <code>LinstorSatellite</code> resources would be not be cleaned up when the satellite is already gone.</li> <li>Fixed a bug where the LINSTOR Controller would never report readiness when TLS is enabled.</li> <li>Fixed order in which patches are applied. Always apply user patches last.</li> </ul>"},{"location":"CHANGELOG/#v210-2023-04-24","title":"v2.1.0 - 2023-04-24","text":""},{"location":"CHANGELOG/#added_10","title":"Added","text":"<ul> <li>Ability to skip deploying the LINSTOR Controller by setting <code>LinstorCluster.spec.externalController</code>.</li> <li>Automatically reconcile changed image configuration.</li> </ul>"},{"location":"CHANGELOG/#changed_11","title":"Changed","text":"<ul> <li>Fix an issue where the CSI node driver would use the CSI socket not through the expected path in the container.</li> <li>Updated images:<ul> <li>LINSTOR 1.22.0</li> <li>LINSTOR CSI 1.0.1</li> <li>DRBD 9.2.3</li> <li>DRBD Reactor 1.1.0</li> <li>HA Controller 1.1.3</li> <li>external CSI images upgraded to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v201-2023-03-08","title":"v2.0.1 - 2023-03-08","text":""},{"location":"CHANGELOG/#added_11","title":"Added","text":"<ul> <li><code>drbd-shutdown-guard</code> init-container, installing a systemd unit that runs on shutdown.   It's purpose is to run <code>drbdsetup secondary --force</code> during shutdown, so that systemd can unmount all volumes, even   with <code>suspend-io</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_12","title":"Changed","text":"<ul> <li>Updated LINSTOR CSI to 1.0.0, mounting the <code>/run/mount</code> directory from the host to enable the <code>_netdev</code> mount option.</li> </ul>"},{"location":"CHANGELOG/#fixed_3","title":"Fixed","text":"<ul> <li>HA Controller deployment requires additional rules to run on OpenShift.</li> </ul>"},{"location":"CHANGELOG/#v200-2023-02-23","title":"v2.0.0 - 2023-02-23","text":""},{"location":"CHANGELOG/#breaking_1","title":"Breaking","text":"<ul> <li>Removed existing CRD <code>LinstorController</code>, <code>LinstorSatelliteSet</code> and <code>LinstorCSIDriver</code>.</li> <li>Helm chart deprecated in favor of new <code>kustomize</code> deployment.</li> <li>Helm chart changed to only deploy the Operator. The LinstorCluster resource to create the storage cluster needs to be   created separately.</li> </ul>"},{"location":"CHANGELOG/#added_12","title":"Added","text":"<ul> <li>New CRDs to control storage cluster: <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code>.</li> <li>Tutorials on how to get started.</li> <li>Automatic selection of loader images based on operating system of node.</li> <li>Customization of single nodes or groups of nodes.</li> <li>Possibility to run DRBD replication using the container network.</li> <li>Support for file system backed storage pools</li> <li>Default deployment for HA Controller. Since we switch to defaulting to <code>suspend-io</code> for lost quorum, we should include   a way for Pods to get unstuck.</li> </ul>"},{"location":"CHANGELOG/#v1100-2022-10-18","title":"v1.10.0 - 2022-10-18","text":""},{"location":"CHANGELOG/#added_13","title":"Added","text":"<ul> <li>Can set the variable <code>mountDrbdResourceDirectoriesFromHost</code> in the Helm chart to create hostPath Volumes for DRBD and   LINSTOR configuration directories for the satellite set.</li> </ul>"},{"location":"CHANGELOG/#changed_13","title":"Changed","text":"<ul> <li>Change default bind address for satellite monitoring to use IPv6 anylocal <code>[::]</code>. This will still to work on IPv4   only systems with IPv6 disabled via sysctl.</li> <li>Default images:<ul> <li>LINSTOR 1.20.0</li> <li>DRBD 9.1.11</li> <li>DRBD Reactor 0.9.0</li> <li>external CSI images upgraded to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_4","title":"Fixed","text":"<ul> <li>Comparing IP addresses for registered components uses golang's built-in net.IP type.</li> <li>Restoring satellites after eviction only happens if the node is ready.</li> </ul>"},{"location":"CHANGELOG/#v191-2022-07-27","title":"v1.9.1 - 2022-07-27","text":""},{"location":"CHANGELOG/#fixed_5","title":"Fixed","text":"<ul> <li>ServiceMonitor resources can't be patched, instead we recreate them.</li> </ul>"},{"location":"CHANGELOG/#v190-2022-07-20","title":"v1.9.0 - 2022-07-20","text":""},{"location":"CHANGELOG/#added_14","title":"Added","text":"<ul> <li>Support for custom labels and annotations with added options to <code>values.yaml</code>.</li> <li>Instructions for deploying the affinity controller.</li> </ul>"},{"location":"CHANGELOG/#changed_14","title":"Changed","text":"<ul> <li>Satellite operator now reports basic satellite status even if controller is not reachable</li> <li>Query single satellite devices to receive errors when the satellite is offline instead of assuming   devices are already configured.</li> <li>Disabled the legacy HA Controller deployment by default. It has been replaced a   separate chart.</li> <li>Default images:<ul> <li>LINSTOR 1.19.1</li> <li>LINSTOR CSI 0.20.0</li> <li>DRBD 9.1.8</li> <li>DRBD Reactor 0.8.0</li> <li>external CSI images to latest versions</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_6","title":"Fixed","text":"<ul> <li><code>last-applied-configuration</code>annotation was never updated, so updating of some fields was not performed correctly.</li> </ul>"},{"location":"CHANGELOG/#v182-2022-05-24","title":"v1.8.2 - 2022-05-24","text":""},{"location":"CHANGELOG/#added_15","title":"Added","text":"<ul> <li>Option to disable creating monitoring resources (Services and ServiceMonitors)</li> <li>Add options <code>csi.controllerSidecars</code>, <code>csi.controllerExtraVolumes</code>, <code>csi.nodeSidecars</code>, <code>csi.nodeExtraVolumes</code>,   <code>operator.controller.sidecars</code>, <code>operator.controller.extraVolumes</code>, <code>operator.satelliteSet.sidecars</code>,   <code>operator.satelliteSet.extraVolumes</code> to allow specifying extra sidecar containers.</li> <li>Add options <code>operator.controller.httpBindAddress</code>, <code>operator.controller.httpsBindAddress</code>,   <code>operator.satelliteSet.monitoringBindAddress</code> to allow specifying bind address.</li> <li>Add example values and doc reference to run piraeus-operator with rbac-proxy.</li> </ul>"},{"location":"CHANGELOG/#changed_15","title":"Changed","text":"<ul> <li>Default images:<ul> <li>LINSTOR 1.18.2</li> <li>LINSTOR CSI 0.19.1</li> <li>DRBD Reactor 0.7.0</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#removed_1","title":"Removed","text":"<ul> <li>Get rid of operator-sdk binary, use native controller-gen instead</li> </ul>"},{"location":"CHANGELOG/#v181-2022-05-12","title":"v1.8.1 - 2022-05-12","text":""},{"location":"CHANGELOG/#changed_16","title":"Changed","text":"<ul> <li>Default images:<ul> <li>LINSTOR 1.18.1</li> <li>LINSTOR CSI 0.19.0</li> <li>DRBD 9.1.7</li> <li>DRBD Reactor 0.6.1</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#added_16","title":"Added","text":"<ul> <li>Upgrades involving k8s databases no long require manually confirming a backup exists using   <code>--set IHaveBackedUpAllMyLinstorResources=true</code>.</li> </ul>"},{"location":"CHANGELOG/#v180-2022-03-15","title":"v1.8.0 - 2022-03-15","text":""},{"location":"CHANGELOG/#added_17","title":"Added","text":"<ul> <li>Allow setting the number of parallel requests created by the CSI sidecars. This limits the load on the LINSTOR   backend, which could easily overload when creating many volumes at once.</li> <li>Unify certificates format for SSL enabled installation, no more java tooling required.</li> <li>Automatic certificates generation using Helm or Cert-manager</li> <li>HA Controller and CSI components now wait for the LINSTOR API to be initialized using InitContainers.</li> </ul>"},{"location":"CHANGELOG/#changed_17","title":"Changed","text":"<ul> <li>Create backups of LINSTOR resource if the \"k8s\" database backend is used and an image change is detected. Backups   are stored in Secret resources as a <code>tar.gz</code>. If the secret would get too big, the backup can be downloaded from   the operator pod.</li> <li>Default images:<ul> <li>LINSTOR 1.18.0</li> <li>LINSTOR CSI 0.18.0</li> <li>DRBD 9.1.6</li> <li>DRBD Reactor 0.5.3</li> <li>LINSTOR HA Controller 0.3.0</li> <li>CSI Attacher v3.4.0</li> <li>CSI Node Driver Registrar v2.4.0</li> <li>CSI Provisioner v3.1.0</li> <li>CSI Snapshotter v5.0.1</li> <li>CSI Resizer v1.4.0</li> <li>Stork v2.8.2</li> </ul> </li> <li>Stork updated to support Kubernetes v1.22+.</li> <li>Satellites no longer have a readiness probe defined. This caused issues in the satellites by repeatedly opening   unexpected connections, especially when using SSL.</li> <li>Only query node devices if a storage pool needs to be created.</li> <li>Use cached storage pool response to avoid causing excessive load on LINSTOR satellites.</li> <li>Protect LINSTOR passphrase from accidental deletion by using a finalizer.</li> </ul>"},{"location":"CHANGELOG/#breaking_2","title":"Breaking","text":"<ul> <li>If you have SSL configured, then the certificates must be regenerated in PEM format.   Learn more in the upgrade guide.</li> </ul>"},{"location":"CHANGELOG/#v171-2022-01-18","title":"v1.7.1 - 2022-01-18","text":""},{"location":"CHANGELOG/#added_18","title":"Added","text":"<ul> <li>Allow the external-provisioner and external-snapshotter access to secrets. This is required to support StorageClass   and SnapshotClass secrets.</li> <li>Instruct external-provisioner to pass PVC name+namespace to the CSI driver, enabling optional support for PVC based   names for LINSTOR volumes.</li> <li>Allow setting the log level of LINSTOR components via CRs. Other components are left using their default log level.   The new default log level is INFO (was DEBUG previously, which was often too verbose).</li> <li>Override the kernel source directory used when compiling DRBD (defaults to /usr/src). See    <code>operator.satelliteSet.kernelModuleInjectionAdditionalSourceDirectory</code></li> <li>etcd-chart: add option to set priorityClassName.</li> </ul>"},{"location":"CHANGELOG/#fixed_7","title":"Fixed","text":"<ul> <li>Use correct secret name when setting up TLS for satellites</li> <li>Correctly configure ServiceMonitor resource if TLS is enabled for LINSTOR Controller.</li> </ul>"},{"location":"CHANGELOG/#v170-2021-12-14","title":"v1.7.0 - 2021-12-14","text":""},{"location":"CHANGELOG/#added_19","title":"Added","text":"<ul> <li><code>pv-hostpath</code>: automatically determine on which nodes PVs should be created if no override is given.</li> <li>Automatically add labels on Kubernetes Nodes to LINSTOR satellites as Auxiliary Properties. This enables using   Kubernetes labels for volume scheduling, for example using <code>replicasOnSame: topology.kubernetes.io/zone</code>.</li> <li>Support LINSTORs <code>k8s</code> backend by adding the necessary RBAC resources and documentation.</li> <li>Automatically create a LINSTOR passphrase when none is configured.</li> <li>Automatic eviction and deletion of offline satellites if the Kubernetes node object was also deleted.</li> </ul>"},{"location":"CHANGELOG/#changed_18","title":"Changed","text":"<ul> <li>Default images:<ul> <li><code>quay.io/piraeusdatastore/piraeus-server:v1.17.0</code></li> <li><code>quay.io/piraeusdatastore/piraeus-csi:v0.17.0</code></li> <li><code>quay.io/piraeusdatastore/drbd9-bionic:v9.1.4</code></li> <li><code>quay.io/piraeusdatastore/drbd-reactor:v0.4.4</code></li> </ul> </li> <li>Recreates or updates to the satellite pods are now applied at once, instead of waiting for a node to complete before   moving to the next.</li> <li>Enable CSI topology by default, allowing better volume scheduling with <code>volumeBindingMode: WaitForFirstConsumer</code>.</li> <li>Disable STORK by default. Instead, we recommend using <code>volumeBindingMode: WaitForFirstConsumer</code> in storage classes.</li> </ul>"},{"location":"CHANGELOG/#v160-2021-09-02","title":"v1.6.0 - 2021-09-02","text":""},{"location":"CHANGELOG/#added_20","title":"Added","text":"<ul> <li>Allow CSI to work with distributions that use a kubelet working directory other than <code>/var/lib/kubelet</code>. See   the <code>csi.kubeletPath</code> option.</li> <li>Enable Storage Capacity Tacking. This enables Kubernetes to base Pod scheduling decisions on remaining storage   capacity. The feature is in beta and enabled by default starting with Kubernetes 1.21.</li> </ul>"},{"location":"CHANGELOG/#changed_19","title":"Changed","text":"<ul> <li> <p>Disable Stork Health Monitoring by default. Stork cannot distinguish between control plane and data plane issues,   which can lead to instances where Stork will migrate a volume that is still mounted on another node, making the   volume effectively unusable.</p> </li> <li> <p>Updated operator to kubernetes v1.21 components.</p> </li> <li> <p>Default images:</p> <ul> <li><code>quay.io/piraeusdatastore/piraeus-server:v1.14.0</code></li> <li><code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.30</code></li> <li><code>quay.io/piraeusdatastore/drbd-reactor:v0.4.3</code></li> <li><code>quay.io/piraeusdatastore/piraeus-ha-controller:v0.2.0</code></li> <li>external CSI images</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#removed_2","title":"Removed","text":"<ul> <li>The cluster-wide snapshot controller is no longer deployed as a dependency of the piraeus-operator chart.   Instead, separate charts are available on artifacthub.io   that deploy the snapshot controller and extra validation for snapshot resources.</li> </ul> <p>The subchart was removed, as it unnecessarily tied updates of the snapshot controller to piraeus and vice versa. With   the tightened validation starting with snapshot CRDs <code>v1</code>, moving the snapshot controller to a proper chart seems   like a good solution.</p>"},{"location":"CHANGELOG/#v151-2021-06-21","title":"v1.5.1 - 2021-06-21","text":""},{"location":"CHANGELOG/#changed_20","title":"Changed","text":"<ul> <li>Default images:<ul> <li>Piraeus Server v1.13.0</li> <li>Piraeus CSI v0.13.1</li> <li>CSI Provisioner v2.1.2</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v150-2021-05-12","title":"v1.5.0 - 2021-05-12","text":""},{"location":"CHANGELOG/#added_21","title":"Added","text":"<ul> <li>All operator-managed workloads apply recommended labels. This requires the recreation of Deployments and DaemonSets   on upgrade. This is automatically handled by the operator, however any customizations applied to the deployments   not managed by the operator will be reverted in the process.</li> <li>Use <code>drbd-reactor</code> to expose Prometheus endpoints on each satellite.</li> <li>Configure <code>ServiceMonitor</code> resources if they are supported by the cluster (i.e. prometheus operator is configured)</li> </ul>"},{"location":"CHANGELOG/#changed_21","title":"Changed","text":"<ul> <li>CSI Nodes no longer use <code>hostNetwork: true</code>. The pods already got the correct hostname via the downwardAPI and do not   talk to DRBD's netlink interface directly.</li> <li>External: CSI snapshotter subchart now packages <code>v1</code> CRDs. Fixes deprecation warnings when installing   the snapshot controller.</li> <li>Default images:<ul> <li>Piraeus Server v1.12.3</li> <li>Piraeus CSI v0.13.0</li> <li>DRBD v9.0.29</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v140-2021-04-07","title":"v1.4.0 - 2021-04-07","text":""},{"location":"CHANGELOG/#added_22","title":"Added","text":"<ul> <li>Additional environment variables and Linstor properties can now be set in the <code>LinstorController</code> CRD.</li> <li>Set node name variable for Controller Pods, enabling k8s-await-election to correctly set up the endpoint for   hairpin mode.</li> </ul>"},{"location":"CHANGELOG/#fixed_8","title":"Fixed","text":"<ul> <li>Update the network address of controller pods if they diverged between Linstor and kubernetes. This can happen after   a node restart, where a pod is recreated with the same name but different IP address.</li> </ul>"},{"location":"CHANGELOG/#v131-2021-01-14","title":"v1.3.1 - 2021-01-14","text":""},{"location":"CHANGELOG/#added_23","title":"Added","text":"<ul> <li>New guide on host preparation here.</li> </ul>"},{"location":"CHANGELOG/#changed_22","title":"Changed","text":"<ul> <li>Default image updated:<ul> <li><code>operator.satelliteSet.kernelModuleInjectionImage</code>: <code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.27</code></li> <li><code>operator.satelliteSet.satelliteImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.1</code></li> <li><code>operator.controller.controllerImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.1</code></li> <li><code>haController.image</code>: <code>quay.io/piraeusdatastore/piraeus-ha-controller:v0.1.3</code></li> <li><code>pv-hostpath</code>: <code>chownerImage</code>: <code>quay.io/centos/centos:8</code></li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v130-2020-12-21","title":"v1.3.0 - 2020-12-21","text":""},{"location":"CHANGELOG/#added_24","title":"Added","text":"<ul> <li>New component: <code>haController</code> will deploy the Piraeus High Availability Controller.   More information is available in   the optional components page</li> <li>Enable strict checking of DRBD parameter to disable usermode helper in container environments.</li> <li>Override the image used in \"chown\" jobs in the <code>pv-hostpath</code> chart by using <code>--set chownerImage=&lt;my-image&gt;</code>.</li> </ul>"},{"location":"CHANGELOG/#changed_23","title":"Changed","text":"<ul> <li>Updated <code>operator-sdk</code> to v0.19.4</li> <li>Set CSI component timeout to 1 minute to reduce the number of retries in the CSI driver</li> <li>Default images updated:<ul> <li><code>operator.controller.controllerImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.0</code></li> <li><code>operator.satelliteSet.satelliteImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.11.0</code></li> <li><code>operator.satelliteSet.kernelModuleInjectionImage</code>: <code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.26</code></li> <li><code>csi.pluginImage</code>: <code>quay.io/piraeusdatastore/piraeus-csi:v0.11.0</code></li> </ul> </li> </ul>"},{"location":"CHANGELOG/#fixed_9","title":"Fixed","text":"<ul> <li>Fixed Helm warnings when setting \"csi.controllerAffinity\", \"operator.controller.affinity\" and   \"operator.satelliteSet.storagePools\".</li> </ul>"},{"location":"CHANGELOG/#v120-2020-11-18","title":"v1.2.0 - 2020-11-18","text":""},{"location":"CHANGELOG/#added_25","title":"Added","text":"<ul> <li><code>storagePools</code> can now also set up devices similar to <code>automaticStorageType</code>, but with more fine grained control.   See the updated storage guide</li> <li>New Helm options to disable creation of LinstorController and LinstorSatelliteSet resource   <code>operator.controller.enabled</code> and <code>operator.satelliteSet.enabled</code>.</li> <li>New Helm option to override the generated controller endpoint: <code>controllerEndpoint</code></li> <li>Allow overriding the default <code>securityContext</code> on a component basis:<ul> <li><code>etcd.podsecuritycontext</code> sets the securityContext of etcd pods</li> <li><code>stork.podsecuritycontext</code> sets the securityContext of stork plugin and scheduler pods</li> <li><code>csi-snapshotter.podsecuritycontext</code> sets the securityContext of the CSI-Snapshotter pods</li> <li><code>operator.podsecuritycontext</code> sets the securityContext of the operator pods</li> </ul> </li> <li>Example settings for openshift</li> <li>LINSTOR controller runs with additional GID 1000, to ensure write access to log directory</li> </ul>"},{"location":"CHANGELOG/#changed_24","title":"Changed","text":"<ul> <li>Fixed a bug in <code>pv-hostpath</code> where permissions on the created directory are not applied on all nodes.</li> <li>Volumes created by <code>pv-hostpath</code> are now group writable. This makes them easier to integrate with <code>fsGroup</code> settings.</li> <li>Default value for affinity on LINSTOR controller and CSI controller changed. The new default is to distribute the pods   across all available nodes.</li> <li>Default value for tolerations for etcd pods changed. They are now able to run on master nodes.</li> <li>Updates to LinstorController, LinstorSatelliteSet and LinstorCSIDriver are now propagated across all created resources</li> <li>Updated default images:<ul> <li>csi sidecar containers updated (compatible with Kubernetes v1.17+)</li> <li>LINSTOR 1.10.0</li> <li>LINSTOR CSI 0.10.0</li> </ul> </li> </ul>"},{"location":"CHANGELOG/#deprecation","title":"Deprecation","text":"<ul> <li>Using <code>automaticStorageType</code> is deprecated. Use the <code>storagePools</code> values instead.</li> </ul>"},{"location":"CHANGELOG/#v110-2020-10-13","title":"v1.1.0 - 2020-10-13","text":""},{"location":"CHANGELOG/#breaking_3","title":"Breaking","text":"<ul> <li>The LINSTOR controller image given in <code>operator.controller.controllerImage</code> has to have   its entrypoint set to <code>k8s-await-election v0.2.0</code>   or newer. Learn more in the upgrade guide.</li> </ul>"},{"location":"CHANGELOG/#added_26","title":"Added","text":"<ul> <li>LINSTOR controller can be started with multiple replicas. See  <code>operator.controller.replicas</code>.   NOTE: This requires support from the container. You need <code>piraeus-server:v1.8.0</code> or newer.</li> <li>The <code>pv-hostpath</code> helper chart automatically sets up permissions for non-root etcd containers.</li> <li>Disable securityContext enforcement by setting <code>global.setSecurityContext=false</code>.</li> <li>Add cluster roles to work with OpenShift's SCC system.</li> <li>Control volume placement and accessibility by using CSIs Topology feature. Controlled by setting   <code>csi.enableTopology</code>.</li> <li>All pods use a dedicated service account to allow for fine-grained permission control.</li> <li>The new helm section <code>psp.*</code> can automatically configure the ServiceAccount   of all components to use the appropriate PSP roles.</li> </ul>"},{"location":"CHANGELOG/#changed_25","title":"Changed","text":"<ul> <li>Default values:<ul> <li><code>operator.controller.controllerImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.9.0</code></li> <li><code>operator.satelliteSet.satelliteImage</code>: <code>quay.io/piraeusdatastore/piraeus-server:v1.9.0</code></li> <li><code>operator.satelliteSet.kernelModuleInjectionImage</code>: <code>quay.io/piraeusdatastore/drbd9-bionic:v9.0.25</code></li> <li><code>stork.storkImage</code>: <code>docker.io/openstorage/stork:2.5.0</code></li> </ul> </li> <li>linstor-controller no longer starts in a privileged container.</li> </ul>"},{"location":"CHANGELOG/#removed_3","title":"Removed","text":"<ul> <li>legacy CRDs (LinstorControllerSet, LinstorNodeSet) have been removed.</li> <li><code>v1alpha</code> CRD versions have been removed.</li> <li>default pull secret <code>drbdiocred</code> removed. To keep using it, use <code>--set drbdRepoCred=drbdiocred</code>.</li> </ul>"},{"location":"CHANGELOG/#v100-2020-08-06","title":"v1.0.0 - 2020-08-06","text":""},{"location":"CHANGELOG/#added_27","title":"Added","text":"<ul> <li><code>v1</code> of all CRDs</li> <li>Central value for controller image pull policy of all pods. Use <code>--set global.imagePullPolicy=&lt;value&gt;</code> on   helm deployment.</li> <li><code>charts/piraeus/values.cn.yaml</code> a set of helm values for faster image download for CN users.</li> <li>Allow specifying resource requirements for all pods. In helm you can set:<ul> <li><code>etcd.resources</code> for etcd containers</li> <li><code>stork.storkResources</code> for stork plugin resources</li> <li><code>stork.schedulerResources</code> for the kube-scheduler deployed for use with stork</li> <li><code>csi-snapshotter.resources</code> for the cluster snapshotter controller</li> <li><code>csi.resources</code> for all CSI related containers. for brevity, there is only one setting for ALL CSI containers.   They   are all stateless go process which use the same amount of resources.</li> <li><code>operator.resources</code> for operator containers</li> <li><code>operator.controller.resources</code> for LINSTOR controller containers</li> <li><code>operator.satelliteSet.resources</code> for LINSTOR satellite containers</li> <li><code>operator.satelliteSet.kernelModuleInjectionResources</code> for kernel module injector/builder containers</li> </ul> </li> <li>Components deployed by the operator can now run with multiple replicas. Components   elect a leader, that will take on the actual work as long as it is active. Should one   pod go down, another replica will take over.   Currently these components support multiple replicas:<ul> <li><code>etcd</code> =&gt; set <code>etcd.replicas</code> to the desired count</li> <li><code>stork</code> =&gt; set <code>stork.replicas</code> to the desired count for stork scheduler and controller</li> <li><code>snapshot-controller</code> =&gt; set <code>csi-snapshotter.replicas</code> to the desired count for cluster-wide CSI snapshot   controller</li> <li><code>csi-controller</code> =&gt; set <code>csi.controllerReplicas</code> to the desired count for the linstor CSI controller</li> <li><code>operator</code> =&gt; set <code>operator.replicas</code> to have multiple replicas of the operator running</li> </ul> </li> <li>Reference docs for all helm settings. Link</li> <li><code>stork.schedulerTag</code> can override the automatically chosen tag for the <code>kube-scheduler</code> image.   Previously, the tag always matched the kubernetes release.</li> </ul>"},{"location":"CHANGELOG/#changed_26","title":"Changed","text":"<ul> <li>Renamed <code>LinstorNodeSet</code> to <code>LinstorSatelliteSet</code>. This brings the operator in line with other LINSTOR resources.   Existing <code>LinstorNodeSet</code> resources will automatically be migrated to <code>LinstorSatelliteSet</code>.</li> <li>Renamed <code>LinstorControllerSet</code> to <code>LinstorController</code>. The old name implied the existence of multiple (separate)   controllers. Existing <code>LinstorControllerSet</code> resources will automatically be migrated to <code>LinstorController</code>.</li> <li>Helm values renamed to align with new CRD names:<ul> <li><code>operator.controllerSet</code> to <code>operator.controller</code></li> <li><code>operator.nodeSet</code> to <code>operator.satelliteSet</code></li> </ul> </li> <li> <p>Node scheduling no longer relies on <code>linstor.linbit.com/piraeus-node</code> labels. Instead, all CRDs support   setting pod affinity and tolerations.   In detail:</p> <ul> <li><code>linstorcsidrivers</code> gained 4 new resource keys, with no change in default behaviour:<ul> <li><code>nodeAffinity</code> affinity passed to the csi nodes</li> <li><code>nodeTolerations</code> tolerations passed to the csi nodes</li> <li><code>controllerAffinity</code> affinity passed to the csi controller</li> <li><code>controllerTolerations</code> tolerations passed to the csi controller</li> </ul> </li> <li><code>linstorcontrollerset</code> gained 2 new resource keys, with no change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> <li><code>linstornodeset</code> gained 2 new resource keys, with change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> </ul> </li> <li> <p>Controller is now a Deployment instead of StatefulSet.</p> </li> <li>Renamed <code>kernelModImage</code> to <code>kernelModuleInjectionImage</code></li> <li>Renamed <code>drbdKernelModuleInjectionMode</code> to <code>KernelModuleInjectionMode</code></li> </ul>"},{"location":"CHANGELOG/#v050-2020-06-29","title":"v0.5.0 - 2020-06-29","text":""},{"location":"CHANGELOG/#added_28","title":"Added","text":"<ul> <li>Support volume resizing with newer CSI versions.</li> <li>A new Helm chart <code>csi-snapshotter</code> that deploys extra components needed for volume snapshots.</li> <li> <p>Add new kmod injection mode <code>DepsOnly</code>. Will try load kmods for LINSTOR layers from the host. Deprecates <code>None</code>.</p> </li> <li> <p>Automatic deployment of Stork scheduler configured for LINSTOR.</p> </li> </ul>"},{"location":"CHANGELOG/#removed_4","title":"Removed","text":""},{"location":"CHANGELOG/#changed_27","title":"Changed","text":"<ul> <li>Replaced <code>bitnami/etcd</code> dependency with vendored custom version   Some important keys for the <code>etcd</code> helm chart have changed:<ul> <li><code>statefulset.replicaCount</code> -&gt; <code>replicas</code></li> <li><code>persistence.enabled</code> -&gt; <code>persistentVolume.enabled</code></li> <li><code>persistence.size</code> -&gt; <code>persistentVolume.storage</code></li> <li><code>\u00e0uth.rbac</code> was removed: use tls certificates</li> <li><code>auth.peer.useAutoTLS</code> was removed</li> <li><code>envVarsConfigMap</code> was removed</li> <li>When using etcd with TLS enabled:<ul> <li>For peer communication, peers need valid certificates for <code>*.&lt;release-name&gt;-etcd</code> (was   <code>.&lt;release-name&gt;&gt;-etcd-headless.&lt;namespace&gt;.svc.cluster.local</code>)</li> <li>For client communication, servers need valid certificates for <code>*.&lt;release-name&gt;-etcd</code>  (was   <code>.&lt;release-name&gt;&gt;-etcd.&lt;namespace&gt;.svc.cluster.local</code>)</li> </ul> </li> </ul> </li> </ul>"},{"location":"CHANGELOG/#v041-2020-06-10","title":"v0.4.1 - 2020-06-10","text":""},{"location":"CHANGELOG/#added_29","title":"Added","text":"<ul> <li>Automatic storage pool creation via <code>automaticStorageType</code> on <code>LinstorNodeSet</code>. If this option is set, LINSTOR   will create a storage pool based on all available devices on a node.</li> </ul>"},{"location":"CHANGELOG/#changed_28","title":"Changed","text":"<ul> <li>Moved storage documentation to the storage guide</li> <li>Helm: update default images</li> </ul>"},{"location":"CHANGELOG/#v040-2020-06-05","title":"v0.4.0 - 2020-06-05","text":""},{"location":"CHANGELOG/#added_30","title":"Added","text":"<ul> <li>Secured database connection for Linstor: When using the <code>etcd</code> connector, you can specify a secret containing a CA   certificate to switch from HTTP to HTTPS communication.</li> <li>Secured connection between Linstor components: You can specify TLS keys to secure the communication between   controller and satellite</li> <li>Secure storage with LUKS: You can specify the master passphrase used by Linstor when creating encrypted volumes   when installing via Helm.</li> <li>Authentication with etcd using TLS client certificates.</li> <li>Secured connection between linstor-client and controller (HTTPS). More in   the security guide</li> <li>Linstor controller endpoint can now be customized for all resources. If not specified, the old default values will be   filled in.</li> </ul>"},{"location":"CHANGELOG/#removed_5","title":"Removed","text":"<ul> <li>NodeSet service (<code>piraeus-op-ns</code>) was replaced by the ControllerSet service (<code>piraeus-op-cs</code>) everywhere</li> </ul>"},{"location":"CHANGELOG/#changed_29","title":"Changed","text":"<ul> <li>CSI storage driver setup: move setup from helm to go operator. This is mostly an internal change.   These changes may be of note if you used a non-default CSI configuration:<ul> <li>helm value <code>csi.image</code> was renamed to <code>csi.pluginImage</code></li> <li>CSI deployment can be controlled by a new resource <code>linstorcsidrivers.piraeus.linbit.com</code></li> </ul> </li> <li>PriorityClasses are not automatically created. When not specified, the priority class is:<ul> <li>\"system-node-critical\", if deployed in \"kube-system\" namespace</li> <li>default PriorityClass in other namespaces</li> </ul> </li> <li>RBAC rules for CSI: creation moved to deployment step (Helm/OLM). ServiceAccounts should be specified in CSI resource.   If no ServiceAccounts are named, the implicitly created accounts from previous deployments will be used.</li> <li>Helm: update default images</li> </ul>"},{"location":"CHANGELOG/#v030-2020-05-08","title":"v0.3.0 - 2020-05-08","text":""},{"location":"CHANGELOG/#changed_30","title":"Changed","text":"<ul> <li>Use single values for images in CRDs instead of specifying the version   separately</li> <li>Helm: Use single values for images instead of specifying repo, name and   version separately</li> <li>Helm: Replace fixed storage pool configuration with list</li> <li>Helm: Do not create any storage pools by default</li> <li>Helm: Replace <code>operator.nodeSet.spec</code> and <code>operator.controllerSet.spec</code> by   just <code>operator.nodeSet</code> and <code>operator.controllerSet</code>.</li> </ul>"},{"location":"CHANGELOG/#v022-2020-04-24","title":"v0.2.2 - 2020-04-24","text":""},{"location":"CHANGELOG/#changed_31","title":"Changed","text":"<ul> <li>Fix reporting of errors in LinstorControllerSet status</li> </ul>"},{"location":"CHANGELOG/#v021-2020-04-14","title":"v0.2.1 - 2020-04-14","text":""},{"location":"CHANGELOG/#changed_32","title":"Changed","text":"<ul> <li>Helm: Update LINSTOR server dependencies to fix startup problems</li> </ul>"},{"location":"CHANGELOG/#v020-2020-04-10","title":"v0.2.0 - 2020-04-10","text":""},{"location":"CHANGELOG/#added_31","title":"Added","text":"<ul> <li>Helm: Allow an existing database to be used instead of always setting up   a dedicated etcd instance</li> </ul>"},{"location":"CHANGELOG/#changed_33","title":"Changed","text":"<ul> <li>Rename <code>etcdURL</code> parameter of LinstorControllerSet to <code>dbConnectionURL</code> to   reflect the fact that it can be used for any database type</li> <li>Upgrade to operator-sdk v0.16.0</li> <li>Helm: Create multiple volumes with a single <code>pv-hostchart</code> installation</li> <li>Helm: Update dependencies</li> </ul>"},{"location":"CHANGELOG/#v014-2020-03-05","title":"v0.1.4 - 2020-03-05","text":""},{"location":"CHANGELOG/#added_32","title":"Added","text":"<ul> <li>Helm: Add support for <code>hostPath</code> <code>PersistentVolume</code> persistence of etcd</li> </ul>"},{"location":"CHANGELOG/#removed_6","title":"Removed","text":"<ul> <li>Helm: Remove vendored etcd chart from repository</li> </ul>"},{"location":"CHANGELOG/#changed_34","title":"Changed","text":"<ul> <li>Rename CRDs from Piraeus to Linstor</li> <li>Make priority classes configurable</li> <li>Fix LINSTOR Controller/Satellite arguments</li> <li>Helm: Make etcd persistent by default</li> <li>Helm: Fix deployment of permissions objects into a non-default namespace</li> <li>Helm: Set default etcd size to 1Gi</li> <li>Helm: Update dependent image versions</li> <li>Docker: Change base image to Debian Buster</li> </ul>"},{"location":"CHANGELOG/#v013-2020-02-24","title":"v0.1.3 - 2020-02-24","text":""},{"location":"CHANGELOG/#added_33","title":"Added","text":"<ul> <li>Support for kernel module injection based on shipped modules - necessary for   CoreOS support.</li> </ul>"},{"location":"CHANGELOG/#v0121-2020-02-21","title":"v0.1.2.1 - 2020-02-21","text":""},{"location":"CHANGELOG/#added_34","title":"Added","text":"<ul> <li>/charts contains Helm v3 chart for this operator</li> </ul>"},{"location":"CHANGELOG/#changed_35","title":"Changed","text":"<ul> <li>CRDs contain additional Spec parameters that allow customizing image repo and   tag/version of the image.</li> <li>Another Spec parameter 'drbdRepoCred' can specify the name of the k8s secret   used to access the container images.</li> <li>LINSTOR Controller image now contains the LINSTOR client, away from the   Satellite images as it was previously the case. Hence, the readiness probe   is changed to use <code>curl</code> instead of <code>linstor</code> client command.</li> </ul>"},{"location":"CHANGELOG/#v010-2020-01-27","title":"v0.1.0 - 2020-01-27","text":""},{"location":"CHANGELOG/#added_35","title":"Added","text":"<ul> <li>examples/operator-intra.yaml file to bundle all the rbac, crds, etc to run the   operator</li> <li>EtcdURL field to controllersetcontroller spec. default: etcd-piraeus:2379</li> <li>Host networking on the LINSTOR Satellite pods with DNSClusterFirstWithHostNet   DNS policy</li> <li>NodeSet service for the Satellite pods that also point to the Controller   service for LINSTOR discovery</li> </ul>"},{"location":"CHANGELOG/#removed_7","title":"Removed","text":"<ul> <li><code>ControllerEndpoint</code> and <code>DefaultController</code> from the PiraeusNodeSet spec</li> </ul>"},{"location":"CHANGELOG/#changed_36","title":"Changed","text":"<ul> <li>Controller persistence is now handled by etcd. There must be a reachable and   operable etcd cluster for this operator to work.</li> <li>Networking is now handled by a kubernetes service with the same name   as the ControllerSet. The NodeSet must have the same name as the ControllerSet   for networking to work properly.</li> <li>Opt-in node label for nodes is now <code>linstor.linbit.com/piraeus-node=true</code></li> <li>Remove requirement for <code>kube-system</code> namespace</li> <li>Naming convention for NodeSet and ControllerSet Pods</li> <li>Updated ports for LINSTOR access on NodeSet and ControllerSet pods</li> <li>Updated framework to work with Operator Framework 0.13.0</li> <li>API Versions on PriorityClass, DaemonSet, StatefulSet, and CRD kinds to reflect   K8s 1.16.0 release</li> </ul>"},{"location":"CHANGELOG/#v001-2019-07-19","title":"v0.0.1 - 2019-07-19","text":""},{"location":"CHANGELOG/#added_36","title":"Added","text":"<ul> <li>Initial public version with docs</li> </ul>"},{"location":"explanation/","title":"Understanding Piraeus Datastore","text":"<p>The following documents explain how Piraeus Datastore works, and why it works the way it does.</p>"},{"location":"explanation/#understanding-piraeus-datastore-components","title":"Understanding Piraeus Datastore Components","text":"<p>A short introduction for every component of Piraeus Datastore.</p>"},{"location":"explanation/components/","title":"Understanding Piraeus Datastore Components","text":"<p>Piraeus Datastore consists of several different components. Each component runs as a separate Deployment, DaemonSet or plain Pod.</p> <p>All Pods are labelled according to their component. You can check the Pods running in your own cluster by running the following <code>kubectl</code> command:</p> <pre><code>$ kubectl get pods '-ocustom-columns=NAME:.metadata.name,COMPONENT:.metadata.labels.app\\.kubernetes\\.io/component'\nNAME                                                   COMPONENT\nha-controller-vd82w                                    ha-controller\nlinstor-controller-6c8f8dc47-cm8hr                     linstor-controller\nlinstor-csi-controller-59b9968b86-ftl76                linstor-csi-controller\nlinstor-csi-node-hcmk9                                 linstor-csi-node\nlinstor-satellite-k8s-10.test-66687                    linstor-satellite\npiraeus-operator-controller-manager-6dcfcb4568-6jntp   piraeus-operator\npiraeus-operator-gencert-59449cb449-nzg6z              piraeus-operator-gencert\n</code></pre>"},{"location":"explanation/components/#piraeus-operator","title":"<code>piraeus-operator</code>","text":"<p>The Piraeus Operator creates and maintains the other components, except for the <code>piraeus-operator-gencert</code> component.</p> <p>Along with deploying the needed Kubernetes resources, it maintains the LINSTOR\u00ae Cluster state by:</p> <ul> <li>Registering satellites</li> <li>Creating storage pools</li> <li>Maintaining node labels</li> </ul>"},{"location":"explanation/components/#piraeus-operator-gencert","title":"<code>piraeus-operator-gencert</code>","text":"<p>The \"generate certificate\" Pod creates and maintains the TLS key and certificate used by the Piraeus Operator. The TLS secret, named <code>webhook-server-cert</code>, is needed to start the Piraeus Operator Pod. In addition, this Pod keeps the <code>ValidatingWebhookConfiguration</code> for the Piraeus Operator up-to-date.</p> <p>The Piraeus Operator needs a TLS certificate to serve the validation endpoint for the custom resources it maintains.</p> <p>Historically, TLS certificates where created by <code>cert-manager</code>. This was removed to reduce the number of dependencies for deploying Piraeus Datastore.</p>"},{"location":"explanation/components/#linstor-controller","title":"<code>linstor-controller</code>","text":"<p>The LINSTOR Controller is responsible for resource placement, resource configuration, and orchestration of any operational processes that require a view of the whole cluster. It maintains a database of all the configuration information for the whole cluster, stored as Kubernetes objects.</p> <p>The LINSTOR Controller connects to the LINSTOR Satellites and sends them instructions for achieving the desired cluster state.</p> <p>It provides an external API used by LINSTOR CSI and Piraeus Operator to change the cluster state.</p>"},{"location":"explanation/components/#linstor-satellite","title":"<code>linstor-satellite</code>","text":"<p>The LINSTOR Satellite service runs on each node. It acts as the local configuration agent for LINSTOR managed storage. It is stateless and receives all the information it needs from the LINSTOR Controller.</p> <p>Satellites are started as DaemonSets, managed by the Piraeus Operator. We deploy one DaemonSet per node, this enables having per-node configuration and customization of the Satellite Pods.</p> <p>Satellites interact with the host operating system directly and are deployed as privileged containers. Integration with the host operating system also leads to two noteworthy interactions with Linux namespaces:</p> <ul> <li>Any DRBD\u00ae device will inherit the network namespace of the Satellite Pods. Unless the Satellites are using   host networking, DRBD will not be able to replicate data without a running Satellite Pod. See the   host networking guide for more information.</li> <li>The Satellite process is spawned in a separate UTS namespace: this allows us to keep control of the hostname reported   to DRBD tools, even when the Pod is using a generated name from the DaemonSet. Thus, DRBD connections will always use   the Kubernetes node name.</li> </ul> <p>The use of separate UTS namespace should be completely transparent to users: running <code>kubectl exec ...</code> on a satellite   Pod will drop you into this namespace, enabling you to run <code>drbdadm</code> commands as expected.</p>"},{"location":"explanation/components/#linstor-csi-controller","title":"<code>linstor-csi-controller</code>","text":"<p>The LINSTOR CSI Controller Pod creates, modifies and deletes volumes and snapshots. It translates the state of Kubernetes resources (<code>StorageClass</code>, <code>PersistentVolumeClaims</code>, <code>VolumeSnapshots</code>) into their equivalent in LINSTOR.</p>"},{"location":"explanation/components/#linstor-csi-node","title":"<code>linstor-csi-node</code>","text":"<p>The LINSTOR CSI Node Pods execute mount and unmount operations. Mount and Unmount are initiated by kubelet before starting a Pod with a Piraeus volume.</p> <p>They are deployed as a DaemonSet on every node in the cluster by default. There needs to be a LINSTOR Satellite running on the same node as a CSI Node Pod.</p>"},{"location":"explanation/components/#ha-controller","title":"<code>ha-controller</code>","text":"<p>The Piraeus High Availability Controller will speed up the fail-over process for stateful workloads using Piraeus for storage.</p> <p>It is deployed on every node in the cluster and listens for DRBD\u00ae events to detect storage failures on other nodes. It evicts Pods when it detects that the storage on their node is inaccessible.</p>"},{"location":"how-to/","title":"How To","text":"<p>These guides show you how to configure a specific aspect or achieve a specific task with Piraeus Datastore.</p>"},{"location":"how-to/#advanced-deployments","title":"Advanced Deployments","text":"<ul> <li> <p>Use Piraeus Datastore with an Existing LINSTOR Cluster</p> <p> Guide</p> </li> <li> <p>Configure the DRBD Module Loader</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#securing-components","title":"Securing Components","text":"<ul> <li> <p>Configure TLS Between LINSTOR Controller and LINSTOR Satellite</p> <p> Guide</p> </li> <li> <p>Configure TLS for the LINSTOR API</p> <p> Guide</p> </li> <li> <p>Configure TLS for DRBD Replication</p> <p> Guide</p> </li> <li> <p>Load DRBD with SecureBoot Enabled</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#kubernetes-distributions","title":"Kubernetes Distributions","text":"<ul> <li> <p>Deploy Piraeus Datastore on OpenShift</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on Talos Linux</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on Flatcar Container Linux</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on MicroK8s</p> <p> Guide</p> </li> <li> <p>Deploy Piraeus Datastore on k0s</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#networking","title":"Networking","text":"<ul> <li> <p>Deploy Piraeus Datastore behind an HTTP Proxy</p> <p> Guide</p> </li> <li> <p>Deploy a NetworkPolicy for Piraeus Datastore</p> <p> Guide</p> </li> <li> <p>Use the Host Network for DRBD Replication</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/#maintenance-tasks","title":"Maintenance Tasks","text":"<ul> <li> <p>Monitor Piraeus Datastore with Prometheus Operator</p> <p> Guide</p> </li> <li> <p>Keep Persistent Volume Affinity Updated with LINSTOR Affinity Controller</p> <p> Guide</p> </li> <li> <p>Restore a LINSTOR Database Backup</p> <p> Guide</p> </li> </ul>"},{"location":"how-to/api-tls/","title":"How to Configure TLS for the LINSTOR API","text":"<p>This guide shows you how to set up TLS for the LINSTOR\u00ae API. The API, served by the LINSTOR Controller, is used by clients such as the CSI Driver and the Operator itself to control the LINSTOR Cluster.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> <li>using either cert-manager or <code>openssl</code> to create TLS certificates.</li> </ul>"},{"location":"how-to/api-tls/#provision-keys-and-certificates-using-cert-manager","title":"Provision Keys and Certificates Using cert-manager","text":"<p>This method requires a working cert-manager deployment in your cluster. For an alternative way to provision keys and certificates, see the <code>openssl</code> section below.</p> <p>When using TLS, the LINSTOR API uses client certificates for authentication. It is good practice to have a separate CA just for these certificates.</p> <pre><code>---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: ca-bootstrapper\n  namespace: piraeus-datastore\nspec:\n  selfSigned: { }\n---\napiVersion: cert-manager.io/v1\nkind: Certificate\nmetadata:\n  name: linstor-api-ca\n  namespace: piraeus-datastore\nspec:\n  commonName: linstor-api-ca\n  secretName: linstor-api-ca\n  duration: 87600h # 10 years\n  isCA: true\n  usages:\n    - signing\n    - key encipherment\n    - cert sign\n  issuerRef:\n    name: ca-bootstrapper\n    kind: Issuer\n---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: linstor-api-ca\n  namespace: piraeus-datastore\nspec:\n  ca:\n    secretName: linstor-api-ca\n</code></pre> <p>Then, configure this new issuer to let the Operator provision the needed certificates:</p> <pre><code>---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    certManager:\n      name: linstor-api-ca\n      kind: Issuer\n</code></pre> <p>This completes the necessary steps for secure the LINSTOR API with TLS using cert-manager. Skip to the last section to verify TLS is working.</p>"},{"location":"how-to/api-tls/#provision-keys-and-certificates-using-openssl","title":"Provision Keys and Certificates Using <code>openssl</code>","text":"<p>If you completed the cert-manager section above, skip directly to the verifying the configuration below.</p> <p>This method requires the <code>openssl</code> program on the command line. For an alternative way to provision keys and certificates, see the cert-manager section above.</p> <p>First, create a new Certificate Authority using a new key and a self-signed certificate, valid for 10 years:</p> <pre><code>openssl req -new -newkey rsa:4096 -days 3650 -nodes -x509 -keyout ca.key -out ca.crt -subj \"/CN=linstor-api-ca\"\n</code></pre> <p>Then, create two new keys, one for the LINSTOR API server, one for all LINSTOR API clients:</p> <pre><code>openssl genrsa -out api-server.key 4096\nopenssl genrsa -out api-client.key 4096\n</code></pre> <p>Next, we will create a certificate for the server. The clients might use different shortened service names, so we need to specify multiple subject names:</p> <pre><code>cat /etc/ssl/openssl.cnf &gt; api-csr.cnf\ncat &gt;&gt; api-csr.cnf &lt;&lt;EOF\n[ v3_req ]\nsubjectAltName = @alt_names\n[ alt_names ]\nDNS.0 = linstor-controller.piraeus-datastore.svc.cluster.local\nDNS.1 = linstor-controller.piraeus-datastore.svc\nDNS.2 = linstor-controller\nEOF\nopenssl req -new -sha256 -key api-server.key -subj \"/CN=linstor-controller\" -config api-csr.cnf -extensions v3_req -out api-server.csr\nopenssl x509 -req -in api-server.csr -CA ca.crt -CAkey ca.key -CAcreateserial -config api-csr.cnf -extensions v3_req -out api-server.crt -days 3650 -sha256\n</code></pre> <p>For the client certificate, simply setting one subject name is enough:</p> <pre><code>openssl req -new -sha256 -key api-client.key -subj \"/CN=linstor-client\" -out api-client.csr\nopenssl x509 -req -in api-client.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out api-client.crt -days 3650 -sha256\n</code></pre> <p>Now, we create Kubernetes secrets from the created keys and certificates:</p> <pre><code>kubectl create secret generic linstor-api-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=api-server.crt --from-file=tls.key=api-server.key\nkubectl create secret generic linstor-client-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=api-client.crt --from-file=tls.key=api-client.key\n</code></pre> <p>Finally, configure the Operator resources to reference the newly created secrets. We configure the same client secret for all components for simplicity.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    apiSecretName: linstor-api-tls\n    clientSecretName: linstor-client-tls\n    csiControllerSecretName: linstor-client-tls\n    csiNodeSecretName: linstor-client-tls\n</code></pre>"},{"location":"how-to/api-tls/#verifying-tls-configuration","title":"Verifying TLS Configuration","text":"<p>You can verify that the secure API is running by manually connecting to the HTTPS endpoint using <code>curl</code></p> <pre><code>$ kubectl exec -n piraeus-datastore deploy/linstor-controller -- curl --key /etc/linstor/client/tls.key --cert /etc/linstor/client/tls.crt --cacert /etc/linstor/client/ca.crt https://linstor-controller.piraeus-datastore.svc:3371/v1/controller/version\n{\"version\":\"1.20.2\",\"git_hash\":\"58a983a5c2f49eb8d22c89b277272e6c4299457a\",\"build_time\":\"2022-12-14T14:21:28+00:00\",\"rest_api_version\":\"1.16.0\"}%\n</code></pre> <p>If the command is successful, the API is using HTTPS and clients are able to connect with their certificates.</p> <p>If you see an error, make sure that the client certificates are trusted by the API secret, and vice versa. The following script provides a quick way to verify that one TLS certificate is trusted by another:</p> <pre><code>function k8s_secret_trusted_by() {\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"tls.crt\" | base64decode }}' \"$1\" &gt; $1.tls.crt\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"ca.crt\" | base64decode }}' \"$2\" &gt; $2.ca.crt\n    openssl verify -CAfile $2.ca.crt $1.tls.crt\n}\nk8s_secret_trusted_by linstor-client-tls linstor-api-tls\n# Expected output:\n# linstor-client-tls.tls.crt: OK\n</code></pre> <p>Another issue might be the API endpoint using a Certificate not using the expected service name. A typical error message for this issue would be:</p> <pre><code>curl: (60) SSL: no alternative certificate subject name matches target host name 'linstor-controller.piraeus-datastore.svc'\n</code></pre> <p>In this case, make sure you have specified the right subject names when provisioning the certificates.</p> <p>All available options are documented in the reference for <code>LinstorCluster</code>.</p>"},{"location":"how-to/drbd-host-networking/","title":"How to Use the Host Network for DRBD Replication","text":"<p>This guide shows you how to use the host network for DRBD\u00ae replication.</p> <p>By default, DRBD will use the container network to replicate volume data. This ensures replication works on a wide range of clusters without further configuration. It also enables use of <code>NetworkPolicy</code> to block unauthorized access to DRBD traffic. Since the network interface of the Pod is tied to the lifecycle of the Pod, it also means DRBD will temporarily disrupt replication when the LINSTOR\u00ae Satellite Pod is restarted.</p> <p>In contrast, using the host network for DRBD replication will cause replication to work independent of the LINSTOR Satellite Pod. The host network might also offer better performance than the container network. As a downside, you will have to manually ensure connectivity between Nodes on the relevant ports.</p> <p>To follow the steps in this guide, you should be familiar with editing <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-container-network-to-host-network","title":"Switch from Container Network to Host Network","text":"<p>Switching from the default container network to host network is possible at any time. Existing DRBD resources will be reconfigured to use the host network interface.</p> <p>To configure the host network for the LINSTOR Satellite, apply the following configuration:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: host-network\nspec:\n  podTemplate:\n    spec:\n      hostNetwork: true\n</code></pre> <p>After the Satellite Pods are recreated, they will use the host network. Any existing DRBD resources are reconfigured to use the new IP Address instead.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-host-network-to-container-network","title":"Switch from Host Network to Container Network","text":"<p>Switching back from host network to container network involves manually resetting the configured peer addresses used by DRBD. This can either be achieved by rebooting every node, or by manually resetting the address using <code>drbdadm</code>.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-host-network-to-container-network-using-reboots","title":"Switch from Host Network to Container Network Using Reboots","text":"<p>First, you need to remove the <code>LinstorSatelliteConfiguration</code> that set <code>hostNetwork: true</code>:</p> <pre><code>$ kubectl delete linstorsatelliteconfigurations.piraeus.io host-network\nlinstorsatelliteconfiguration.piraeus.io \"host-network\" deleted\n</code></pre> <p>Then, reboot each cluster node, either one by one or multiple at once. In general, replication will not work between rebooted nodes and non-rebooted nodes. The non-rebooted nodes will continue to use the host network addresses, which are generally not reachable from the container network.</p> <p>After all nodes are rebooted, all resources are configured to use the container network, and all DRBD connections should be connected again.</p>"},{"location":"how-to/drbd-host-networking/#switch-from-host-network-to-container-network-using-drbdadm","title":"Switch from Host Network to Container Network Using <code>drbdadm</code>","text":"<p>During this procedure, ensure no new volumes or snapshots are created: otherwise the migration to the container network might not be applied to all resources.</p> <p>First, you need to temporarily stop all replication and suspend all DRBD volumes using <code>drbdadm suspend-io all</code>. The command is executed once on each LINSTOR Satellite Pod.</p> <pre><code>$ kubectl exec ds/linstor-satellite.node1.example.com -- drbdadm suspend-io all\n$ kubectl exec ds/linstor-satellite.node2.example.com -- drbdadm suspend-io all\n$ kubectl exec ds/linstor-satellite.node3.example.com -- drbdadm suspend-io all\n</code></pre> <p>Next, you will need to disconnect all DRBD connections on all nodes.</p> <pre><code>$ kubectl exec ds/linstor-satellite.node1.example.com -- drbdadm disconnect --force all\n$ kubectl exec ds/linstor-satellite.node2.example.com -- drbdadm disconnect --force all\n$ kubectl exec ds/linstor-satellite.node3.example.com -- drbdadm disconnect --force all\n</code></pre> <p>Now, we can safely reset all DRBD connection paths, which frees the connection to be moved to the container network.</p> <pre><code>$ kubectl exec ds/linstor-satellite.node1.example.com -- drbdadm del-path all\n$ kubectl exec ds/linstor-satellite.node2.example.com -- drbdadm del-path all\n$ kubectl exec ds/linstor-satellite.node3.example.com -- drbdadm del-path all\n</code></pre> <p>Finally, removing the <code>LinstorSatelliteConfiguration</code> that set <code>hostNetwork: true</code> will trigger the creation of new LINSTOR Satellite Pods using the container network:</p> <pre><code>$ kubectl delete linstorsatelliteconfigurations.piraeus.io host-network\nlinstorsatelliteconfiguration.piraeus.io \"host-network\" deleted\n</code></pre> <p>After the Pods are recreated and the LINSTOR Satellites are <code>Online</code>, the DRBD resource will be reconfigured and resume IO.</p>"},{"location":"how-to/drbd-loader/","title":"How to Configure the DRBD Module Loader","text":"<p>This guide shows you how to configure various aspects of the DRBD\u00ae Module Loader.</p> <p>To follow the steps in this guide, you should be familiar with editing <code>LinstorSatelliteConfiguration</code> resources.</p> <p>DRBD Module Loader is the component responsible for making the DRBD kernel module available, as well as loading other useful kernel modules for Piraeus.</p> <p>The following modules are loaded if available:</p> Module Purpose <code>libcrc32c</code> dependency for DRBD <code>nvmet_rdma</code>, <code>nvme_rdma</code> LINSTOR NVME layer <code>loop</code> LINSTOR when using loop devices as backing disks <code>dm_writecache</code> LINSTOR writecache layer <code>dm_cache</code> LINSTOR cache layer <code>dm_thin_pool</code> LINSTOR thin-provisioned storage <code>dm_snapshot</code> LINSTOR Snapshots <code>dm_crypt</code> LINSTOR encrypted volumes"},{"location":"how-to/drbd-loader/#disable-the-drbd-module-loader","title":"Disable the DRBD Module Loader","text":"<p>In some circumstances it might be necessary to disable the DRBD Module Loader entirely. For example, you are using an immutable operating system, and DRBD and other modules are loaded as part of the host configuration.</p> <p>To disable the DRBD Module Loader completely, use the following configuration:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: no-loader\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          $patch: delete\n</code></pre>"},{"location":"how-to/drbd-loader/#select-a-different-drbd-loader-version","title":"Select a Different DRBD Loader Version","text":"<p>By default, the Operator will try to find a DRBD Module Loader matching the host operating system. The host distribution is determined by inspecting the <code>.status.nodeInfo.osImage</code> field of the Kubernetes Node resource. A user-defined image can be used if the automatic mapping does not succeed or if you have different module loading requirements.</p> <p>This configuration overrides the chosen DRBD Module Loader image with a user-defined image <code>example.com/drbd-loader:v9</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: custom-drbd-module-loader-image\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          image: example.com/drbd-loader:v9\n</code></pre> <p>Piraeus maintains the following images:</p> Image Distribution <code>quay.io/piraeusdatastore/drbd9-almalinux9</code> RedHat Enterprise Linux 9 rebuilds <code>quay.io/piraeusdatastore/drbd9-almalinux8</code> RedHat Enterprise Linux 8 rebuilds <code>quay.io/piraeusdatastore/drbd9-centos7</code> RedHat Enterprise Linux 7 rebuilds <code>quay.io/piraeusdatastore/drbd9-noble</code> Ubuntu 24.04 <code>quay.io/piraeusdatastore/drbd9-jammy</code> Ubuntu 22.04 <code>quay.io/piraeusdatastore/drbd9-focal</code> Ubuntu 20.04 <code>quay.io/piraeusdatastore/drbd9-bionic</code> Ubuntu 18.04 <code>quay.io/piraeusdatastore/drbd9-bookworm</code> Debian 12 <code>quay.io/piraeusdatastore/drbd9-bullseye</code> Debian 11 <code>quay.io/piraeusdatastore/drbd9-buster</code> Debian 10 <p>You can create a loader image for your own distribution using the Piraeus sources as reference.</p>"},{"location":"how-to/drbd-loader/#change-the-way-drbd-module-loader-loads-the-drbd-module","title":"Change the Way DRBD Module Loader Loads the DRBD Module","text":"<p>By default, DRBD Module Loader will try to build the kernel module from source. The loader can also be configured to load the module from a Debian or RPM package included in the image, or skip loading DRBD entirely.</p> <p>To change the behaviour of the DRBD Loader, set the <code>LB_HOW</code> environment variable:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: no-drbd-module-loader\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          env:\n            - name: LB_HOW\n              value: deps_only\n</code></pre> <code>LB_HOW</code> Loader behaviour <code>compile</code> The default. Build the DRBD module from source and try to load all optional modules from the host. <code>shipped_modules</code> Searches for <code>.rpm</code> or <code>.deb</code> packages at  <code>/pkgs</code> and inserts contained the DRBD modules. Optional modules are loaded from the host if available. <code>deps_only</code> Only try loading the optional modules. No DRBD module will be loaded."},{"location":"how-to/drbd-tls/","title":"How to Use Transport Layer Security for DRBD Replication","text":"<p>This guide shows you how to use Transport Layer Security (TLS) for DRBD\u00ae replication.</p> <p>TLS is a protocol designed to provide security, including privacy, integrity and authentication for network communications. Starting with DRBD 9.2.6, replication traffic in DRBD can be encrypted using TLS, using the Linux kernel TLS Upper Layer Protocol.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code> resources.</li> <li>configuring TLS certificates for internal traffic.</li> </ul>"},{"location":"how-to/drbd-tls/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install Piraeus Operator &gt;= 2.3.0. The following command shows the deployed version, in this case v2.3.0:   <pre><code>$ kubectl get pods -l app.kubernetes.io/component=piraeus-operator -ojsonpath='{.items[*].spec.containers[?(@.name==\"manager\")].image}{\"\\n\"}'\nquay.io/piraeusdatastore/piraeus-operator:v2.3.0\n</code></pre></li> <li>Use a host operating system with kernel TLS offload enabled. TLS offload was added in Linux 4.19. The following   distributions are known to have TLS offload enabled:</li> <li>RHEL &gt;= 8.2</li> <li>Ubuntu &gt;= 22.04</li> <li>Debian &gt;= 12</li> <li>Have DRBD 9.2.6 or newer loaded. The following script shows the currently loaded DRBD version on all nodes:   <pre><code>for SATELLITE in $(kubectl get pods -l app.kubernetes.io/component=linstor-satellite -ojsonpath='{range .items[*]}{.metadata.name}{\"\\n\"}{end}'); do\n  echo \"$SATELLITE: $(kubectl exec $SATELLITE -- head -1 /proc/drbd)\"\ndone\n</code></pre></li> </ul>"},{"location":"how-to/drbd-tls/#configure-tls-between-linstor-controller-and-linstor-satellite","title":"Configure TLS Between LINSTOR Controller and LINSTOR Satellite","text":"<p>This step is covered in a dedicated guide. Follow the steps in the guide, but set the <code>tlsHandshakeDaemon</code> field in the <code>LinstorSatelliteConfiguration</code> resource:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: internal-tls\nspec:\n  internalTLS:\n    tlsHandshakeDaemon: true\n    # ...\n</code></pre> <p>This change will cause the Piraeus Operator to deploy an additional container named <code>ktls-utils</code> on the Satellite Pod.</p> <pre><code>$ kubectl logs -l app.kubernetes.io/component=linstor-satellite -c ktls-utils\ntlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06\ntlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06\ntlshd[1]: Built from ktls-utils 0.10 on Oct  4 2023 07:26:06\n</code></pre>"},{"location":"how-to/drbd-tls/#configure-tls-for-drbd","title":"Configure TLS for DRBD","text":"<p>To instruct LINSTOR\u00ae to configure TLS for DRBD, the <code>DrbdOptions/Net/tls</code> property needs to be set to <code>yes</code>. This can be done directly on the <code>LinstorCluster</code> resource, so it automatically applies to all resources, or as part of the parameters in a StorageClass.</p> <p>To apply the property cluster-wide, add the following property entry to your <code>LinstorCluster</code> resource:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  properties:\n    - name: DrbdOptions/Net/tls\n      value: \"yes\"\n</code></pre> <p>To apply the property only for certain StorageClasses, add the following parameter to the selected StorageClasses:</p> <pre><code>apiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: example\nprovisioner: linstor.csi.linbit.com\nparameters:\n  property.linstor.csi.linbit.com/DrbdOptions/Net/tls: \"yes\"\n  # ...\n</code></pre>"},{"location":"how-to/drbd-tls/#switch-existing-resources-to-tls","title":"Switch Existing Resources to TLS","text":"<p>DRBD does not support online reconfiguration to use DRBD. To switch existing resources to use TLS, for example by setting the property on the <code>LinstorCluster</code> resource, you need to perform the following steps on all nodes:</p> <p>First, you need to temporarily stop all replication and suspend all DRBD volumes using <code>drbdadm suspend-io all</code>. The command is executed once on each LINSTOR Satellite Pod.</p> <pre><code>$ kubectl exec node1.example.com -- drbdadm suspend-io all\n$ kubectl exec node2.example.com -- drbdadm suspend-io all\n$ kubectl exec node3.example.com -- drbdadm suspend-io all\n</code></pre> <p>Next, you will need to disconnect all DRBD connections on all nodes.</p> <pre><code>$ kubectl exec node1.example.com -- drbdadm disconnect --force all\n$ kubectl exec node2.example.com -- drbdadm disconnect --force all\n$ kubectl exec node3.example.com -- drbdadm disconnect --force all\n</code></pre> <p>Now, we can safely reconnect DRBD connection paths, which configures the TLS connection parameters.</p> <pre><code>$ kubectl exec node1.example.com -- drbdadm adjust all\n$ kubectl exec node2.example.com -- drbdadm adjust all\n$ kubectl exec node3.example.com -- drbdadm adjust all\n</code></pre>"},{"location":"how-to/drbd-tls/#confirm-drbd-uses-tls","title":"Confirm DRBD Uses TLS","text":"<p>To confirm that DRBD is using TLS for replication, check the following resources.</p> <p>First, confirm that the <code>ktls-utils</code> container performed the expected handshakes:</p> <pre><code>$ kubectl logs -l app.kubernetes.io/component=linstor-satellite -c ktls-utils\n...\nHandshake with node2.example.com (10.127.183.183) was successful\nHandshake with node2.example.com (10.127.183.183) was successful\n...\nHandshake with node3.example.com (10.125.97.42) was successful\nHandshake with node3.example.com (10.125.97.42) was successful\n...\n</code></pre> <p>[!NOTE] The following messages are expected when running <code>ktls-utils</code> in a container and can be safely ignored: <pre><code>File /etc/tlshd.d/tls.key: expected mode 600\nadd_key: Bad message\n</code></pre></p> <p>Next, check the statistics on TLS sessions controlled by the kernel on each node. You should see an equal, nonzero number of <code>TlsRxSw</code> and <code>TlsRxSw</code>.</p> <pre><code>$ kubectl exec node1.example.com -- cat /proc/net/tls_stat\nTlsCurrTxSw                         4\nTlsCurrRxSw                         4\nTlsCurrTxDevice                     0\nTlsCurrRxDevice                     0\nTlsTxSw                             4\nTlsRxSw                             4\nTlsTxDevice                         0\nTlsRxDevice                         0\nTlsDecryptError                     0\nTlsRxDeviceResync                   0\nTlsDecryptRetry                     0\nTlsRxNoPadViolation                 0\n</code></pre> <p>[!NOTE] If your network card supports TLS offloading, you might see <code>TlsTxDevice</code> and <code>TlsRxDevice</code> being nonzero instead.</p>"},{"location":"how-to/external-controller/","title":"How to Use an Existing LINSTOR Cluster","text":"<p>This guide shows you how to connect Piraeus with an existing LINSTOR\u00ae Cluster, managed outside Kubernetes.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> </ul>"},{"location":"how-to/external-controller/#configure-the-piraeus-resources","title":"Configure the Piraeus Resources","text":"<p>To use an externally managed LINSTOR Cluster, specify the URL of the LINSTOR Controller in the <code>LinstorCluster</code> resource. In the following example, the Controller is reachable at <code>http://linstor-controller.example.com:3370</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  externalController:\n    url: http://linstor-controller.example.com:3370\n</code></pre> <p>After applying the <code>LinstorCluster</code>, Piraeus will make the following changes to the default deployment:</p> <ul> <li>The <code>linstor-controller</code> Deployment is removed</li> <li>The <code>linstor-csi-controller</code> and <code>linstor-csi-node</code> resources will reference the external controller.</li> </ul>"},{"location":"how-to/external-controller/#configuring-host-networking-for-linstor-satellites","title":"Configuring Host Networking for LINSTOR Satellites","text":"<p>Normally the Pod network is not reachable from outside the Kubernetes Cluster. In this case the existing LINSTOR Controller won't be able to communicate with the Satellites in the Kubernetes cluster. So you should configure your Satellites to use host networking.</p> <p>To use host networking, apply the following configuration resource:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: host-network\nspec:\n  podTemplate:\n    spec:\n      hostNetwork: true\n</code></pre>"},{"location":"how-to/external-controller/#verifying-the-configuration","title":"Verifying the Configuration","text":"<p>To verify that the external LINSTOR Controller is configured, check:</p> <ul> <li>The <code>Available</code> condition on the <code>LinstorCluster</code> resource reports the expected Controller URL:   <pre><code>$ kubectl get LinstorCluster -ojsonpath='{.items[].status.conditions[?(@.type==\"Available\")].message}{\"\\n\"}'\nController 1.20.3 (API: 1.16.0, Git: 8d19a891df018f6e3d40538d809904f024bfe361) reachable at 'http://linstor-controller.example.com:3370'\n</code></pre></li> <li>The <code>linstor-csi-controller</code> Deployment uses the expected URL:   <pre><code>$ kubectl get -n piraeus-datastore deployment linstor-csi-controller -ojsonpath='{.spec.template.spec.containers[?(@.name==\"linstor-csi\")].env[?(@.name==\"LS_CONTROLLERS\")].value}{\"\\n\"}'\nhttp://linstor-controller.example.com:3370\n</code></pre></li> <li>The <code>linstor-csi-node</code> Deployment uses the expected URL:   <pre><code>$ kubectl get -n piraeus-datastore daemonset linstor-csi-node -ojsonpath='{.spec.template.spec.containers[?(@.name==\"linstor-csi\")].env[?(@.name==\"LS_CONTROLLERS\")].value}{\"\\n\"}'\nhttp://linstor-controller.example.com:3370\n</code></pre></li> <li>The Kubernetes nodes are registered as Satellite nodes on the LINSTOR Controller:   <pre><code>$ kubectl get nodes -owide\nNAME               STATUS   ROLES           AGE   VERSION   INTERNAL-IP      EXTERNAL-IP   OS-IMAGE                    KERNEL-VERSION                 CONTAINER-RUNTIME\nk8s-1-26-10.test   Ready    control-plane   22m   v1.26.3   192.168.122.10   &lt;none&gt;        AlmaLinux 9.1 (Lime Lynx)   5.14.0-162.22.2.el9_1.x86_64   containerd://1.6.20\n...\n$ linstor node list\n\u256d\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u2500\u256e\n\u250a Node             \u250a NodeType  \u250a Addresses                   \u250a State  \u250a\n\u255e\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2561\n\u250a k8s-1-26-10.test \u250a SATELLITE \u250a 192.168.122.10:3366 (PLAIN) \u250a Online \u250a\n...\n</code></pre></li> </ul>"},{"location":"how-to/flatcar/","title":"How to Load DRBD on Flatcar Container Linux","text":"<p>This guide shows you how to set up the DRBD\u00ae Module Loader when using Flatcar Container Linux.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> </ul>"},{"location":"how-to/flatcar/#configure-the-drbd-module-loader","title":"Configure the DRBD Module Loader","text":"<p>Flatcar Container Linux uses a read-only <code>/usr</code> file system. For building DRBD from source on Flatcar Container Linux, the default bind mount for the not existing <code>/usr/src</code> directory needs to be disabled for the <code>drbd-module-loader</code> init container.</p> <p>To change the configuration for the <code>drbd-module-loader</code> container, apply the following <code>LinstorSatelliteConfiguration</code>:</p> <pre><code>---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: no-usr-src-mount\nspec:\n  podTemplate:\n    spec:\n      volumes:\n        - name: usr-src\n          $patch: delete\n      initContainers:\n        - name: drbd-module-loader\n          volumeMounts:\n            - mountPath: /usr/src\n              name: usr-src\n              $patch: delete\n</code></pre>"},{"location":"how-to/http-proxy/","title":"How to Use Piraeus Datastore with an HTTP Proxy","text":"<p>This guide shows you how to configure the DRBD\u00ae Module Loader when using a HTTP Proxy.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li> </ul>"},{"location":"how-to/http-proxy/#configuration","title":"Configuration","text":"<p>We will use environment variables to configure the proxy, this tells the drbd-module-loader component to use the proxy for outgoing communication.</p> <p>Configure the sample below according to your environment and apply the configuration using <code>kubectl apply -f filename.yml</code>.</p> <p>This sample configuration assumes that a HTTP proxy is reacheable at <code>http://10.0.0.1:3128</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: http-proxy\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-module-loader\n          env:\n            - name: HTTP_PROXY\n              value: http://10.0.0.1:3128 # Add your proxy connection here\n            - name: HTTPS_PROXY\n              value: http://10.0.0.1:3128 # Add your proxy connection here\n            - name: NO_PROXY\n              value: localhost,127.0.0.1,10.0.0.0/8,172.16.0.0/12 # Add internal IP ranges and domains here\n</code></pre>"},{"location":"how-to/install-kernel-headers/","title":"Installing Linux Kernel Headers","text":"<p>Piraeus Datastore uses DRBD\u00ae to mirror your volume data to one or more nodes. This document aims to describe the way to install the necessary files for common Linux distributions.</p> <p>To check if your nodes already have the necessary files installed, try running:</p> <pre><code>$ test -d /lib/modules/$(uname -r)/build/ &amp;&amp; echo found headers\n</code></pre> <p>If the command prints <code>found headers</code>, your nodes are good to go.</p>"},{"location":"how-to/install-kernel-headers/#installing-on-ubuntu","title":"Installing on Ubuntu","text":"<p>Installation of Linux Kernel headers on Ubuntu can be done through the <code>apt</code> package manager:</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-$(uname -r)\n</code></pre> <p>In addition, you can install the <code>linux-headers-virtual</code> package. This causes <code>apt upgrade</code> to install the headers matching any newly installed kernel versions.</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-virtual\n</code></pre>"},{"location":"how-to/install-kernel-headers/#installing-on-debian","title":"Installing on Debian","text":"<p>Installation of Linux Kernel headers on Debian can be done through the <code>apt</code> package manager:</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-$(uname -r)\n</code></pre> <p>In addition, you can install an additional package, that causes <code>apt</code> to also install Kernel headers on upgrade:</p> <pre><code>$ sudo apt-get update\n$ sudo apt-get install -y linux-headers-$(dpkg --print-architecture)\n</code></pre>"},{"location":"how-to/install-kernel-headers/#installing-on-redhat-enterprise-linux","title":"Installing on RedHat Enterprise Linux","text":"<p>Installing on RedHat Enterprise Linux or compatible distributions, such as AlmaLinux or Rocky Linux can be done through the <code>dnf</code> package manager:</p> <pre><code>$ sudo dnf install -y kernel-devel-$(uname -r)\n</code></pre> <p>In addition, you can install an additional package, that causes <code>yum</code> to also install Kernel headers on upgrade:</p> <pre><code>$ sudo dnf install -y kernel-devel\n</code></pre>"},{"location":"how-to/internal-tls/","title":"How to Configure TLS Between LINSTOR Controller and LINSTOR Satellite","text":"<p>This guide shows you how to set up TLS between LINSTOR\u00ae Controller and LINSTOR Satellite.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the LINSTOR client to verify success.</li> <li>using either cert-manager or <code>openssl</code> to create TLS certificates.</li> </ul>"},{"location":"how-to/internal-tls/#provision-keys-and-certificates-using-cert-manager","title":"Provision Keys and Certificates Using cert-manager","text":"<p>This method requires a working cert-manager deployment in your cluster. For an alternative way to provision keys and certificates, see the <code>openssl</code> section below.</p> <p>LINSTOR Controller and Satellite only need to trust each other, so it is good practice to have a CA only for those components. Apply the following YAML to create a new Issuer:</p> <pre><code>---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: ca-bootstrapper\n  namespace: piraeus-datastore\nspec:\n  selfSigned: { }\n---\napiVersion: cert-manager.io/v1\nkind: Certificate\nmetadata:\n  name: linstor-internal-ca\n  namespace: piraeus-datastore\nspec:\n  commonName: linstor-internal-ca\n  secretName: linstor-internal-ca\n  duration: 87600h # 10 years\n  isCA: true\n  usages:\n    - signing\n    - key encipherment\n    - cert sign\n  issuerRef:\n    name: ca-bootstrapper\n    kind: Issuer\n---\napiVersion: cert-manager.io/v1\nkind: Issuer\nmetadata:\n  name: linstor-internal-ca\n  namespace: piraeus-datastore\nspec:\n  ca:\n    secretName: linstor-internal-ca\n</code></pre> <p>Then, configure this new issuer to let the Operator provision the needed certificates:</p> <pre><code>---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    certManager:\n      name: linstor-internal-ca\n      kind: Issuer\n---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: internal-tls\nspec:\n  internalTLS:\n    certManager:\n      name: linstor-internal-ca\n      kind: Issuer\n</code></pre> <p>This completes the necessary steps for secure TLS connections between LINSTOR Controller and Satellite using cert-manager. Skip to the last section to verify TLS is working.</p>"},{"location":"how-to/internal-tls/#provision-keys-and-certificates-using-openssl","title":"Provision Keys and Certificates Using <code>openssl</code>","text":"<p>If you completed the cert-manager section above, skip directly to the verifying the configuration below.</p> <p>This method requires the <code>openssl</code> program on the command line. For an alternative way to provision keys and certificates, see the cert-manager section above.</p> <p>First, create a new Certificate Authority using a new key and a self-signed certificate, valid for 10 years:</p> <pre><code>openssl req -new -newkey rsa:4096 -days 3650 -nodes -x509 -keyout ca.key -out ca.crt -subj \"/CN=linstor-internal-ca\"\n</code></pre> <p>Then, create two new keys, one for the LINSTOR Controller, one for all Satellites:</p> <pre><code>openssl genrsa -out controller.key 4096\nopenssl genrsa -out satellite.key 4096\n</code></pre> <p>Next, we will create a certificate for each key, valid for 10 years, signed by the Certificate Authority:</p> <pre><code>openssl req -new -sha256 -key controller.key -subj \"/CN=linstor-controller\" -out controller.csr\nopenssl req -new -sha256 -key satellite.key -subj \"/CN=linstor-satellite\" -out satellite.csr\nopenssl x509 -req -in controller.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out controller.crt -days 3650 -sha256\nopenssl x509 -req -in satellite.csr -CA ca.crt -CAkey ca.key -CAcreateserial -out satellite.crt -days 3650 -sha256\n</code></pre> <p>Now, we create Kubernetes secrets from the created keys and certificates:</p> <pre><code>kubectl create secret generic linstor-controller-internal-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=controller.crt --from-file=tls.key=controller.key\nkubectl create secret generic linstor-satellite-internal-tls -n piraeus-datastore --type=kubernetes.io/tls --from-file=ca.crt=ca.crt --from-file=tls.crt=satellite.crt --from-file=tls.key=satellite.key\n</code></pre> <p>Finally, configure the Operator resources to reference the newly created secrets:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    secretName: linstor-controller-internal-tls\n---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: internal-tls\nspec:\n  internalTLS:\n    secretName: linstor-satellite-internal-tls\n</code></pre>"},{"location":"how-to/internal-tls/#verifying-tls-configuration","title":"Verifying TLS Configuration","text":"<p>You can verify the secure TLS connection between LINSTOR Controller and Satellite by checking the output of the <code>linstor node list</code> command. If TLS is enabled, you will see <code>(SSL)</code> next to the active satellite address:</p> <pre><code>$ kubectl exec -n piraeus-datastore deploy/linstor-controller -- linstor node list\n+---------------------------------------------------------------------+\n| Node               | NodeType  | Addresses                 | State  |\n|=====================================================================|\n| node01.example.com | SATELLITE | 10.116.72.142:3367 (SSL)  | Online |\n| node02.example.com | SATELLITE | 10.127.183.140:3367 (SSL) | Online |\n| node03.example.com | SATELLITE | 10.125.97.50:3367 (SSL)   | Online |\n+---------------------------------------------------------------------+\n</code></pre> <p>If you see <code>(PLAIN)</code> instead, this indicates that the TLS configuration was not applied successfully. Check the status of the <code>LinstorCluster</code> and <code>LinstorSatellite</code> resource.</p> <p>If you see <code>(SSL)</code>, but the node remains offline, this usually indicates that a certificate is not trusted by the other party. Verify that the Controller's <code>tls.crt</code> is trusted by the Satellite's <code>ca.crt</code> and vice versa. The following script provides a quick way to verify that one TLS certificate is trusted by another:</p> <pre><code>function k8s_secret_trusted_by() {\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"tls.crt\" | base64decode }}' \"$1\" &gt; $1.tls.crt\n    kubectl get secret -n piraeus-datastore -ogo-template='{{ index .data \"ca.crt\" | base64decode }}' \"$2\" &gt; $2.ca.crt\n    openssl verify -CAfile $2.ca.crt $1.tls.crt\n}\nk8s_secret_trusted_by satellite-tls controller-tls\n# Expected output:\n# satellite-tls.tls.crt: OK\n</code></pre> <p>All available options are documented in the reference for <code>LinstorCluster</code> and <code>LinstorSatelliteConfiguration</code>.</p>"},{"location":"how-to/k0s/","title":"How to Configure Piraeus Datastore on k0s","text":"<p>This guide shows you how to configure Piraeus Datastore when using k0s.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> </ul>"},{"location":"how-to/k0s/#configure-the-csi-driver","title":"Configure the CSI Driver","text":"<p>Because k0s store their state in a separate directory (<code>/var/lib/k0s</code>) the LINSTOR CSI Driver needs to be updated to use a new path for mounting volumes.</p> <p>To change the LINSTOR CSI Driver, so that it uses the k0s state paths, apply the following <code>LinstorCluster</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  csiNode:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-csi\n            volumeMounts:\n            - mountPath: /var/lib/k0s/kubelet\n              name: publish-dir\n              mountPropagation: Bidirectional\n          - name: csi-node-driver-registrar\n            args:\n            - --v=5\n            - --csi-address=/csi/csi.sock\n            - --kubelet-registration-path=/var/lib/k0s/kubelet/plugins/linstor.csi.linbit.com/csi.sock\n            - --health-port=9809\n        volumes:\n         - name: publish-dir\n           hostPath:\n             path: /var/lib/k0s/kubelet\n         - name: registration-dir\n           hostPath:\n             path: /var/lib/k0s/kubelet/plugins_registry\n         - name: plugin-dir\n           hostPath:\n              path: /var/lib/k0s/kubelet/plugins/linstor.csi.linbit.com\n</code></pre>"},{"location":"how-to/linstor-affinity-controller/","title":"How to Deploy the LINSTOR Affinity Controller","text":"<p>This guide shows you how to deploy the LINSTOR Affinity Controller for Piraeus Datastore.</p> <p>The LINSTOR Affinity Controller keeps the affinity of your volumes in sync between Kubernetes and LINSTOR.</p> <p>When using a strict volume affinity setting, such as <code>allowRemoteVolumeAccess: false</code>, the Persistent Volume (PV) resource created by Piraeus Datastore will have a fixed affinity. When the volume is moved to a different node, for example because one of the existing replicas is being evacuated, the PV is not updated automatically.</p> <p>The LINSTOR Affinity controller watches PVs and LINSTOR resource and keeps the affinity up-to-date.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>Deploying workloads in Kubernetes using <code>helm</code></li> </ul>"},{"location":"how-to/linstor-affinity-controller/#add-the-piraeus-datastore-chart-repository","title":"Add the Piraeus Datastore Chart Repository","text":"<p>Piraeus Datastore maintains a helm chart repository for commonly deployed components, including the LINSTOR Affinity Controller. To add the repository to your helm configuration, run:</p> <pre><code>$ helm repo add piraeus-charts https://piraeus.io/helm-charts/\n</code></pre>"},{"location":"how-to/linstor-affinity-controller/#deploy-the-linstor-affinity-controller","title":"Deploy the LINSTOR Affinity Controller","text":"<p>After adding the repository, deploy the LINSTOR Affinity Controller:</p> <pre><code>$ helm install linstor-affinity-controller piraeus-charts/linstor-affinity-controller\nNAME: linstor-affinity-controller\nLAST DEPLOYED: Mon Dec  4 09:14:07 2023\nNAMESPACE: piraeus-datastore\nSTATUS: deployed\nREVISION: 1\nTEST SUITE: None\nNOTES:\nLINSTOR Affinity Controller deployed.\n\nUsed LINSTOR URL: http://linstor-controller.piraeus-datastore.svc:3370\n</code></pre> <p>If you deploy the LINSTOR Affinity Controller to the same namespace as the Piraeus Operator, the deployment will automatically determine the necessary parameters for connecting to LINSTOR.</p> <p>In some cases, helm may not be able to determine the connection parameters. In this case, you need to manually provide the following values:</p> <pre><code>linstor:\n  # The URL of the LINSTOR Controller API. This example contains the default value.\n  endpoint: http://linstor-controller.piraeus-datastore.svc:3370\n  # This is the default URL when using TLS for securing the API\n  #endpoint: https://linstor-controller.piraeus-datastore.svc:3371\n  # This is the name of the secret containing TLS key and certificates for connecting to the LINSTOR API with TLS.\n  clientSecret: \"\"\noptions:\n  # This is the namespace used by Piraeus Operator to sync Kubernetes Node labels with LINSTOR node properties.\n  # For Piraeus Operator, this needs to be set to the following value:\n  propertyNamespace: Aux/topology\n</code></pre>"},{"location":"how-to/microk8s/","title":"How to Configure Piraeus Datastore on MicroK8s","text":"<p>This guide shows you how to configure Piraeus Datastore when using MicroK8s.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorCluster</code> resources.</li> </ul>"},{"location":"how-to/microk8s/#configure-the-csi-driver","title":"Configure the CSI Driver","text":"<p>MicroK8s is distributed as a Snap. Because Snaps store their state in a separate directory (<code>/var/snap</code>) the LINSTOR CSI Driver needs to be updated to use a new path for mounting volumes.</p> <p>To change the LINSTOR CSI Driver, so that it uses the MicroK8s state paths, apply the following <code>LinstorCluster</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  patches:\n    - target:\n        name: linstor-csi-node\n        kind: DaemonSet\n      patch: |\n        apiVersion: apps/v1\n        kind: DaemonSet\n        metadata:\n          name: linstor-csi-node\n        spec:\n          template:\n            spec:\n              containers:\n              - name: linstor-csi\n                volumeMounts:\n                - mountPath: /var/lib/kubelet\n                  name: publish-dir\n                  $patch: delete\n                - mountPath: /var/snap/microk8s/common/var/lib/kubelet\n                  name: publish-dir\n                  mountPropagation: Bidirectional\n</code></pre>"},{"location":"how-to/monitoring/","title":"How to Deploy Monitoring with Prometheus Operator","text":"<p>Piraeus Datastore offers integration with the Prometheus monitoring stack.</p> <p>The integration configures:</p> <ul> <li>Metrics scraping for the LINSTOR and DRBD state.</li> <li>Alerts based on the cluster state</li> <li>A Grafana dashboard</li> </ul> <p>To complete this guide, you should be familiar with:</p> <ul> <li>Deploying workloads in Kubernetes using <code>helm</code></li> <li>Deploying resources using <code>kubectl</code></li> </ul>"},{"location":"how-to/monitoring/#deploying-prometheus-operator","title":"Deploying Prometheus Operator","text":"<p>\ud83d\uddd2\ufe0f NOTE: If you already have a working Prometheus Operator deployment, skip this step.</p> <p>First deploy the Prometheus Operator. A simple way to deploy it, is to use the helm chart provided by the Prometheus Community.</p> <p>First, add the helm chart repository to your local helm configuration:</p> <pre><code>$ helm repo add prometheus-community https://prometheus-community.github.io/helm-charts\n</code></pre> <p>Then, deploy the <code>kube-prometheus-stack</code> chart. This chart will set up Prometheus, AlertManager and Grafana for your cluster. Configure it to search for monitoring and alerting rules in all namespaces:</p> <pre><code>$ helm install --create-namespace -n monitoring prometheus prometheus-community/kube-prometheus-stack \\\n  --set prometheus.prometheusSpec.serviceMonitorSelectorNilUsesHelmValues=false \\\n  --set prometheus.prometheusSpec.podMonitorSelectorNilUsesHelmValues=false \\\n  --set prometheus.prometheusSpec.ruleSelectorNilUsesHelmValues=false\n</code></pre> <p>\ud83d\uddd2\ufe0f NOTE: By default, the deployment will only monitor resources in the <code>kube-system</code> and its own namespace. Piraeus Datastore is usually deployed in a different namespace, so Prometheus needs to be configured to watch this namespace. In the example above, this is achieved by setting the various <code>*NilUsesHelmValues</code> parameters to <code>false</code>.</p>"},{"location":"how-to/monitoring/#deploying-monitoring-and-alerting-rules-for-piraeus-datastore","title":"Deploying Monitoring and Alerting Rules for Piraeus Datastore","text":"<p>After creating a Prometheus Operator deployment and configuring it to watch all namespaces, apply the monitoring and alerting resources for Piraeus Datastore:</p> <pre><code>$ kubectl apply --server-side -n piraeus-datastore -k \"https://github.com/piraeusdatastore/piraeus-operator//config/extras/monitoring?ref=v2\"\n</code></pre>"},{"location":"how-to/monitoring/#verify-monitoring","title":"Verify Monitoring","text":"<p>Verify that the monitoring configuration is working by checking the prometheus console. First, get access to the prometheus console from your local browser by forwarding it to local port 9090:</p> <pre><code>$ kubectl port-forward -n monitoring services/prometheus-kube-prometheus-prometheus 9090:9090\n</code></pre> <p>Now, open http://localhost:9090/graph and display the <code>linstor_info</code> and <code>drbd_version</code> metrics:</p> <p> </p> <p>To view the dashboard, forward the grafana service to local port 3000:</p> <pre><code>$ kubectl port-forward -n monitoring services/prometheus-grafana 3000:http-web\n</code></pre> <p>Now, open http://localhost:3000 and log in. If using the example deployment from above, use username <code>admin</code> and password <code>prom-operator</code> to gain access. Then, select \"Piraeus Datastore\" from the available dashboards:</p> <p></p>"},{"location":"how-to/network-policy/","title":"How to Deploy a NetworkPolicy for Piraeus Datastore","text":"<p>Network Policies offer a way to restrict network access of specific pods. They can be used to block undesired network connections to specific Pods.</p> <p>Piraeus Datastore provides basic Network Policies that configure restricted access to the LINSTOR Satellites. The provided policy restricts incoming network connections to LINSTOR Satellite to only the following sources:</p> <ul> <li>Other LINSTOR Satellite Pods to allow for DRBD replication</li> <li>The LINSTOR Controller Pod, to facilitate LINSTOR Cluster operations</li> <li>Metrics collection from DRBD Reactor.</li> </ul> <p>To deploy the Network Policy, apply the following remote resource:</p> <pre><code>$ kubectl apply --server-side -k \"https://github.com/piraeusdatastore/piraeus-operator//config/extras/network-policy?ref=v2\"\nnetworkpolicy.networking.k8s.io/satellite serverside-applied\n</code></pre>"},{"location":"how-to/openshift/","title":"How to Load DRBD on OpenShift","text":"<p>This guide shows you how to set the DRBD\u00ae Module Loader when using OpenShift.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the <code>oc</code> command line tool to access the OpenShift cluster.</li> </ul>"},{"location":"how-to/openshift/#find-the-driver-toolkit-image","title":"Find the Driver Toolkit Image","text":"<p>The Driver Toolkit image contains the necessary files for building DRBD. Every OpenShift release includes a version of the Driver Toolkit image matching the operating system version of the release. You can use <code>oc</code> to print the correct image version:</p> <pre><code>$ oc adm release info --image-for=driver-toolkit\nquay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709\n</code></pre>"},{"location":"how-to/openshift/#configure-the-drbd-module-loader","title":"Configure the DRBD Module Loader","text":"<p>By default, the DRBD Module Loader will try to find the necessary header files to build DRBD from source on the host system. In OpenShift, these header files are not included in the host system. Instead, they are included in the Driver Toolkit image.</p> <p>To change the DRBD Module Loader, so that it uses the header files included in the Driver Toolkit image, apply the following <code>LinstorSatelliteConfiguration</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: openshift-loader-override\nspec:\n  podTemplate:\n    spec:\n      volumes:\n        - name: usr-src\n          emptyDir: { }\n          hostPath:\n            $patch: delete\n      initContainers:\n        - name: kernel-header-copy\n          image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709\n          args:\n            - cp\n            - -avt\n            - /container/usr/src\n            - /usr/src/kernels\n          volumeMounts:\n            - name: usr-src\n              mountPath: /container/usr/src\n          securityContext:\n            privileged: true\n        - name: drbd-module-loader\n          securityContext:\n            privileged: true\n</code></pre> <p>NOTE: Replace the <code>image</code> of the <code>kernel-header-copy</code> container with the image returned by <code>oc adm release info</code>.</p> <p>After the automatic restart of the LINSTOR\u00ae Satellite Pods, DRBD will be built from source, using the correct header files.</p>"},{"location":"how-to/openshift/#openshift-update-considerations","title":"OpenShift Update Considerations","text":"<p>OpenShift updates also update the host operating system. Since every node will be rebooted during the update, the DRBD Module loader needs to rebuild DRBD once after the restart for the new host operating system.</p> <p>To ensure that the DRBD rebuild is successful, you need to update the image in the <code>openshift-loader-override</code> configuration before starting the upgrade process. You can extract the Driver Toolkit image for the new OpenShift version before starting the upgrade like this:</p> <pre><code>$ oc adm release info 4.12.2 --image-for=driver-toolkit\nquay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1328c4e7944b6d8eda40a8f789471a1aec63abda75ac1199ce098b965ec16709\n</code></pre>"},{"location":"how-to/restore-linstor-db/","title":"How to Restore a LINSTOR Database Backup","text":"<p>This guide shows you how to restore a LINSTOR\u00ae Controller from a database backup. A backup is created automatically on every database migration of the default <code>k8s</code> database.</p> <p>[!CAUTION] Restoring from a backup means all changes made to the Cluster state after the backup was taken are lost. This includes information about Persistent Volumes and Volume Snapshots that where created after the backup.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li> </ul>"},{"location":"how-to/restore-linstor-db/#find-the-latest-backup","title":"Find the Latest Backup","text":"<p>The backup is stored in Kubernetes Secrets. List all backups by using the following command:</p> <pre><code>$ kubectl get secrets --field-selector type=piraeus.io/linstor-backup --sort-by .metadata.creationTimestamp -ocustom-columns=\"NAME:.metadata.name,CREATED-AT:metadata.creationTimestamp,VERSION:.metadata.annotations.piraeus\\.io/linstor-version\"\nNAME                                                     CREATED-AT             VERSION\nlinstor-backup-for-linstor-controller-db7fbfd95-zsfmm    2024-11-04T07:54:29Z   LINSTOR Controller 1.27.0\nlinstor-backup-for-linstor-controller-745d54bf99-544hf   2024-11-04T08:03:59Z   LINSTOR Controller 1.29.1\n</code></pre> <p>Select the backup you want to restore, making note of the name. For example, to restore the LINSTOR 1.27.0 version, we set:</p> <pre><code>$ BACKUP_NAME=linstor-backup-for-linstor-controller-db7fbfd95-zsfmm\n</code></pre>"},{"location":"how-to/restore-linstor-db/#temporarily-stop-the-linstor-controller-deployment","title":"Temporarily stop the LINSTOR Controller Deployment","text":"<p>To safely restore the database, ensure that the LINSTOR Controller is shut down by scaling the Piraeus Operator and LINSTOR Controller deployment to 0 replicas:</p> <pre><code>$ kubectl scale deployment piraeus-operator-controller-manager --replicas 0\ndeployment.apps/piraeus-operator-controller-manager scaled\n$ kubectl scale deployment linstor-controller --replicas 0\ndeployment.apps/linstor-controller scaled\n</code></pre>"},{"location":"how-to/restore-linstor-db/#create-a-new-backup-of-the-current-cluster-state","title":"Create a New Backup of the Current Cluster State","text":"<p>Since the restore process is destructive, first create a backup of the current database:</p> <pre><code>$ mkdir backup\n$ cd backup\n$ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty kubectl get crds -oyaml &gt; crds.yaml\n$ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty -I {} sh -c 'kubectl get {} -oyaml &gt; {}.yaml'\n</code></pre>"},{"location":"how-to/restore-linstor-db/#restore-the-database","title":"Restore the Database","text":"<p>Copy and unpack the selected backup to a local directory by using the following commands:</p> <pre><code>$ mkdir restore\n$ cd restore\n# Replace $BACKUP_NAME with your selected backup name\n$ kubectl get secrets --sort-by=.metadata.name -l piraeus.io/backup=$BACKUP_NAME -ogo-template='{{range .items}}{{index .data \"backup.tar.gz\" | base64decode}}{{end}}' &gt; backup.tar.gz\n$ tar -xvf backup.tar.gz\ncrds.yaml\n[...]\n</code></pre> <p>Then, replace the current database with the database from the backup:</p> <pre><code>$ kubectl api-resources --api-group=internal.linstor.linbit.com -oname | xargs --no-run-if-empty kubectl delete crds\n$ kubectl create -f .\n</code></pre>"},{"location":"how-to/restore-linstor-db/#restart-the-linstor-controller-deployment","title":"Restart the LINSTOR Controller Deployment","text":"<p>Now we can safely restart the Piraeus Operator and LINSTOR Controller Deployment.</p> <pre><code>$ kubectl scale deployment piraeus-operator-controller-manager --replicas 1\ndeployment.apps/piraeus-operator-controller-manager scaled\n$ kubectl scale deployment linstor-controller --replicas 1\ndeployment.apps/linstor-controller scaled\n$ kubectl rollout status deployment piraeus-operator-controller-manager\nWaiting for deployment \"piraeus-operator-controller-manager\" rollout to finish: 0 of 1 updated replicas are available...\ndeployment \"piraeus-operator-controller-manager\" successfully rolled out\n$ kubectl rollout status deployment linstor-controller\nWaiting for deployment \"linstor-controller\" rollout to finish: 0 of 1 updated replicas are available...\ndeployment \"linstor-controller\" successfully rolled out\n</code></pre>"},{"location":"how-to/secure-boot/","title":"How to Load DRBD with SecureBoot Enabled","text":"<p>This guide shows you how to use the DRBD\u00ae Module Loader on machines with SecureBoot enabled.</p> <p>When SecureBoot is enabled the Linux Kernel refuses to load unsigned kernel modules. Since the DRBD modules are built from source, they do not have a valid signature by default. To load them, they need to be signed, and the signing key needs to be inserted into the machine's trust store.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>generating key material with <code>openssl</code>.</li> <li>managing machine owner keys with <code>mokutil</code>.</li> <li>creating and protecting Kubernetes Secret resources.</li> </ul>"},{"location":"how-to/secure-boot/#prerequisites","title":"Prerequisites","text":"<ul> <li>A Kubernetes node running with SecureBoot enabled. This can be checked by running the following command on each node:   <pre><code># mokutil --sb-state\nSecureBoot enabled\n</code></pre></li> <li>Console access to the machine during early boot, or permissions to update the EFI platform keys another way.</li> </ul>"},{"location":"how-to/secure-boot/#generate-key-material","title":"Generate Key Material","text":"<p>Create a private key and self-signed certificate using the <code>openssl</code> command line utility. The following command will create a new private key named <code>signing_key.pem</code> and a certificate named <code>signing_key.x509</code>, valid for 10 years, in the appropriate format:</p> <pre><code>$ openssl req -x509 -new -nodes -utf8 -sha256 -days 36500 -batch -outform DER \\\n    -out signing_key.x509 -keyout signing_key.pem -config - &lt;&lt;EOF\n[ req ]\ndefault_bits = 4096\ndistinguished_name = req_distinguished_name\nprompt = no\nstring_mask = utf8only\nx509_extensions = myexts\n\n[ req_distinguished_name ]\nO = Piraeus Datastore\nCN = Piraeus Datastore kernel module signing key\nemailAddress = piraeus-signing-key@example.com\n\n[ myexts ]\nbasicConstraints=critical,CA:FALSE\nkeyUsage=digitalSignature\nsubjectKeyIdentifier=hash\nauthorityKeyIdentifier=keyid\nEOF\n</code></pre>"},{"location":"how-to/secure-boot/#enroll-the-certificate-in-the-machine-trust-store","title":"Enroll the Certificate in the Machine Trust Store","text":"<p>The generated certificate needs to be added to the machine's trust store. This step depends on the machine platform you are using. The instructions here apply to any system where you have console access during early boot, such as bare-metal or most virtualization platforms.</p> <p>First, distribute the generated certificate <code>signing_key.x509</code> to all nodes. Then, use the following command to add the certificate to the machine owner keys (MOK) using a password of your choice:</p> <pre><code># mokutil --import signing_key.x509\ninput password:\ninput password again:\n</code></pre> <p>To enable the keys, start a console session on the machine, either by directly attching a keyboard and monitor, attaching a virtual console using the machines BMC, or using tools of your virtualization platform such as virt-viewer or VNC.</p> <p>Then, reboot the machine, chosing to \"Perform MOK management\" when promted. Now: * Select \"Enroll MOK\":</p> <p> * Continue enrollment of the key:</p> <p> * Enter the password chosen when running <code>mokutil --import</code>:</p> <p> * Reboot the machine:</p> <p></p>"},{"location":"how-to/secure-boot/#sign-the-drbd-module-using-the-created-key-material","title":"Sign the DRBD Module Using the Created Key Material","text":"<p>Create a Kubernetes Secret resource containing the generated key material. The following command creates a secret named <code>drbd-signing-keys</code>:</p> <pre><code>$ kubectl create secret generic drbd-signing-keys --type piraeus.io/signing-key \\\n    --from-file=signing_key.pem --from-file=signing_key.x509\nsecret/drbd-signing-keys created\n</code></pre> <p>Now, configure the <code>drbd-module-loader</code> to use the key material to sign the kernel modules. The following <code>LinstorSatelliteConfiguration</code> resource makes the key available in the <code>drbd-module-loader</code> container available and sets the <code>LB_SIGN</code> environment variable to start signing the modules:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: drbd-module-signing\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n      - name: drbd-module-loader\n        env:\n        - name: LB_SIGN\n          value: /signing-key\n        volumeMounts:\n        - name: signing-key\n          mountPath: /signing-key\n          readOnly: true\n      volumes:\n      - name: signing-key\n        secret:\n          secretName: drbd-signing-keys\n</code></pre>"},{"location":"how-to/secure-boot/#verifying-success","title":"Verifying Success","text":"<p>When everything is configured correctly, the <code>drbd-module-loader</code> init container will be able to insert the DRBD modules.</p> <pre><code>$ kubectl logs ds/linstor-satellite.node1.example.com drbd-module-loader\n...\nDRBD version loaded:\nversion: 9.2.8 (api:2/proto:86-122)\nGIT-hash: e163b05a76254c0f51f999970e861d72bb16409a build by @linstor-satellite.k8s-21.test-zskzl, 2024-04-03 09:04:15\nTransports (api:20): tcp (9.2.8) lb-tcp (9.2.8) rdma (9.2.8)\n</code></pre> <p>If the modules are not signed, or the signature is not trusted, the <code>drbd-module-loader</code> container will crash with one of the following error messages:</p> <pre><code>insmod: ERROR: could not insert module ./drbd.ko: Operation not permitted\ninsmod: ERROR: could not insert module ./drbd_transport_tcp.ko: Operation not permitted\ninsmod: ERROR: could not insert module ./drbd_transport_lb-tcp.ko: Operation not permitted\n\nCould not load DRBD kernel modules\n</code></pre> <pre><code>insmod: ERROR: could not insert module ./drbd.ko: Key was rejected by service\ninsmod: ERROR: could not insert module ./drbd_transport_tcp.ko: Key was rejected by service\ninsmod: ERROR: could not insert module ./drbd_transport_lb-tcp.ko: Key was rejected by service\n\nCould not load DRBD kernel modules\n</code></pre> <pre><code>insmod: ERROR: could not insert module ./drbd.ko: Required key not available\ninsmod: ERROR: could not insert module ./drbd_transport_tcp.ko: Required key not available\ninsmod: ERROR: could not insert module ./drbd_transport_lb-tcp.ko: Required key not available\n\nCould not load DRBD kernel modules\n</code></pre> <p>Additional information is available in the kernel logs:</p> <pre><code>$ dmesg\n...\n# The module is not signed. Check that the LB_SIGN environment variable is set in the container.\nLockdown: insmod: unsigned module loading is restricted; see man kernel_lockdown.7\n# The module is signed, but the signing key is not in the machine's trust store.\n# Check the enrolled keys using \"mokutil --list-enrolled\".\nPKCS#7 signature not signed with a trusted key\n</code></pre>"},{"location":"how-to/talos/","title":"How to Load DRBD on Talos Linux","text":"<p>This guide shows you how to set the DRBD\u00ae Module Loader when using Talos Linux.</p> <p>To complete this guide, you should be familiar with:</p> <ul> <li>editing <code>LinstorSatelliteConfiguration</code> resources.</li> <li>using the <code>talosctl</code> command line to to access Talos Linux nodes.</li> <li>using the <code>kubectl</code> command line tool to access the Kubernetes cluster.</li> </ul>"},{"location":"how-to/talos/#configure-talos-system-extension-for-drbd","title":"Configure Talos system extension for DRBD","text":"<p>By default, the DRBD Module Loader will try to find the necessary header files to build DRBD from source on the host system. In Talos Linux these header files are not included in the host system. Instead, the Kernel modules is packed into a system extension.</p> <p>Ensure Talos has the correct <code>drbd</code> system extension loaded for the running Kernel.</p> <p>This is done by building a install image from the talos factory with drbd included</p> <p>You will also need to update the machine config to set the following kernel module parameters:</p> <pre><code>machine:\n  kernel:\n    modules:\n      - name: drbd\n        parameters:\n          - usermode_helper=disabled\n      - name: drbd_transport_tcp\n</code></pre> <p>Validate <code>drbd</code> module is loaded: <pre><code>$ talosctl -n &lt;NODE_IP&gt; read /proc/modules\ndrbd_transport_tcp 28672 - - Live 0xffffffffc046c000 (O)\ndrbd 643072 - - Live 0xffffffffc03b9000 (O)\n</code></pre></p> <p>Validate <code>drbd</code> module parameter <code>usermode_helper</code> is set to <code>disabled</code>: <pre><code>$ talosctl -n &lt;NODE_IP&gt; read /sys/module/drbd/parameters/usermode_helper\ndisabled\n</code></pre></p>"},{"location":"how-to/talos/#configure-the-drbd-module-loader","title":"Configure the DRBD Module Loader","text":"<p>To change the DRBD Module Loader, so that it uses the modules provided by system extension, apply the following <code>LinstorSatelliteConfiguration</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: talos-loader-override\nspec:\n  podTemplate:\n    spec:\n      initContainers:\n        - name: drbd-shutdown-guard\n          $patch: delete\n        - name: drbd-module-loader\n          $patch: delete\n      volumes:\n        - name: run-systemd-system\n          $patch: delete\n        - name: run-drbd-shutdown-guard\n          $patch: delete\n        - name: systemd-bus-socket\n          $patch: delete\n        - name: lib-modules\n          $patch: delete\n        - name: usr-src\n          $patch: delete\n        - name: etc-lvm-backup\n          hostPath:\n            path: /var/etc/lvm/backup\n            type: DirectoryOrCreate\n        - name: etc-lvm-archive\n          hostPath:\n            path: /var/etc/lvm/archive\n            type: DirectoryOrCreate\n</code></pre> <p>Explanation:</p> <ul> <li><code>/etc/lvm/*</code> is read-only in Talos and therefore can't be used. Let's use <code>/var/etc/lvm/*</code> instead.</li> <li>Talos does not ship with Systemd, so everything Systemd related needs to be removed</li> <li><code>/usr/lib/modules</code> and <code>/usr/src</code> are not needed as the Kernel module is already compiled and needs just to be used.</li> </ul>"},{"location":"reference/","title":"API Reference","text":"<p>This is the API Reference for Piraeus Operator. A user may make modifications to these resources to change the cluster state (<code>LinstorCluster</code> or <code>LinstorSatelliteConfiguration</code>) or check the status of a resource (<code>LinstorSatellite</code>).</p> <ul> <li> <p>LinstorCluster</p> <p>This resource controls the state of the LINSTOR\u00ae cluster and integration with Kubernetes.</p> <p> Reference</p> </li> <li> <p>LinstorSatelliteConfiguration</p> <p>This resource controls the state of the LINSTOR Satellites, optionally applying it to only a subset of nodes.</p> <p> Reference</p> </li> <li> <p>LinstorNodeConnection</p> <p>This resource controls the state of the LINSTOR\u00ae node connections.</p> <p> Reference</p> </li> <li> <p>LinstorSatellite</p> <p>This resource controls the state of a single LINSTOR Satellite. This resource is not intended to be changed directly, instead it is created by the Piraeus Operator by merging all matching <code>LinstorSatelliteConfiguration</code> resources.</p> <p> Reference</p> </li> </ul>"},{"location":"reference/linstorcluster/","title":"<code>LinstorCluster</code>","text":"<p>This resource controls the state of the LINSTOR\u00ae cluster and integration with Kubernetes. In particular, it controls:</p> <ul> <li>LINSTOR Controller</li> <li>LINSTOR CSI Driver</li> <li><code>LinstorSatellite</code>, configured through <code>LinstorSatelliteConfiguration</code> resources.</li> </ul>"},{"location":"reference/linstorcluster/#spec","title":"<code>.spec</code>","text":"<p>Configures the desired state of the cluster.</p>"},{"location":"reference/linstorcluster/#specnodeselector","title":"<code>.spec.nodeSelector</code>","text":"<p>Selects on which nodes Piraeus Datastore should be deployed. Nodes that are excluded by the selector will not be able to run any workload using a Piraeus volume.</p> <p>If empty (the default), Piraeus will be deployed on all nodes in the cluster.</p> <p>When this is used together with <code>.spec.nodeAffinity</code>, both need to match in order for a node to run Piraeus.</p>"},{"location":"reference/linstorcluster/#example","title":"Example","text":"<p>This example restricts Piraeus Datastore to nodes matching <code>example.com/storage: \"yes\"</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  nodeSelector:\n    example.com/storage: \"yes\"\n</code></pre>"},{"location":"reference/linstorcluster/#specnodeaffinity","title":"<code>.spec.nodeAffinity</code>","text":"<p>Selects on which nodes Piraeus Datastore should be deployed. Nodes that are excluded by the affinity will not be able to run any workload using a Piraeus volume.</p> <p>If empty (the default), Piraeus will be deployed on all nodes in the cluster.</p> <p>When this is used together with <code>.spec.nodeSelector</code>, both need to match in order for a node to run Piraeus.</p>"},{"location":"reference/linstorcluster/#example_1","title":"Example","text":"<p>This example restricts Piraeus Datastore to nodes in zones <code>a</code> and <code>b</code>, but not on <code>control-plane</code> nodes:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  nodeAffinity:\n    nodeSelectorTerms:\n      - matchExpressions:\n          - key: topology.kubernetes.io/zone\n            operator: In\n            values:\n              - a\n              - b\n          - key: node-role.kubernetes.io/control-plane\n            operator: DoesNotExist\n</code></pre>"},{"location":"reference/linstorcluster/#specrepository","title":"<code>.spec.repository</code>","text":"<p>Sets the default image registry to use for all Piraeus images. The full image name is created by appending an image identifier and tag.</p> <p>If empty (the default), Piraeus will use <code>quay.io/piraeusdatastore</code>.</p> <p>The current list of default images is available here.</p>"},{"location":"reference/linstorcluster/#example_2","title":"Example","text":"<p>This example pulls all Piraeus images from <code>registry.example.com/piraeus-mirror</code> rather than <code>quay.io/piraeusdatastore</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  repository: registry.example.com/piraeus-mirror\n</code></pre>"},{"location":"reference/linstorcluster/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Sets the given properties on the LINSTOR Controller level, applying them to the whole Cluster.</p>"},{"location":"reference/linstorcluster/#example_3","title":"Example","text":"<p>This example sets the port range used for DRBD\u00ae volumes to <code>10000-20000</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  properties:\n    - name: TcpPortAutoRange\n      value: \"10000-20000\"\n</code></pre>"},{"location":"reference/linstorcluster/#speclinstorpassphrasesecret","title":"<code>.spec.linstorPassphraseSecret</code>","text":"<p>Configures the LINSTOR passphrase, used by LINSTOR when creating encrypted volumes and storing access credentials for backups.</p> <p>The referenced secret must exist in the same namespace as the operator (by default <code>piraeus-datastore</code>), and have a <code>MASTER_PASSPHRASE</code> entry.</p>"},{"location":"reference/linstorcluster/#example_4","title":"Example","text":"<p>This example configures a passphrase <code>example-passphrase</code>. Please choose a different passphrase for your deployment.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: linstor-passphrase\n  namespace: piraeus-datastore\ndata:\n  # CHANGE THIS TO USE YOUR OWN PASSPHRASE!\n  # Created by: echo -n \"example-passphrase\" | base64\n  MASTER_PASSPHRASE: ZXhhbXBsZS1wYXNzcGhyYXNl\n---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  linstorPassphraseSecret: linstor-passphrase\n</code></pre>"},{"location":"reference/linstorcluster/#specpatches","title":"<code>.spec.patches</code>","text":"<p>The given patches will be applied to all resources controlled by the operator. The patches are forwarded to <code>kustomize</code> internally, and take the same format.</p> <p>The unpatched resources are available in the subdirectories of the <code>pkg/resources</code> directory.</p>"},{"location":"reference/linstorcluster/#warning","title":"Warning","text":"<p>No checks are run on the result of user-supplied patches: the resources are applied as-is. Patching some fundamental aspect, such as removing a specific volume from a container may lead to a degraded cluster.</p>"},{"location":"reference/linstorcluster/#example_5","title":"Example","text":"<p>This example sets a CPU limit of <code>10m</code> on the CSI Node init container and changes the LINSTOR Controller service to run in <code>SingleStack</code> mode.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  patches:\n    - target:\n        kind: Daemonset\n        name: csi-node\n      patch: |-\n        - op: add\n          path: /spec/template/spec/initContainers/0/resources\n          value:\n            limits:\n               cpu: 10m\n    - target:\n        kind: Service\n        name: linstor-controller\n      patch: |-\n        apiVersion: v1\n        kind: service\n        metadata:\n          name: linstor-controller\n        spec:\n          ipFamilyPolicy: SingleStack\n</code></pre>"},{"location":"reference/linstorcluster/#specexternalcontroller","title":"<code>.spec.externalController</code>","text":"<p>Configures the Operator to use an external controller instead of deploying one in the Cluster.</p>"},{"location":"reference/linstorcluster/#example_6","title":"Example","text":"<p>This examples instructs the Operator to use the external LINSTOR Controller reachable at <code>http://linstor.example.com:3370</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  externalController:\n    url: http://linstor.example.com:3370\n</code></pre>"},{"location":"reference/linstorcluster/#speccontroller","title":"<code>.spec.controller</code>","text":"<p>Controls the LINSTOR Controller Deployment: * Setting <code>enabled: false</code> disables the controller deployment entirely. See also <code>.spec.externalController</code>. * Setting a <code>podTemplate:</code> allows for simple modification of the LINSTOR Controller Deployment.</p>"},{"location":"reference/linstorcluster/#example_7","title":"Example","text":"<p>This example configures a resource request of <code>memory: 1Gi</code> for the LINSTOR Controller Deployment:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  controller:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-controller\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#speccsicontroller","title":"<code>.spec.csiController</code>","text":"<p>Controls the CSI Controller Deployment: * Setting <code>enabled: false</code> disables the deployment entirely. * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Controller Deployment.</p>"},{"location":"reference/linstorcluster/#example_8","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Controller Deployment:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  csiController:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-csi\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#speccsinode","title":"<code>.spec.csiNode</code>","text":"<p>Controls the CSI Node DaemonSet: * Setting <code>enabled: false</code> disables the deployment entirely. * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Node DaemonSet.</p>"},{"location":"reference/linstorcluster/#example_9","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Node DaemonSet:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  csiNode:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: linstor-csi\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#spechighavailabilitycontroller","title":"<code>.spec.highAvailabilityController</code>","text":"<p>Controls the High Availability Controller DaemonSet: * Setting <code>enabled: false</code> disables the deployment entirely. * Setting a <code>podTemplate:</code> allows for simple modification of the CSI Node Deployment.</p>"},{"location":"reference/linstorcluster/#example_10","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 10m</code> for the CSI Node Deployment:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  highAvailabilityController:\n    enabled: true\n    podTemplate:\n      spec:\n        containers:\n          - name: ha-controller\n            resources:\n              requests:\n                memory: 1Gi\n</code></pre>"},{"location":"reference/linstorcluster/#specinternaltls","title":"<code>.spec.internalTLS</code>","text":"<p>Configures a TLS secret used by the LINSTOR Controller to: * Validate the certificate of the LINSTOR Satellites, that is the Satellites must have certificates signed by <code>ca.crt</code>. * Provide a client certificate for authentication with LINSTOR Satellites, that is <code>tls.key</code> and <code>tls.crt</code> must be accepted by the Satellites.</p> <p>To configure TLS communication between Satellite and Controller, <code>LinstorSatelliteConfiguration.spec.internalTLS</code> must be set accordingly.</p> <p>Setting a <code>secretName</code> is optional, it will default to <code>linstor-controller-internal-tls</code>.</p> <p>Optional, a reference to a cert-manager <code>Issuer</code> can be provided to let the operator create the required secret.</p> <p>If the referenced secret does not contain a <code>ca.crt</code> certificate of a certificate authority, a <code>caReference</code> pointing to a secondary <code>Secret</code> or <code>ConfigMap</code> resource can be configured.</p>"},{"location":"reference/linstorcluster/#example_11","title":"Example","text":"<p>This example creates a manually provisioned TLS secret and references it in the LinstorCluster configuration.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-linstor-controller-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    secretName: my-linstor-controller-tls\n</code></pre>"},{"location":"reference/linstorcluster/#example_12","title":"Example","text":"<p>This example sets up automatic creation of the LINSTOR Controller TLS secret using a cert-manager issuer named <code>piraeus-root</code>. The certificates will be validated against the certificate in the <code>trust-root</code> ConfigMap.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  internalTLS:\n    certManager:\n      kind: Issuer\n      name: piraeus-root\n    caReference:\n      name: trust-root\n      kind: ConfigMap\n      key: root.crt\n</code></pre>"},{"location":"reference/linstorcluster/#specapitls","title":"<code>.spec.apiTLS</code>","text":"<p>Configures the TLS secrets used to secure the LINSTOR API. There are four different secrets to configure:</p> <ul> <li><code>apiSecretName</code>: sets the name of the secret used by the LINSTOR Controller to enable HTTPS. Defaults to   <code>linstor-api-tls</code>. All clients of the API must have certificates signed by the <code>ca.crt</code> of this secret.</li> <li><code>clientSecretName</code>: sets the name of the secret used by the Operator to connect to the LINSTOR API. Defaults to   <code>linstor-client-tls</code>. Must be trusted by <code>ca.crt</code> in the API Secret. Also used by the LINSTOR Controller to configure   the included LINSTOR CLI.</li> <li><code>csiControllerSecretName</code> sets the name of the secret used by the CSI Controller. Defaults to   <code>linstor-csi-controller-tls</code>. Must be trusted by <code>ca.crt</code> in the API Secret.</li> <li><code>csiNodeSecretName</code> sets the name of the secret used by the CSI Controller. Defaults to <code>linstor-csi-node-tls</code>.   Must be trusted by <code>ca.crt</code> in the API Secret.</li> </ul> <p>Optional, a reference to a cert-manager <code>Issuer</code> can be provided to let the operator create the required secrets.</p> <p>If the referenced secret does not contain a <code>ca.crt</code> certificate of a certificate authority, a <code>caReference</code> pointing to a secondary <code>Secret</code> or <code>ConfigMap</code> resource can be configured.</p>"},{"location":"reference/linstorcluster/#example_13","title":"Example","text":"<p>This example creates a manually provisioned TLS secret and references it in the LinstorCluster configuration. It uses the same secret for all clients of the LINSTOR API.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-linstor-api-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-linstor-client-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    apiSecretName: my-linstor-api-tls\n    clientSecretName: my-linstor-client-tls\n    csiControllerSecretName: my-linstor-client-tls\n    csiNodeSecretName: my-linstor-client-tls\n</code></pre>"},{"location":"reference/linstorcluster/#example_14","title":"Example","text":"<p>This example sets up automatic creation of the LINSTOR API and LINSTOR Client TLS secret using a cert-manager issuer named <code>piraeus-root</code>. The certificates will be validated against the certificate in the <code>trust-root</code> Secret.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  apiTLS:\n    certManager:\n      kind: Issuer\n      name: piraeus-root\n    caReference:\n      name: trust-root\n      kind: Secret\n      key: root.crt\n</code></pre>"},{"location":"reference/linstorcluster/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the cluster.</p>"},{"location":"reference/linstorcluster/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the Cluster through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Applied</code> All Kubernetes resources controlled by the Operator are applied and up to date. <code>Available</code> The LINSTOR Controller is deployed and reponding to requests. <code>Configured</code> The LINSTOR Controller is configured with the properties from <code>.spec.properties</code>"},{"location":"reference/linstornodeconnection/","title":"<code>LinstorNodeConnection</code>","text":"<p>This resource controls the state of the LINSTOR\u00ae node connections.</p> <p>Node connections control the DRBD options set on a particular path, such as which protocol and network interface to use.</p>"},{"location":"reference/linstornodeconnection/#spec","title":"<code>.spec</code>","text":"<p>Configures the desired state of the node connections.</p>"},{"location":"reference/linstornodeconnection/#specselector","title":"<code>.spec.selector</code>","text":"<p>Selects which connections the resource should apply to. By default, a <code>LinstorNodeConnection</code> resource applies to every possible connection in the cluster.</p> <p>A resource applies to a connection if one of the provided selectors match. A selector itself can contain multiple expressions. If multiple expressions are specified in a selector, the connection must match all of them.</p> <p>Every expression requires a label name (<code>key</code>) on which it operates and an operator <code>op</code>. Depending on the operator, you can also specify specific values for the node label.</p> <p>The following operators are available:</p> <ul> <li><code>Exists</code>, the label specified in <code>key</code> is present on both nodes of the connection, with any value. This is the   default.</li> <li><code>DoesNotExist</code>, the label specified in <code>key</code> is not present on the nodes in the connections.</li> <li><code>In</code>, the label specified in <code>key</code> matches any of the provided <code>values</code> for the nodes in the connection.</li> <li><code>NotIn</code> the label specified in <code>key</code> does not match any of the provided <code>values</code> for the nodes in the connection.</li> <li><code>Same</code> the label specified in <code>key</code> has the same value for the nodes in the connection.</li> <li><code>NotSame</code> the label specified in <code>key</code> has different values for the nodes in the connection.</li> </ul>"},{"location":"reference/linstornodeconnection/#example","title":"Example","text":"<p>This example restricts the resource to connections between nodes matching <code>example.com/storage: \"yes\"</code>:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: selector\nspec:\n  selector:\n    - matchLabels:\n        - key: example.com/storage\n          op: In\n          values:\n            - yes\n</code></pre>"},{"location":"reference/linstornodeconnection/#example_1","title":"Example","text":"<p>This example restricts the resource to connections between nodes in the same region, but different zones.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: selector\nspec:\n  selector:\n    - matchLabels:\n        - key: topology.kubernetes.io/region\n          op: Same\n        - key: topology.kubernetes.io/zone\n          op: NotSame\n</code></pre>"},{"location":"reference/linstornodeconnection/#specpaths","title":"<code>.spec.paths</code>","text":"<p>Paths configure one or more network connections between nodes. If a path is configured, LINSTOR will use the given network interface to configure DRBD replication. The network interfaces have to be registered with LINSTOR first, using <code>linstor node interface create ...</code>.</p>"},{"location":"reference/linstornodeconnection/#example_2","title":"Example","text":"<p>This example configures all nodes to use the \"data-nic\" network interface instead of the default interface.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: network-paths\nspec:\n  paths:\n    - name: path1\n      interface: data-nic\n</code></pre>"},{"location":"reference/linstornodeconnection/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Sets the given properties on the LINSTOR Node Connection level.</p>"},{"location":"reference/linstornodeconnection/#example_3","title":"Example","text":"<p>This example sets the DRBD\u00ae protocol to <code>C</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorNodeConnection\nmetadata:\n  name: drbd-options\nspec:\n  properties:\n    - name: DrbdOptions/Net/protocol\n      value: C\n</code></pre>"},{"location":"reference/linstornodeconnection/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the connections.</p>"},{"location":"reference/linstornodeconnection/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the LINSTOR Node Connection through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Configured</code> The LINSTOR Node Connection is applied to all matching pairs of nodes."},{"location":"reference/linstorsatellite/","title":"<code>LinstorSatellite</code>","text":"<p>This resource controls the state of a LINSTOR\u00ae satellite.</p> <p>NOTE: This resource is not intended to be changed directly, instead it is created by the Piraeus Operator by merging all matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#spec","title":"<code>.spec</code>","text":"<p>Holds the desired state the satellite.</p>"},{"location":"reference/linstorsatellite/#specrepository","title":"<code>.spec.repository</code>","text":"<p>Holds the default image registry to use for all Piraeus images. Inherited from <code>LinstorCluster</code>.</p> <p>If empty (the default), the operator will use <code>quay.io/piraeusdatastore</code>.</p>"},{"location":"reference/linstorsatellite/#specclusterref","title":"<code>.spec.clusterRef</code>","text":"<p>Holds a reference to the <code>LinstorCluster</code> that controls this satellite.</p>"},{"location":"reference/linstorsatellite/#specstoragepools","title":"<code>.spec.storagePools</code>","text":"<p>Holds the storage pools to configure on the node. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Holds the properties which should be set on the node level. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#specinternaltls","title":"<code>.spec.internalTLS</code>","text":"<p>Configures a TLS secret used by the LINSTOR Satellite. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#specpatches","title":"<code>.spec.patches</code>","text":"<p>Holds patches to apply to the Kubernetes resources. Inherited from matching <code>LinstorSatelliteConfiguration</code> resources.</p>"},{"location":"reference/linstorsatellite/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the satellite.</p>"},{"location":"reference/linstorsatellite/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the LINSTOR Satellite through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Applied</code> All Kubernetes resources were applied. <code>Available</code> The LINSTOR Satellite is connected to the LINSTOR Controller <code>Configured</code> Storage Pools and Properties are configured on the Satellite <code>EvacuationCompleted</code> Only available when the Satellite is being deleted: Indicates progress of the eviction of resources."},{"location":"reference/linstorsatelliteconfiguration/","title":"<code>LinstorSatelliteConfiguration</code>","text":"<p>This resource controls the state of one or more LINSTOR\u00ae satellites.</p>"},{"location":"reference/linstorsatelliteconfiguration/#spec","title":"<code>.spec</code>","text":"<p>Configures the desired state of satellites.</p>"},{"location":"reference/linstorsatelliteconfiguration/#specnodeselector","title":"<code>.spec.nodeSelector</code>","text":"<p>Selects which nodes the LinstorSatelliteConfiguration should apply to. If empty, the configuration applies to all nodes.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example","title":"Example","text":"<p>This example sets the <code>AutoplaceTarget</code> property to <code>no</code> on all nodes labelled <code>piraeus.io/autoplace: \"no\"</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: disabled-nodes\nspec:\n  nodeSelector:\n    piraeus.io/autplace: \"no\"\n  properties:\n    - name: AutoplaceTarget\n      value: \"no\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specnodeaffinity","title":"<code>.spec.nodeAffinity</code>","text":"<p>Selects which nodes the LinstorSatelliteConfiguration should apply to. If empty, the configuration applies to all nodes.</p> <p>When this is used together with <code>.spec.nodeSelector</code>, both need to match in order for the configuration to apply to a node.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_1","title":"Example","text":"<p>This example sets the <code>AutoplaceTarget</code> property to <code>no</code> on all non-worker nodes:</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: disabled-nodes\nspec:\n  nodeAffinity:\n    nodeSelectorTerms:\n      - matchExpressions:\n          - key: node-role.kubernetes.io/control-plane\n            operator: Exists\n  properties:\n    - name: AutoplaceTarget\n      value: \"no\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specproperties","title":"<code>.spec.properties</code>","text":"<p>Sets the given properties on the LINSTOR Satellite level.</p> <p>The property value can either be set directly using <code>value</code>, inherited from the Kubernetes Node's metadata using <code>valueFrom</code>, or expanded from Kubernetes Node's metadata using <code>expandFrom</code>. Metadata fields are specified using the same syntax as the Downward API for Pods.</p> <p>Using <code>expandFrom</code> allows for using field references matching more than one field. Either specify a field that is already a map (<code>metadata.labels</code> or <code>metadata.annotations</code>), or select a subset by using <code>*</code> at the end of a key. Using <code>*</code> will select the keys and values matching the prefix up to the <code>*</code> character. There are two ways to use <code>expandFrom</code>:</p> <ul> <li>Setting a <code>nameTemplate</code> will create one property per matched field. The property name is generated by taking   the <code>name</code> field and appending the expanded <code>nameTemplate</code>. <code>nameTemplate</code> supports the following expansions:</li> <li><code>$1</code> is replaced with the field key, i.e. the part matched by the <code>+</code> character.</li> <li><code>$2</code> is replaced with the value of the matched field.</li> </ul> <p>The <code>valueTemplate</code> is expanded using the same replacements, and sets the property value. * Setting no <code>nameTemplate</code> will create one property using <code>name</code>. The value of the property is the   joined expansion of the <code>valueTemplate</code> field for every matched field. See above for supported expansions. The result   is joined using the optional <code>delimiter</code> value.</p> <p>In addition, setting <code>optional</code> to true means the property is only applied if the value is not empty. This is useful in case the property value should be inherited from the node's metadata</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_2","title":"Example","text":"<p>This examples sets the following Properties on every satellite: * <code>PrefNic</code> (the preferred network interface) is always set to <code>default-ipv6</code> * <code>Aux/example-property</code> (an auxiliary property, unused by LINSTOR itself) takes the value from the <code>piraeus.io/example</code>   label of the Kubernetes Node. If a node has no <code>piraeus.io/example</code> label, the property value will be <code>\"\"</code>. * <code>AutoplaceTarget</code> (if set to <code>no</code>, will exclude the node from LINSTOR's Autoplacer) takes the value from the   <code>piraeus.io/autoplace</code> annotation of the Kubernetes Node. If a node has no <code>piraeus.io/autoplace</code> annotation, the   property will not be set. * <code>Aux/role/</code> copies all <code>node-role.kubernetes.io/*</code> label keys and values. For example, a worker node with the   <code>node-role.kubernetes.io/worker: \"true\"</code> label will have <code>Aux/role/worker</code> set to <code>\"true\"</code>. * <code>Aux/features</code> copies the names of all <code>feature.example.com/*</code> label keys to the value, joined by <code>,</code>. For example,   a node with <code>feature.example.com/gpu</code> and <code>feature.example.com/storage</code> will have <code>Aux/features</code> set to   <code>\"gpu,storage\"</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: ipv6-nodes\nspec:\n  properties:\n    - name: PrefNic\n      value: \"default-ipv6\"\n    - name: Aux/example-property\n      valueFrom:\n        nodeFieldRef: metadata.labels['piraeus.io/example']\n    - name: AutoplaceTarget\n      valueFrom:\n        nodeFieldRef: metadata.annotations['piraeus.io/autoplace']\n      optional: yes\n    - name: Aux/role/\n      expandFrom:\n        nodeFieldRef: metadata.labels['node-role.kubernetes.io/*']\n        nameTemplate: \"$1\"\n        valueTemplate: \"$2\"\n    - name: Aux/features\n      expandFrom:\n        nodeFieldRef: metadata.labels['feature.example.com/*']\n        valueTemplate: \"$1\"\n        delimiter: \",\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specstoragepools","title":"<code>.spec.storagePools</code>","text":"<p>Configures LINSTOR Storage Pools.</p> <p>Every Storage Pool needs at least a <code>name</code>, and a type. Types are specified by setting a (potentially empty) value on the matching key. Available types are:</p> <ul> <li><code>lvmPool</code>: Configures a LVM Volume Group as storage   pool. Defaults to using the storage pool name as the VG name. Can be overridden by setting <code>volumeGroup</code>.</li> <li><code>lvmThinPool</code>: Configures a LVM Thin Pool as storage pool.   Defaults to using the storage pool name as name for the thin pool volume and the storage pool name prefixed by   <code>linstor_</code> as the VG name. Can be overridden by setting <code>thinPool</code> and <code>volumeGroup</code>.</li> <li><code>filePool</code>: Configures a file system based storage pool. Configures a host directory as location for the volume files.   Defaults to using the <code>/var/lib/linstor-pools/&lt;storage pool name&gt;</code> directory.</li> <li><code>fileThinPool</code>: Configures a file system based storage pool. Behaves the same as <code>filePool</code>, except the files will   be thinly allocated on file systems that support sparse files.</li> <li><code>zfsPool</code>: Configure a ZFS ZPool as storage pool. Defaults to using the storage   pool name as name for the zpool. Can be overriden by setting <code>zPool</code>.</li> <li><code>zfsThinPool</code>: Configure a ZFS ZPool as storage pool. Behaves the same as   <code>zfsPool</code>, except the contained zVol will be created using sparse reservation.</li> </ul> <p>Optionally, you can configure LINSTOR to automatically create the backing pools. <code>source.hostDevices</code> takes a list of raw block devices, which LINSTOR will prepare as the chosen backing pool.</p> <p>All storage pools also can also be configured with <code>properties</code>. Properties are set on the Storage Pool level. The configuration values have the same form as Satellite Properties.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_3","title":"Example","text":"<p>This example configures these LINSTOR Storage Pools on all satellites: * A LVM Pool named <code>vg1</code>. It will use the VG <code>vg1</code>, which needs to exist on the nodes already. * A LVM Thin Pool named <code>vg1-thin</code>. It will use the thin pool <code>vg1/thin</code>, which also needs to exist on the nodes. * A LVM Pool named <code>vg2-from-raw-devices</code>. It will use the VG <code>vg2</code>, which will be created on demand from the raw   devices <code>/dev/sdb</code> and <code>/dev/sdc</code> if it does not exist already. In addition, it sets the <code>StorDriver/LvcreateOptions</code>   property to <code>-i 2</code>, which causes every created LV to be striped across 2 PVs. * A File System Pool named <code>fs1</code>. It will use the <code>/var/lib/linstor-pools/fs1</code> directory on the host, creating the   directory if necessary. * A File System Pool named <code>fs2</code>, using sparse files. It will use the custom <code>/mnt/data</code> directory on the host. * A ZFS Pool named <code>zfs1</code>. It will use ZPool <code>zfs1</code>, which needs to exist on the nodes already. * A ZFS Thin Pool named <code>zfs2</code>. It will use ZPool <code>zfs-thin2</code>, which will be created on demand from the raw device   <code>/dev/sdd</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: storage-satellites\nspec:\n  storagePools:\n    - name: vg1\n      lvmPool: {}\n    - name: vg1-thin\n      lvmThinPool:\n        volumeGroup: vg1\n        thinPool: thin\n    - name: vg2-from-raw-devices\n      lvmPool:\n        volumeGroup: vg2\n      source:\n        hostDevices:\n          - /dev/sdb\n          - /dev/sdc\n      properties:\n        - name: StorDriver/LvcreateOptions\n          value: '-i 2'\n    - name: fs1\n      filePool: {}\n    - name: fs2\n      fileThinPool:\n        directory: /mnt/data\n    - name: zfs1\n      zfsPool: {}\n    - name: zfs2\n      zfsThinPool:\n        zPool: zfs-thin2\n      source:\n        hostDevices:\n        - /dev/sdd\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specinternaltls","title":"<code>.spec.internalTLS</code>","text":"<p>Configures a TLS secret used by the LINSTOR Satellites to: * Validate the certificate of the LINSTOR Controller, that is the Controller must have certificates signed by <code>ca.crt</code>. * Provide a server certificate for authentication by the LINSTOR Controller, that is <code>tls.key</code> and <code>tls.crt</code> must be accepted by the Controller.</p> <p>To configure TLS communication between Satellite and Controller, <code>LinstorCluster.spec.internalTLS</code> must be set accordingly.</p> <p>Setting a <code>secretName</code> is optional, it will default to <code>&lt;node-name&gt;-tls</code>, where <code>&lt;node-name&gt;</code> is replaced with the name of the Kubernetes Node.</p> <p>Optional, a reference to a cert-manager <code>Issuer</code> can be provided to let the operator create the required secret.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_4","title":"Example","text":"<p>This example creates a manually provisioned TLS secret and references it in the LinstorSatelliteConfiguration, setting it for all nodes.</p> <pre><code>---\napiVersion: v1\nkind: Secret\nmetadata:\n  name: my-node-tls\n  namespace: piraeus-datastore\ndata:\n  ca.crt: LS0tLS1CRUdJT...\n  tls.crt: LS0tLS1CRUdJT...\n  tls.key: LS0tLS1CRUdJT...\n---\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: satellite-tls\nspec:\n  internalTLS:\n    secretName: my-node-tls\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#example_5","title":"Example","text":"<p>This example sets up automatic creation of the LINSTOR Satellite TLS secrets using a cert-manager issuer named <code>piraeus-root</code>.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: satellite-tls\nspec:\n  internalTLS:\n    certManager:\n      kind: Issuer\n      name: piraeus-root\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specipfamilies","title":"<code>.spec.ipFamilies</code>","text":"<p>Configures the IP Family (IPv4 or IPv6) to use to connect to the LINSTOR Satellite.</p> <p>If unset, the LINSTOR Controller will attempt to reach the LINSTOR Satellite via all recognized addresses in the Satellite Pods' Status. If set, the LINSTOR Controller will only attempt to reach the LINSTOR Satellite via all addresses matching the listed IP Families.</p> <p>Valid values are <code>IPv4</code> and <code>IPv6</code>.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_6","title":"Example","text":"<p>This example configures the LINSTOR Controller to only use IPv4, even in a dual stack cluster.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: ipv4-only\nspec:\n  ipFamilies:\n  - IPv4\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specpodtemplate","title":"<code>.spec.podTemplate</code>","text":"<p>Configures the Pod used to run the LINSTOR Satellite.</p> <p>The template is applied as a patch (see <code>.spec.patches</code>) to the default resources, so it can be \"sparse\".</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_7","title":"Example","text":"<p>This example configures a resource request of <code>cpu: 100m</code> on the satellite, and also enables host networking.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: resource-and-host-network\nspec:\n  podTemplate:\n    spec:\n      hostNetwork: true\n      containers:\n        - name: linstor-satellite\n          resources:\n            requests:\n              cpu: 100m\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#specpatches","title":"<code>.spec.patches</code>","text":"<p>The given patches will be applied to all resources controlled by the operator. The patches are forwarded to <code>kustomize</code> internally, and take the same format.</p> <p>The unpatched resources are available in the subdirectories of the <code>pkg/resources/satellite</code> directory.</p>"},{"location":"reference/linstorsatelliteconfiguration/#warning","title":"Warning","text":"<p>No checks are run on the result of user-supplied patches: the resources are applied as-is. Patching some fundamental aspect, such as removing a specific volume from a container may lead to a degraded cluster.</p>"},{"location":"reference/linstorsatelliteconfiguration/#example_8","title":"Example","text":"<p>This example configures the LINSTOR Satellite to use the \"TRACE\" log level, creating very verbose output.</p> <pre><code>apiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: all-satellites\nspec:\n  patches:\n    - target:\n        kind: ConfigMap\n        name: satellite-config\n      patch: |-\n        apiVersion: v1\n        kind: ConfigMap\n        metadata:\n          name: satellite-config\n        data:\n          linstor_satellite.toml: |\n            [logging]\n              linstor_level = \"TRACE\"\n</code></pre>"},{"location":"reference/linstorsatelliteconfiguration/#status","title":"<code>.status</code>","text":"<p>Reports the actual state of the cluster.</p>"},{"location":"reference/linstorsatelliteconfiguration/#statusconditions","title":"<code>.status.conditions</code>","text":"<p>The Operator reports the current state of the Satellite Configuration through a set of conditions. Conditions are identified by their <code>type</code>.</p> <code>type</code> Explanation <code>Applied</code> The given configuration was applied to all <code>LinstorSatellite</code> resources."},{"location":"tutorial/","title":"Tutorials","text":"<p>These tutorials help you get started with Piraeus Datastore</p>"},{"location":"tutorial/#get-started","title":"Get Started","text":"<p>Get started with Piraeus Datastore by deploying Piraeus Operator and provisioning your first volume.</p>"},{"location":"tutorial/#creating-replicated-volumes","title":"Creating Replicated Volumes","text":"<p>Create replicated volumes, making your data accessible on any cluster node.</p>"},{"location":"tutorial/#creating-and-restoring-from-snapshots","title":"Creating and Restoring from Snapshots","text":"<p>Create snapshots and restore a volume, safeguarding data against accidental deletion.</p>"},{"location":"tutorial/get-started/","title":"Get Started","text":"<p>Learn about the ways to get started with Piraeus Datastore by deploying Piraeus Operator and provisioning your first volume.</p>"},{"location":"tutorial/get-started/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install the Linux kernel headers on the hosts.</li> <li>Install <code>kubectl</code> version <code>&gt;= 1.22</code></li> </ul>"},{"location":"tutorial/get-started/#install-piraeus-operator","title":"Install Piraeus Operator","text":"<p>In this tutorial we will be using <code>kubectl</code> with the built-in <code>kustomize</code> feature to deploy Piraeus Operator. All resources needed to run Piraeus Operator are included in a single Kustomization.</p> <p>Install Piraeus Operator by running:</p> <pre><code>$ kubectl apply --server-side -k \"https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.7.1\"\nnamespace/piraeus-datastore configured\n...\n</code></pre> <p>The Piraeus Operator will be installed in a new namespace <code>piraeus-datastore</code>. After a short wait the operator will be ready. The following command waits until the Operator is ready:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -n piraeus-datastore -l app.kubernetes.io/component=piraeus-operator\npod/piraeus-operator-controller-manager-dd898f48c-bhbtv condition met\n</code></pre>"},{"location":"tutorial/get-started/#deploy-piraeus-datastore","title":"Deploy Piraeus Datastore","text":"<p>Now, we will deploy Piraeus Datastore using a new resource managed by Piraeus Operator. We create a <code>LinstorCluster</code>, which creates all the necessary resources (Deployments, Pods, and so on...) for our Datastore:</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec: {}\nEOF\n</code></pre> <p>Again, all workloads will be deployed to the <code>piraeus-datastore</code> namespace. After a short wait the Datastore will ready:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -n piraeus-datastore -l app.kubernetes.io/name=piraeus-datastore\npod/linstor-controller-65cbbc74db-9vm9n condition met\npod/linstor-csi-controller-5ccb7d84cd-tvd9h condition met\npod/linstor-csi-node-2lkpd condition met\npod/linstor-csi-node-hbcvv condition met\npod/linstor-csi-node-hmrd7 condition met\npod/n1.example.com condition met\npod/n2.example.com condition met\npod/n3.example.com condition met\npod/piraeus-operator-controller-manager-dd898f48c-bhbtv condition met\n</code></pre> <p>We can now inspect the state of the deployed LINSTOR\u00ae Cluster using the <code>linstor</code> client:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor node list\n+-------------------------------------------------------------------+\n| Node           | NodeType  | Addresses                   | State  |\n|===================================================================|\n| n1.example.com | SATELLITE | 10.116.72.166:3366 (PLAIN)  | Online |\n| n2.example.com | SATELLITE | 10.127.183.190:3366 (PLAIN) | Online |\n| n3.example.com | SATELLITE | 10.125.97.33:3366 (PLAIN)   | Online |\n+-------------------------------------------------------------------+\n</code></pre>"},{"location":"tutorial/get-started/#configuring-storage","title":"Configuring Storage","text":"<p>We have not yet configured any storage location for our volumes. This can be accomplished by creating a new <code>LinstorSatelliteConfiguration</code> resource. We will create a storage pool of type <code>fileThinPool</code> on each node. We chose <code>fileThinPool</code> as it does not require further configuration on the host.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: piraeus.io/v1\nkind: LinstorSatelliteConfiguration\nmetadata:\n  name: storage-pool\nspec:\n  storagePools:\n    - name: pool1\n      fileThinPool:\n        directory: /var/lib/piraeus-datastore/pool1\nEOF\n</code></pre> <p>This will cause some Pods to be recreated. While this occurs <code>linstor node list</code> will temporarily show offline nodes:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor node list\n+--------------------------------------------------------------------+\n| Node           | NodeType  | Addresses                   | State   |\n|====================================================================|\n| n1.example.com | SATELLITE | 10.116.72.166:3366 (PLAIN)  | OFFLINE |\n| n2.example.com | SATELLITE | 10.127.183.190:3366 (PLAIN) | OFFLINE |\n| n3.example.com | SATELLITE | 10.125.97.33:3366 (PLAIN)   | OFFLINE |\n+--------------------------------------------------------------------+\n</code></pre> <p>Waiting a bit longer, the nodes will be <code>Online</code> again. Once the nodes are connected again, we can verify that the storage pools were configured:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor storage-pool list\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n| StoragePool          | Node           | Driver    | PoolName                         | FreeCapacity | TotalCapacity | CanSnapshots | State | SharedName |\n|=========================================================================================================================================================|\n| DfltDisklessStorPool | n1.example.com | DISKLESS  |                                  |              |               | False        | Ok    |            |\n| DfltDisklessStorPool | n2.example.com | DISKLESS  |                                  |              |               | False        | Ok    |            |\n| DfltDisklessStorPool | n3.example.com | DISKLESS  |                                  |              |               | False        | Ok    |            |\n| pool1                | n1.example.com | FILE_THIN | /var/lib/piraeus-datastore/pool1 |    24.54 GiB |     49.30 GiB | True         | Ok    |            |\n| pool1                | n2.example.com | FILE_THIN | /var/lib/piraeus-datastore/pool1 |    23.03 GiB |     49.30 GiB | True         | Ok    |            |\n| pool1                | n3.example.com | FILE_THIN | /var/lib/piraeus-datastore/pool1 |    26.54 GiB |     49.30 GiB | True         | Ok    |            |\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre>"},{"location":"tutorial/get-started/#using-piraeus-datastore","title":"Using Piraeus Datastore","text":"<p>We now have successfully deployed and configured Piraeus Datastore, and are ready to create our first <code>PersistentVolume</code> in Kubernetes.</p> <p>First, we will set up a new <code>StorageClass</code> for our volumes. In the <code>StorageClass</code>, we specify the storage pool from above:</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: piraeus-storage\nprovisioner: linstor.csi.linbit.com\nallowVolumeExpansion: true\nvolumeBindingMode: WaitForFirstConsumer\nparameters:\n  linstor.csi.linbit.com/storagePool: pool1\nEOF\n</code></pre> <p>Next, we will create a <code>PersistentVolumeClaim</code>, requesting 1G of storage from our newly created <code>StorageClass</code>.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: data-volume\nspec:\n  storageClassName: piraeus-storage\n  resources:\n    requests:\n      storage: 1Gi\n  accessModes:\n    - ReadWriteOnce\nEOF\n</code></pre> <p>When we check the created PersistentVolumeClaim, we can see that it remains in <code>Pending</code> state.</p> <pre><code>$ kubectl get persistentvolumeclaim\nNAME          STATUS    VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS      AGE\ndata-volume   Pending                                      piraeus-storage   14s\n</code></pre> <p>We first need to create a \"consumer\", which in this case is just a <code>Pod</code>. For our consumer, we will create a Deployment for a simple web server, serving files from our volume.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: web-server\nspec:\n  selector:\n    matchLabels:\n      app.kubernetes.io/name: web-server\n  template:\n    metadata:\n      labels:\n        app.kubernetes.io/name: web-server\n    spec:\n      containers:\n        - name: web-server\n          image: nginx\n          volumeMounts:\n            - mountPath: /usr/share/nginx/html\n              name: data\n      volumes:\n        - name: data\n          persistentVolumeClaim:\n            claimName: data-volume\nEOF\n</code></pre> <p>After a short wait, the Pod is <code>Running</code>, and our <code>PersistentVolumeClaim</code> is now <code>Bound</code>:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=web-server\npod/web-server-84867b5449-hgdzx condition met\n$ kubectl get persistentvolumeclaim\nNAME          STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS      AGE\ndata-volume   Bound    pvc-9e1149e7-33db-47a7-8fc6-172514422143   1Gi        RWO            piraeus-storage   1m\n</code></pre> <p>Checking the running container, we see that the volume is mounted where we expected it:</p> <pre><code>$ kubectl exec deploy/web-server -- df -h /usr/share/nginx/html\nFilesystem      Size  Used Avail Use% Mounted on\n/dev/drbd1000   973M   24K  906M   1% /usr/share/nginx/html\n</code></pre> <p>Taking a look with the <code>linstor</code> client, we can see that the volume is listed in LINSTOR and marked as <code>InUse</code> by the Pod.</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor resource list-volumes\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n| Node           | Resource                                 | StoragePool | VolNr | MinorNr | DeviceName    | Allocated | InUse  |    State |\n|===========================================================================================================================================|\n| n1.example.com | pvc-9e1149e7-33db-47a7-8fc6-172514422143 | pool1       |     0 |    1000 | /dev/drbd1000 | 16.91 MiB | InUse  | UpToDate |\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre> <p>We have now successfully set up Piraeus Datastore and used it to provision a Persistent Volume in a Kubernetes cluster.</p>"},{"location":"tutorial/replicated-volumes/","title":"Creating Replicated Volumes","text":"<p>Learn about creating replicated volumes, making your data accessible on any cluster node.</p> <p>In this tutorial you will learn how to create a replicated volume, and verify that the data stays accessible when moving Pods from one node to another.</p>"},{"location":"tutorial/replicated-volumes/#prerequisites","title":"Prerequisites","text":"<ul> <li>A Kubernetes Cluster with at least two nodes.</li> <li>An installed and configured Piraeus Datastore. Learn how to get started in our introduction tutorial</li> </ul>"},{"location":"tutorial/replicated-volumes/#creating-the-volume","title":"Creating the Volume","text":"<p>First, we will create a new <code>StorageClass</code> for our replicated volumes. We will be using the <code>pool1</code> storage pool from the Get Started tutorial, but this time also set the <code>placementCount</code> to 2, telling LINSTOR\u00ae to store the volume data on two nodes.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: piraeus-storage-replicated\nprovisioner: linstor.csi.linbit.com\nallowVolumeExpansion: true\nvolumeBindingMode: WaitForFirstConsumer\nparameters:\n  linstor.csi.linbit.com/storagePool: pool1\n  linstor.csi.linbit.com/placementCount: \"2\"\nEOF\n</code></pre> <p>Next, we will again create a <code>PersistentVolumeClaim</code>, requesting a 1G replicated volume from our newly created <code>StorageClass</code>.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: replicated-volume\nspec:\n  storageClassName: piraeus-storage-replicated\n  resources:\n    requests:\n      storage: 1Gi\n  accessModes:\n    - ReadWriteOnce\nEOF\n</code></pre> <p>For our workload, we will create a Pod which will use the replicated volume to log its name, the current date, and the node it is running on.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: volume-logger\nspec:\n  selector:\n    matchLabels:\n      app.kubernetes.io/name: volume-logger\n  strategy:\n    type: Recreate\n  template:\n    metadata:\n      labels:\n        app.kubernetes.io/name: volume-logger\n    spec:\n      terminationGracePeriodSeconds: 0\n      containers:\n        - name: volume-logger\n          image: busybox\n          args:\n            - sh\n            - -c\n            - |\n              echo \"Hello from \\$HOSTNAME, running on \\$NODENAME, started at \\$(date)\" &gt;&gt; /volume/hello\n              # We use this to keep the Pod running\n              tail -f /dev/null\n          env:\n            - name: NODENAME\n              valueFrom:\n                fieldRef:\n                  fieldPath: spec.nodeName\n          volumeMounts:\n            - mountPath: /volume\n              name: replicated-volume\n      volumes:\n        - name: replicated-volume\n          persistentVolumeClaim:\n            claimName: replicated-volume\nEOF\n</code></pre> <p>After a short wait, the Pod is <code>Running</code>, our <code>PersistentVolumeClaim</code> is now <code>Bound</code>, and we can see that LINSTOR placed the volume on two nodes:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-84dd47f4cb-trh4l\n$ kubectl get persistentvolumeclaim\nNAME                STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS                 AGE\nreplicated-volume   Bound    pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d   1Gi        RWO            piraeus-storage-replicated   1m\n$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor resource list-volumes\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n| Node           | Resource                                 | StoragePool | VolNr | MinorNr | DeviceName    | Allocated | InUse  |    State |\n|===========================================================================================================================================|\n| n1.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 | 16.91 MiB | InUse  | UpToDate |\n| n2.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 |   876 KiB | Unused | UpToDate |\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre> <p>NOTE: If your cluster has three or more nodes, you will actually see a third volume, marked as <code>TieBreaker</code>. This is intentional and improves the behaviour should one of the cluster nodes become unavailable.</p> <p>Now, we can check that our Pod actually logged the expected information by reading <code>/volume/hello</code> in the Pod:</p> <pre><code>$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-84dd47f4cb-trh4l, running on n1.example.com, started at Fri Feb  3 08:53:47 UTC 2023\n</code></pre>"},{"location":"tutorial/replicated-volumes/#testing-replication","title":"Testing Replication","text":"<p>Now, we will verify that when we move the Pod to another node, we still have access to the same data.</p> <p>To test this, we will disable scheduling on the node the Pod is currently running on. This forces Kubernetes to move the Pod to another node once we trigger a restart. In our examples, the Hello message tells us that the Pod was started on <code>n1.example.com</code>, so this is the node we disable. Replace the name with your own node name.</p> <pre><code>$ kubectl cordon n1.example.com\nnode/n1.example.com cordoned\n</code></pre> <p>Now, we can trigger a new rollout of the deployment. Since we disabled scheduling <code>n1.example.com</code>, another node will have to take over our Pod.</p> <pre><code>$ kubectl rollout restart deploy/volume-logger\ndeployment.apps/volume-logger restarted\n$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-5db9dd7b87-lps2f condition met\n$ kubectl get pods -owide\nNAME                             READY   STATUS    RESTARTS   AGE   IP            NODE             NOMINATED NODE   READINESS GATES\nvolume-logger-5db9dd7b87-lps2f   1/1     Running   0          26s   10.125.97.9   n2.example.com   &lt;none&gt;           &lt;none&gt;\n</code></pre> <p>As expected, the Pod is now running on a different node, in this case on <code>n2.example.com</code>.</p> <p>Now, we can verify that the message from the original pod is still present:</p> <pre><code>$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-84dd47f4cb-trh4l, running on n1.example.com, started at Fri Feb  3 08:53:47 UTC 2023\nHello from volume-logger-5db9dd7b87-lps2f, running on n2.example.com, started at Fri Feb  3 08:55:42 UTC 2023\n</code></pre> <p>As expected, we still see the message from <code>n1.example.com</code>, as well as the message from the new Pod on <code>n2.example.com</code>.</p> <p>We can also see that LINSTOR now shows the volume as <code>InUse</code> on the new node:</p> <pre><code>$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor resource list-volumes\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n| Node           | Resource                                 | StoragePool | VolNr | MinorNr | DeviceName    | Allocated | InUse  |    State |\n|===========================================================================================================================================|\n| n1.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 | 16.91 MiB | Unused | UpToDate |\n| n2.example.com | pvc-dbe422ac-c5ae-4786-a624-74d2be8a262d | pool1       |     0 |    1000 | /dev/drbd1000 |   952 KiB | InUse  | UpToDate |\n+-------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre> <p>You have now successfully created a replicated volume and verified that the data is accessible from multiple nodes.</p>"},{"location":"tutorial/replicated-volumes/#resetting-the-disabled-node","title":"Resetting the Disabled Node","text":"<p>Now that we have verified replication works, we can reset the disabled node:</p> <pre><code>$ kubectl uncordon n1.example.com\nnode/n1.example.com uncordoned\n</code></pre>"},{"location":"tutorial/snapshots/","title":"Creating and Restoring From Snapshots","text":"<p>Learn how to create snapshots of your data, and how you can restore the data in a snapshot.</p> <p>Snapshots create a copy of the volume content at a particular point in time. This copy remains untouched when you make modifications to the volume content. This, for example, enables you to create backups of your data before performing modifications or deletion on your data.</p> <p>Since a backup is useless, unless you have a way to restore it, this tutorial will teach you both how to create a snapshot, and how to restore in the case of accidental deletion of your data.</p>"},{"location":"tutorial/snapshots/#prerequisites","title":"Prerequisites","text":"<ul> <li>An installed and configured Piraeus Datastore. Learn how to get started in our introduction tutorial</li> <li>A storage pool supporting snapshots. LINSTOR supports snapshots for <code>LVM_THIN</code>, <code>FILE_THIN</code>, <code>ZFS</code> and <code>ZFS_THIN</code> pools.   If you followed the introduction tutorial, you are using the supported <code>FILE_THIN</code> pool.</li> <li>A cluster with <code>snapshot-controller</code> deployed. To check if   it is already deployed, try running:   <pre><code>$ kubectl api-resources --api-group=snapshot.storage.k8s.io -oname\nvolumesnapshotclasses.snapshot.storage.k8s.io\nvolumesnapshotcontents.snapshot.storage.k8s.io\nvolumesnapshots.snapshot.storage.k8s.io\n</code></pre>   If your output looks like above, you are good to go.   If your output is empty, you should deploy a snapshot controller. You can quickly deploy it by using:   <pre><code>kubectl apply -k https://github.com/kubernetes-csi/external-snapshotter//client/config/crd\nkubectl apply -k https://github.com/kubernetes-csi/external-snapshotter//deploy/kubernetes/snapshot-controller\n</code></pre></li> </ul>"},{"location":"tutorial/snapshots/#creating-an-example-workload","title":"Creating an Example Workload","text":"<p>We will be using the same workload as in the replicated volumes tutorial. This workload will save the Pods name, the node it is running on, and a timestamp to our volume. By logging this information to our volume, we can easily keep track of our data.</p> <p>First, we create our <code>StorageClass</code>, <code>PersistentVolumeClaim</code> and <code>Deployment</code>:</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\n---\napiVersion: storage.k8s.io/v1\nkind: StorageClass\nmetadata:\n  name: piraeus-storage\nprovisioner: linstor.csi.linbit.com\nallowVolumeExpansion: true\nvolumeBindingMode: WaitForFirstConsumer\nparameters:\n  linstor.csi.linbit.com/storagePool: pool1\n---\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: data-volume\nspec:\n  storageClassName: piraeus-storage\n  resources:\n    requests:\n      storage: 1Gi\n  accessModes:\n    - ReadWriteOnce\n---\napiVersion: apps/v1\nkind: Deployment\nmetadata:\n  name: volume-logger\nspec:\n  selector:\n    matchLabels:\n      app.kubernetes.io/name: volume-logger\n  strategy:\n    type: Recreate\n  template:\n    metadata:\n      labels:\n        app.kubernetes.io/name: volume-logger\n    spec:\n      terminationGracePeriodSeconds: 0\n      containers:\n        - name: volume-logger\n          image: busybox\n          args:\n            - sh\n            - -c\n            - |\n              echo \"Hello from \\$HOSTNAME, running on \\$NODENAME, started at \\$(date)\" &gt;&gt; /volume/hello\n              # We use this to keep the Pod running\n              tail -f /dev/null\n          env:\n            - name: NODENAME\n              valueFrom:\n                fieldRef:\n                  fieldPath: spec.nodeName\n          volumeMounts:\n            - mountPath: /volume\n              name: data-volume\n      volumes:\n        - name: data-volume\n          persistentVolumeClaim:\n            claimName: data-volume\nEOF\n</code></pre> <p>Then, we wait for the Pod to start, and verify that the expected information was logged to our volume:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-cbcd897b7-jrmks condition met\n$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-cbcd897b7-jrmks, running on n3.example.com, started at Mon Feb 13 15:32:46 UTC 2023\n</code></pre>"},{"location":"tutorial/snapshots/#creating-a-snapshot","title":"Creating a Snapshot","text":"<p>Creating a snapshot requires the creation of a <code>SnapshotClass</code> first. The <code>SnapshotClass</code> specifies our <code>linstor.csi.linbit.com</code> provisioner, and sets the clean-up policy for our snapshots to <code>Delete</code>, meaning deleting the Kubernetes resources will also delete the snapshots in LINSTOR\u00ae.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: snapshot.storage.k8s.io/v1\nkind: VolumeSnapshotClass\nmetadata:\n  name: piraeus-snapshots\ndriver: linstor.csi.linbit.com\ndeletionPolicy: Delete\nEOF\n</code></pre> <p>Next, we will request the creation of a snapshot using a <code>VolumeSnapshot</code> resource. The <code>VolumeSnapshot</code> resource references the <code>PersistentVolumeClaim</code> resource we created initially, as well as our newly created <code>VolumeSnapshotClass</code>.</p> <pre><code>$ kubectl apply -f - &lt;&lt;EOF\napiVersion: snapshot.storage.k8s.io/v1\nkind: VolumeSnapshot\nmetadata:\n  name: data-volume-snapshot-1\nspec:\n  volumeSnapshotClassName: piraeus-snapshots\n  source:\n    persistentVolumeClaimName: data-volume\nEOF\n</code></pre> <p>Now, we need to wait for the snapshot to be created. We can then also verify its creation in LINSTOR:</p> <pre><code>$ kubectl wait volumesnapshot --for=jsonpath='{.status.readyToUse}'=true data-volume-snapshot-1\nvolumesnapshot.snapshot.storage.k8s.io/data-volume-snapshot-1 condition met\n$ kubectl get volumesnapshot data-volume-snapshot-1\nNAME                     READYTOUSE   SOURCEPVC     SOURCESNAPSHOTCONTENT   RESTORESIZE   SNAPSHOTCLASS       SNAPSHOTCONTENT                                    CREATIONTIME   AGE\ndata-volume-snapshot-1   true         data-volume                           1Gi           piraeus-snapshots   snapcontent-a8757c1d-cd37-42d2-9557-a24b1222d118   15s            15s\n$ kubectl -n piraeus-datastore exec deploy/linstor-controller -- linstor snapshot list\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n| ResourceName                             | SnapshotName                                  | NodeNames      | Volumes  | CreatedOn           | State      |\n|=========================================================================================================================================================|\n| pvc-9c04b307-d22d-454f-8f24-ed5837fe4426 | snapshot-a8757c1d-cd37-42d2-9557-a24b1222d118 | n3.example.com | 0: 1 GiB | 2023-02-13 15:36:18 | Successful |\n+---------------------------------------------------------------------------------------------------------------------------------------------------------+\n</code></pre>"},{"location":"tutorial/snapshots/#modifying-the-data","title":"Modifying the Data","text":"<p>Now we want to simulate a situation where we accidentally delete some important data. The important data in our example workload is the log of Pod name, Node name and timestamp. We will manually delete the file on the volume to simulate accidental removal of an important file on a persistent volume:</p> <pre><code>$ kubectl exec deploy/volume-logger -- rm /volume/hello\n$ kubectl exec deploy/volume-logger -- cat /volume/hello\ncat: can't open '/volume/hello': No such file or directory\ncommand terminated with exit code 1\n</code></pre>"},{"location":"tutorial/snapshots/#restoring-from-a-snapshot","title":"Restoring From a Snapshot","text":"<p>This is the exact situation where snapshots can come in handy. Since we created a snapshot before we made removed the file, we can create a new volume to recover our data. We will be replacing the existing <code>data-volume</code> with a new version based on the snapshot.</p> <p>First, we will stop the Deployment by scaling it down to zero Pods, so that it does not interfere with our next steps:</p> <pre><code>$ kubectl scale deploy/volume-logger --replicas=0\ndeployment.apps \"volume-logger\" deleted\n$ kubectl rollout status deploy/volume-logger\ndeployment \"volume-logger\" successfully rolled out\n</code></pre> <p>Next, we will also remove the <code>PersistentVolumeClaim</code>. We still have the snapshot which contains the data we want to restore, so we can safely remove the volume.</p> <pre><code>$ kubectl delete pvc/data-volume\npersistentvolumeclaim \"data-volume\" deleted\n</code></pre> <p>Now, we will create a new <code>PersistentVolumeClaim</code>, referencing our snapshot. This will create a volume, using the data from the snapshot.</p> <pre><code>kubectl apply -f - &lt;&lt;EOF\napiVersion: v1\nkind: PersistentVolumeClaim\nmetadata:\n  name: data-volume\nspec:\n  storageClassName: piraeus-storage\n  resources:\n    requests:\n      storage: 1Gi\n  dataSource:\n    apiGroup: snapshot.storage.k8s.io\n    kind: VolumeSnapshot\n    name: data-volume-snapshot-1\n  accessModes:\n    - ReadWriteOnce\nEOF\n</code></pre> <p>Since we named this new volume <code>data-volume</code>, we can just scale up our Deployment again, and the new Pod will start using the restored volume:</p> <pre><code>$ kubectl scale deploy/volume-logger --replicas=1\ndeployment.apps/volume-logger scaled\n</code></pre> <p>After the Pod started, we can once again verify the content of our volume:</p> <pre><code>$ kubectl wait pod --for=condition=Ready -l app.kubernetes.io/name=volume-logger\npod/volume-logger-cbcd897b7-5qjbz condition met\n$ kubectl exec deploy/volume-logger -- cat /volume/hello\nHello from volume-logger-cbcd897b7-jrmks, running on n3.example.com, started at Mon Feb 13 15:32:46 UTC 2023\nHello from volume-logger-cbcd897b7-gr6hh, running on n3.example.com, started at Mon Feb 13 15:42:17 UTC 2023\n</code></pre> <p>You have now successfully created a snapshot, and used it to back up and restore a volume after accidental deletion.</p>"},{"location":"upgrade/","title":"General notes","text":"<p>During the upgrade process, provisioning of volumes and attach/detach operations might not work. Existing volumes and volumes already in use by a pod will continue to work without interruption.</p> <p>To upgrade, apply the resource of the latest release. Use the same method that was used to create the initial deployment (<code>kubectl</code> vs <code>helm</code>). There is no need to change existing <code>LinstorCluster</code>, <code>LinstorSatelliteConfiguration</code> or <code>LinstorNodeConnection</code> resources.</p> <p>To upgrade to the latest release using <code>kubectl</code>, run the following commands:</p> <pre><code>$ kubectl apply --server-side -k \"https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.7.1\"\n$ kubectl wait pod --for=condition=Ready -n piraeus-datastore --all\n</code></pre>"},{"location":"upgrade/#upgrades-from-v26-to-v27","title":"Upgrades from v2.6 to v2.7","text":"<p>Generally, no special steps required.</p> <p>LINSTOR Satellites now try to automatically detect the LVM configuration on the host. Any patch targeting the Satellites /etc/lvm/lvm.conf file may need to be adapted.</p>"},{"location":"upgrade/#upgrades-from-v25-to-v26","title":"Upgrades from v2.5 to v2.6","text":"<p>No special steps required.</p>"},{"location":"upgrade/#upgrades-from-v24-to-v25","title":"Upgrades from v2.4 to v2.5","text":"<p>No special steps required.</p>"},{"location":"upgrade/#upgrades-from-v23-to-v24","title":"Upgrades from v2.3 to v2.4","text":"<p>Generally, no special steps required.</p> <p>LINSTOR Satellites are now managed via DaemonSet resources. Any patch targeting a <code>satellite</code> Pod resources is automatically converted to the equivalent DaemonSet resource patch. In the Pod list, you will see these Pods using a new <code>linstor-satellite</code> prefix.</p>"},{"location":"upgrade/#upgrades-from-v22-to-v23","title":"Upgrades from v2.2 to v2.3","text":"<p>Removed the <code>NetworkPolicy</code> resource from default deployment. It can be reapplied as a separate step.</p>"},{"location":"upgrade/#upgrades-from-v21-to-v22","title":"Upgrades from v2.1 to v2.2","text":"<p>Removed the dependency on cert-manager for the initial deployment. To clean up an existing <code>Certificate</code> resource, run the following commands:</p> <pre><code>$ kubectl delete certificate -n piraeus-datastore piraeus-operator-serving-cert\n</code></pre>"},{"location":"upgrade/#upgrades-from-v20-to-v21","title":"Upgrades from v2.0 to v2.1","text":"<p>No special steps required.</p>"},{"location":"upgrade/#upgrades-from-v1-to-v2","title":"Upgrades from v1 to v2","text":"<p>Please follow the specialized upgrade guides.</p>"},{"location":"upgrade/#upgrade-from-v19-to-v110","title":"Upgrade from v1.9 to v1.10","text":"<p>If you want to share DRBD configuration directories with the host, please update the CRDs before upgrading using helm:</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre>"},{"location":"upgrade/#upgrade-from-v18-to-v19","title":"Upgrade from v1.8 to v1.9","text":"<p>If you want to protect metrics endpoints, take a look on guide on enabling rbac-proxy sidecars.</p> <p>We've also disabled the <code>haController</code> component in our chart. The replacement is available from artifacthub.io, containing much needed improvements in robustness and fail-over speed. If you want to still use the old version, set <code>haController.enabled=true</code>.</p>"},{"location":"upgrade/#upgrade-from-v17-to-v18","title":"Upgrade from v1.7 to v1.8","text":"<p>If you need to set the number of worker threads, or you need to set the log level of LINSTOR components, please update the CRDs before upgrading using helm:</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre> <p>In case if you have SSL enabled installation, you need to regenerate your certificates in PEM format. Read the guide on securing the deployment and repeat the described steps.</p>"},{"location":"upgrade/#upgrade-from-v16-to-v17","title":"Upgrade from v1.6 to v1.7","text":"<p>Node labels are now automatically applied to LINSTOR satellites as \"Auxiliary Properties\". That means you can reuse your existing Kubernetes Topology information (for example <code>topology.kubernetes.io/zone</code> labels) when scheduling volumes using the <code>replicasOnSame</code> and <code>replicasOnDifferent</code> settings. However, this also means that the Operator will delete any existing auxiliary properties that were already applied. To apply auxiliary properties to satellites, you have to apply a label to the Kubernetes node object.</p>"},{"location":"upgrade/#upgrade-from-v15-to-v16","title":"Upgrade from v1.5 to v1.6","text":"<p>The <code>csi-snapshotter</code> subchart was removed from this repository. Users who relied on it for their snapshot support should switch to the seperate charts provided by the Piraeus team on artifacthub.io The new charts also include notes on how to upgrade to newer CRD versions.</p> <p>To support the new <code>csi.kubeletPath</code> option an update to the LinstorCSIDriver CRD is required:</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre>"},{"location":"upgrade/#upgrade-from-v14-to-v15","title":"Upgrade from v1.4 to v1.5","text":"<p>To make use of the new <code>monitoringImage</code> value in the LinstorSatelliteSet CRD, you need to replace the existing CRDs before running the upgrade. If the CRDs are not upgraded, the operator will not deploy the monitoring container alongside the satellites.</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre> <p>Then run the upgrade:</p> <pre><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;\n</code></pre>"},{"location":"upgrade/#upgrade-from-v13-to-v14","title":"Upgrade from v1.3 to v1.4","text":"<p>No special steps required, unless using the newly introduced <code>additionalEnv</code> and <code>additionalProperties</code> overrides.</p> <p>If you plan to use the new overrides, replace the CustomResourceDefinitions before running the upgrade</p> <pre><code>$ kubectl replace -f ./charts/piraeus/crds\n</code></pre> <p>Then run the upgrade:</p> <pre><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;\n</code></pre>"},{"location":"upgrade/#upgrade-from-v12-to-v13","title":"Upgrade from v1.2 to v1.3","text":"<p>No special steps required. After checking out the new repo, run a simple helm upgrade:</p> <pre><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;\n</code></pre>"},{"location":"upgrade/#upgrade-from-v11-to-v12","title":"Upgrade from v1.1 to v1.2","text":"<p>Piraeus v1.2 is supported on Kubernetes 1.17+. If you are using an older Kubernetes distribution, you may need to change the default settings (for example the CSI provisioner)</p> <p>To start the upgrade process, ensure you have a backup of the LINSTOR Controller database. If you are using the etcd deployment included in Piraeus, you can create a backup using:</p> <pre><code>kubectl exec piraeus-op-etcd-0 -- etcdctl snapshot save /tmp/save.db\nkubectl cp piraeus-op-etcd-0:/tmp/save.db save.db\n</code></pre> <p>Now you can start the upgrade process. Simply run <code>helm upgrade piraeus-op ./charts/piraeus</code>. If you installed Piraeus with customization, pass the same options you used for <code>helm install</code> to <code>helm upgrade</code>. This will cause the operator pod to be re-created and shortly after all other Piraeus pods.</p> <p>There is a known issue when updating the CSI components: the pods will not be updated to the newest image and the <code>errors</code> section of the LinstorCSIDrivers resource shows an error updating the DaemonSet. In this case, manually delete <code>deployment/piraeus-op-csi-controller</code> and <code>daemonset/piraeus-op-csi-node</code>. They will be re-created by the operator.</p> <p>After a short wait, all pods should be running and ready. Check that no errors are listed in the status section of LinstorControllers, LinstorSatelliteSets and LinstorCSIDrivers.</p>"},{"location":"upgrade/#upgrade-from-v10-to-v11","title":"Upgrade from v1.0 to v1.1","text":"<ul> <li>The LINSTOR controller image given in <code>operator.controller.controllerImage</code> has to have   its entrypoint set to <code>k8s-await-election v0.2.0</code>   or newer. All images starting with <code>piraeus-server:v1.8.0</code> meet this requirement.</li> </ul> <p>Older images will not work, as the <code>Service</code> will not automatically pick up on the active pod.</p> <p>To upgrade, first update the deployed LINSTOR image to a compatible version, then upgrade the   operator.</p>"},{"location":"upgrade/#upgrade-to-v10","title":"Upgrade to v1.0","text":"<p>Upgrades from v0.* versions to v1.0 are best-effort only. The following guide assumes an upgrade from v0.5.0.</p> <ul> <li> <p>CRDs have been updated and set to version <code>v1</code>. You need to replace any existing CRDs with these new ones:   <pre><code>kubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcontrollers_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcsidrivers_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorsatellitesets_crd.yaml\n</code></pre></p> </li> <li> <p>Renamed <code>LinstorNodeSet</code> to <code>LinstorSatelliteSet</code>. This brings the operator in line with other LINSTOR resources.   Existing <code>LinstorNodeSet</code> resources will automatically be migrated to <code>LinstorSatelliteSet</code>. The old resources will   not be deleted. You can verify that migration was successful by running the following command:   <pre><code>$ kubectl get linstornodesets.piraeus.linbit.com -o=jsonpath='{range .items[*]}{.metadata.name}{\"\\t\"}{.status.ResourceMigrated}{\"\\t\"}{.status.DependantsMigrated}{\"\\n\"}{end}'\npiraeus-op-ns true    true\n</code></pre>   If both values are <code>true</code>, migration was successful. The old resource can be removed after migration.</p> </li> <li> <p>Renamed <code>LinstorControllerSet</code> to <code>LinstorController</code>. The old name implied the existence of multiple (separate)   controllers. Existing <code>LinstorControllerSet</code> resources will automatically be migrated to <code>LinstorController</code>. The old   resources will not be deleted. You can verify that migration was successful by running the following command:   <pre><code>$ kubectl get linstorcontrollersets.piraeus.linbit.com -o=jsonpath='{range .items[*]}{.metadata.name}{\"\\t\"}{.status.ResourceMigrated}{\"\\t\"}{.status.DependantsMigrated}{\"\\n\"}{end}'\npiraeus-op-cs true    true\n</code></pre>   If both values are <code>true</code>, migration was successful. The old resource can be removed after migration.</p> </li> <li> <p>Along with the CRDs, Helm settings changed too:</p> <ul> <li><code>operator.controllerSet</code> to <code>operator.controller</code></li> <li><code>operator.nodeSet</code> to <code>operator.satelliteSet</code>   If old settings are used, Helm will return an error.</li> </ul> </li> <li> <p>Node scheduling no longer relies on <code>linstor.linbit.com/piraeus-node</code> labels. Instead, all CRDs support   setting pod affinity and tolerations.   In detail:</p> <ul> <li><code>linstorcsidrivers</code> gained 4 new resource keys, with no change in default behaviour:<ul> <li><code>nodeAffinity</code> affinity passed to the csi nodes</li> <li><code>nodeTolerations</code> tolerations passed to the csi nodes</li> <li><code>controllerAffinity</code> affinity passed to the csi controller</li> <li><code>controllerTolerations</code> tolerations passed to the csi controller</li> </ul> </li> <li><code>linstorcontrollerset</code> gained 2 new resource keys, with no change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> <li><code>linstornodeset</code> gained 2 new resource keys, with change in default behaviour:<ul> <li><code>affinity</code> affinity passed to the linstor controller pod</li> <li><code>tolerations</code> tolerations passed to the linstor controller pod</li> </ul> </li> </ul> <p>Previously, linstor satellite pods required nodes marked with <code>linstor.linbit.com/piraeus-node=true</code>. The new   default value does not place this restriction on nodes. To restore the old behaviour, set the following affinity:   <pre><code>affinity:\n  nodeAffinity:\n    requiredDuringSchedulingIgnoredDuringExecution:\n      nodeSelectorTerms:\n      - matchExpressions:\n        - key: linstor.linbit.com/piraeus-node\n          operator: In\n          values:\n          - \"true\"\n</code></pre></p> </li> <li> <p>Other changed helm settings:   <code>drbdKernelModuleInjectionMode</code>: renamed to <code>kernelModuleInjectionMode</code> <code>kernelModImage</code>: renamed to <code>kernelModuleInjectionImage</code>   If old settings are used, Helm will return an error.</p> </li> </ul>"},{"location":"upgrade/#upgrade-between-v0-versions","title":"Upgrade between v0.* versions","text":"<p>While the API version was <code>v1alpha1</code>, this project did not maintain stability of or provide conversion of the Custom Resource Definitions.</p> <p>If you are using the Helm deployment, you may find that upgrades fail with errors similar to the following:</p> <pre><code>UPGRADE FAILED: cannot patch \"piraeus-op-cs\" with kind LinstorController: LinstorController.piraeus.linbit.com \"piraeus-op-cs\" is invalid: spec.etcdURL: Required value\n</code></pre> <p>The simplest solution in this case is to manually replace the CRD:</p> <pre><code>kubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcsidrivers_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorsatellitesets_crd.yaml\nkubectl replace -f charts/piraeus/crds/piraeus.linbit.com_linstorcontrollers_crd.yaml\n</code></pre> <p>Then continue with the Helm upgrade. Values that are lost during the replacement will be set again by Helm.</p>"},{"location":"upgrade/migration/","title":"Upgrading Piraeus Operator from Version 1 to Version 2","text":"<p>The following document guides you through the upgrade process for Piraeus Operator from version 1 (\"v1\") to version 2 (\"v2\").</p> <p>Piraeus Operator v2 offers improved convenience and customization. This however made it necessary to make significant changes to the way Piraeus Operator manages Piraeus Datastore. As such, upgrading from v1 to v2 is a procedure requiring manual oversight.</p> <p>Upgrading Piraeus Operator is done in four steps:</p> <ul> <li>Step 1: (Optional) Migrate the LINSTOR database to use the <code>k8s</code> backend.</li> <li>Step 2: Collect information about the current deployment.</li> <li>Step 3: Remove the Piraeus Operator v1 deployment, keeping existing volumes untouched.</li> <li>Step 4: Deploy Piraeus Operator v2 using the information gathered in step 2.</li> </ul>"},{"location":"upgrade/migration/#prerequisites","title":"Prerequisites","text":"<p>This guide assumes:</p> <ul> <li>You used Helm to create the original deployment and are familiar with upgrading Helm deployments.</li> <li>Your Piraeus Datastore deployment is up-to-date with the latest v1 release. Check the releases here.</li> <li>You have the following command line tools available:</li> <li><code>kubectl</code></li> <li><code>helm</code></li> <li><code>jq</code></li> <li>You are familiar with the <code>linstor</code> command line utility, specifically to verify the cluster state.</li> </ul>"},{"location":"upgrade/migration/#key-changes-between-operator-v1-and-v2","title":"Key Changes Between Operator V1 and V2","text":""},{"location":"upgrade/migration/#administrative-changes","title":"Administrative Changes","text":"<ul> <li>The resources <code>LinstorController</code>, <code>LinstorSatelliteSet</code> and <code>LinstorCSIDriver</code> have been replaced by   <code>LinstorCluster</code> and   <code>LinstorSatelliteConfgiuration</code>.</li> <li>The default deployment runs the LINSTOR Satellite in the container network.   The migration script will propose changing to the host network.</li> </ul>"},{"location":"upgrade/migration/#operational-changes","title":"Operational Changes","text":"<ul> <li>In Operator v1, all labels on the Kubernetes node resource were replicated on the satellite, making them usable in the   <code>replicasOnSame</code> and <code>replicasOnDifferent</code> parameters on the storage class. In Operator v2, only the following   labels are automatically synchronized.</li> <li><code>kubernetes.io/hostname</code></li> <li><code>topology.kubernetes.io/region</code></li> <li><code>topology.kubernetes.io/zone</code>   Use <code>LinstorSatelliteConfiguration.spec.properties</code>   to synchronize additional labels.</li> <li>The following settings are applied by Operator v2 cluster-wide:</li> <li>DrbdOptions/Net/rr-conflict: retry-connect</li> <li>DrbdOptions/Resource/on-suspended-primary-outdated: force-secondary</li> <li>DrbdOptions/Resource/on-no-data-accessible: suspend-io</li> <li>DrbdOptions/auto-quorum: suspend-io</li> <li>Operator v2 also includes a High-Availability Controller   deployment to prevent stuck nodes caused by suspended DRBD devices.</li> </ul>"},{"location":"upgrade/migration/1-migrate-database/","title":"Migrating the LINSTOR Controller Database to Use the <code>k8s</code> Backend","text":"<p>This document guides you through the process of migrating an existing LINSTOR\u00ae Cluster to use the <code>k8s</code> database backend.</p> <p>This is the optional first step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"upgrade/migration/1-migrate-database/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> </ul>"},{"location":"upgrade/migration/1-migrate-database/#when-to-migrate-the-linstor-controller-database-to-the-k8s-backend","title":"When to Migrate the LINSTOR Controller Database to the <code>k8s</code> Backend","text":"<p>LINSTOR can use different database backends to store important state, such as the available volumes and where they are deployed. The available backends are:</p> <ul> <li>An H2 database stored in a local file on the controller.</li> <li>A compatible database server, such as MySQL or PostgreSQL.</li> <li>An etcd cluster.</li> <li>An <code>k8s</code> backend, using Custom Resources to store the cluster state directly in the Kubernetes API.</li> </ul> <p>Of these backends, only the <code>k8s</code> backend works without any additional components when running in the Kubernetes cluster.</p> <p>Because the Piraeus Operator v1 is older than the LINSTOR <code>k8s</code> backend, the default for a long time was the use of a separate etcd cluster, deployed by default when using Piraeus Operator v1. Since then, etcd proved to be difficult to maintain, often requiring manual intervention.</p> <p>Because of this, consider migrating away from separate etcd cluster to using the <code>k8s</code> backend.</p> <p>If you already use one of the other backends, no migration is necessary. You can check the currently used backend of your LINSTOR cluster by running the following command:</p> <pre><code>$ kubectl exec deploy/piraeus-op-cs-controller -- cat /etc/linstor/linstor.toml\n[db]\n  connection_url = \"etcd://piraeus-op-etcd:2379\"\n</code></pre> <p>If the <code>connection_url</code> value starts with <code>etcd://</code> you are using the etcd backend and should consider migrating.</p>"},{"location":"upgrade/migration/1-migrate-database/#migrating-the-linstor-controller-database","title":"Migrating the LINSTOR Controller Database","text":"<p>During the migration, the LINSTOR Controller needs to be stopped. This means that provisioning and deletion of volumes will not work for the duration of the migration. Existing volumes will continue working normally.</p>"},{"location":"upgrade/migration/1-migrate-database/#1-stop-the-linstor-controller","title":"1. Stop the LINSTOR Controller","text":"<p>To prevent unwanted modifications to the database during the migration, you need to stop the LINSTOR Controller. To stop the LINSTOR Controller, set the expected replicas for the controller to zero.</p> <p>First, find the currently deployed Piraeus Datastore release. For this guide, it is 1.10.8:</p> <pre><code>$ helm list\nNAME        NAMESPACE          REVISION  UPDATED                                 STATUS    CHART           APP VERSION\npiraeus-op  piraeus-datastore  1         2023-11-07 10:30:44.184389038 +0100 CET deployed  piraeus-1.10.8  1.10.8\n</code></pre> <p>Then change the deployment to deploy no replicas for the LINSTOR Controller. Ensure to check out the chart version currently deployed, so that no accidental upgrade happens:</p> <pre><code>$ git checkout v1.10.8\n$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set operator.controller.replicas=0\n$ kubectl rollout status deploy/piraeus-op-cs-controller -w\ndeployment \"piraeus-op-cs-controller\" successfully rolled out\n</code></pre>"},{"location":"upgrade/migration/1-migrate-database/#2-prepare-a-pod-for-running-the-migration","title":"2. Prepare a Pod for Running the Migration","text":"<p>To run the migration, you need access to the <code>linstor-database</code> tool, which comes preinstalled with the LINSTOR Controller image. The following command displays the LINSTOR Controller image, the name of the ConfigMap storing the LINSTOR Configuration, and the service account for LINSTOR Controller. Take note of them, as they will be used for the migration Pod.</p> <pre><code>$ kubectl get deploy/piraeus-op-cs-controller --output=jsonpath='IMAGE={$.spec.template.spec.containers[?(@.name==\"linstor-controller\")].image}{\"\\n\"}CONFIG_MAP={$.spec.template.spec.volumes[?(@.name==\"linstor-conf\")].configMap.name}{\"\\n\"}SERVICE_ACCOUNT={$.spec.template.spec.serviceAccountName}{\"\\n\"}'\nIMAGE=quay.io/piraeusdatastore/piraeus-server:v1.24.2\nCONFIG_MAP=piraeus-op-cs-controller-config\nSERVICE_ACCOUNT=linstor-controller\n</code></pre> <p>Using the information from the LINSTOR Controller deployment, create a Pod used during the migration process. Replace <code>$IMAGE</code>, <code>$CONFIG_MAP</code> and <code>$SERVICE_ACCOUNT</code> with the appropriate values.</p> <pre><code>apiVersion: v1\nkind: Pod\nmetadata:\n  name: linstor-database-migration\nspec:\n  serviceAccountName: $SERVICE_ACCOUNT\n  containers:\n    - name: backup\n      image: $IMAGE\n      command:\n        - /bin/bash\n        - -c\n        - \"sleep infinity\"\n      volumeMounts:\n        - name: linstor-conf\n          mountPath: /etc/linstor\n          readOnly: true\n        - name: backup\n          mountPath: /backup\n        - name: logs\n          mountPath: /logs\n  volumes:\n    - name: backup\n      emptyDir: {}\n    - name: logs\n      emptyDir: {}\n    - name: linstor-conf\n      configMap:\n        name: $CONFIG_MAP\n</code></pre>"},{"location":"upgrade/migration/1-migrate-database/#3-create-a-database-backup","title":"3. Create a Database Backup","text":"<p>Using the newly created migration Pod, create a database backup using the <code>linstor-database</code> tool.</p> <pre><code>$ kubectl exec linstor-database-migration -- /usr/share/linstor-server/bin/linstor-database export-db -c /etc/linstor /backup/backup-before-migration.json\nLoading configuration file \"/etc/linstor/linstor.toml\"\n15:22:55.684 [main] INFO LINSTOR/linstor-db -- SYSTEM - ErrorReporter DB first time init.\n15:22:55.685 [main] INFO LINSTOR/linstor-db -- SYSTEM - Log directory set to: './logs'\n15:22:56.417 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\"\n15:22:56.418 [main] INFO LINSTOR/linstor-db -- SYSTEM - Extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\" is not installed\n15:22:56.418 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\"\n15:22:56.426 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\" was successful\n15:22:56.427 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\"\n15:22:56.429 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\" was successful\n15:22:57.666 [main] INFO LINSTOR/linstor-db -- SYSTEM - Initializing the etcd database\n15:22:57.667 [main] INFO LINSTOR/linstor-db -- SYSTEM - etcd connection URL is \"etcd://piraeus-op-etcd:2379\"\n15:22:59.480 [main] INFO LINSTOR/linstor-db -- SYSTEM - Export finished\n</code></pre> <p>Then, copy the just created backup to permanent storage, so that it is not lost should the migration pod restart:</p> <pre><code>$ kubectl cp linstor-database-migration:/backup/backup-before-migration.json backup-before-migration.json\n</code></pre>"},{"location":"upgrade/migration/1-migrate-database/#4-update-the-linstor-configuration-to-point-to-the-new-database-backend","title":"4. Update the LINSTOR Configuration to Point to the New Database Backend","text":"<p>After creating and storing the backup it is safe to change the LINSTOR configuration. This is done by running another <code>helm upgrade</code>, changing the database configuration for the LINSTOR Controller. Once again, ensure that you apply the chart version currently deployed, so that no accidental upgrade happens:</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set operator.controller.dbConnectionURL=k8s\n</code></pre> <p>This will also change the configuration in the <code>linstor-database-migration</code> Pod, but it might need some time to propagate. Eventually, you will see the <code>k8s</code> database connection:</p> <pre><code>$ kubectl exec linstor-database-migration -- cat /etc/linstor/linstor.toml\n[db]\n  connection_url = \"k8s\"\n</code></pre>"},{"location":"upgrade/migration/1-migrate-database/#5-import-the-database-from-the-backup","title":"5. Import the Database from the Backup","text":"<p>After changing the configuration, you can again use the <code>linstor-database</code> tool to restore the database backup to the new backend.</p> <pre><code>$ kubectl exec linstor-database-migration -- /usr/share/linstor-server/bin/linstor-database import-db -c /etc/linstor /backup/backup-before-migration.json\nLoading configuration file \"/etc/linstor/linstor.toml\"\n15:39:41.270 [main] INFO LINSTOR/linstor-db -- SYSTEM - ErrorReporter DB version 1 found.\n15:39:41.272 [main] INFO LINSTOR/linstor-db -- SYSTEM - Log directory set to: './logs'\n15:39:41.848 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\"\n15:39:41.849 [main] INFO LINSTOR/linstor-db -- SYSTEM - Extension module \"com.linbit.linstor.modularcrypto.FipsCryptoModule\" is not installed\n15:39:41.850 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\"\n15:39:41.858 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.modularcrypto.JclCryptoModule\" was successful\n15:39:41.859 [main] INFO LINSTOR/linstor-db -- SYSTEM - Attempting dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\"\n15:39:41.860 [main] INFO LINSTOR/linstor-db -- SYSTEM - Dynamic load of extension module \"com.linbit.linstor.spacetracking.ControllerSpaceTrackingModule\" was successful\n15:39:43.307 [main] INFO LINSTOR/linstor-db -- SYSTEM - Initializing the k8s crd database connector\n15:39:43.307 [main] INFO LINSTOR/linstor-db -- SYSTEM - Kubernetes-CRD connection URL is \"k8s\"\n15:40:22.418 [main] INFO LINSTOR/linstor-db -- SYSTEM - Import finished\n</code></pre>"},{"location":"upgrade/migration/1-migrate-database/#6-start-the-linstor-controller","title":"6. Start the LINSTOR Controller","text":"<p>Now that the new database backend is initialized, it is safe to start the LINSTOR Controller again. Simply change the number of replicas for the LINSTOR Controller back to the original value before starting the migration. Once again, ensure that you apply the chart version currently deployed, so that no accidental upgrade happens:</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set operator.controller.replicas=1\ndeployment \"piraeus-op-cs-controller\" successfully rolled out\n</code></pre> <p>Once the LINSTOR Controller is up and running, verify the state of your cluster: check all nodes and resource are in the expected state:</p> <pre><code>$ kubectl exec deploy/piraeus-op-cs-controller -- linstor node list\n$ kubectl exec deploy/piraeus-op-cs-controller -- linstor storage-pool list\n$ kubectl exec deploy/piraeus-op-cs-controller -- linstor resource list-volumes\n$ kubectl exec deploy/piraeus-op-cs-controller -- linstor error-reports list\n</code></pre>"},{"location":"upgrade/migration/1-migrate-database/#7-clean-up-migration-resources","title":"7. Clean up Migration Resources","text":"<p>After successful migration, you can clean up left over resources.</p> <p>First, you can remove the <code>linstor-database-migration</code> Pod:</p> <pre><code>$ kubectl delete pod linstor-database-migration\n</code></pre> <p>Then, you can also remove the etcd deployment by upgrading the helm deployment, setting <code>etcd.enabled=false</code>:</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --reuse-values --set etcd.enabled=false\n</code></pre>"},{"location":"upgrade/migration/2-collect-information/","title":"Collect Information before Performing the Upgrade","text":"<p>Before performing the upgrade and removing the old deployment, collect information on the state of your cluster. This ensures the upgraded deployment will have a compatible configuration.</p> <p>This is the second step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"upgrade/migration/2-collect-information/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> <li>Install <code>jq</code></li> </ul>"},{"location":"upgrade/migration/2-collect-information/#run-the-data-collection-script","title":"Run the Data Collection Script","text":"<p>To collect the necessary information for the migration, run the script provided at <code>docs/upgrade/migration/collect-operator-v1-information.sh</code>. You can run the script either from a checked out repository, or directly from GitHub:</p> <pre><code>$ curl --proto '=https' --tlsv1.2 -sSf \\\n  https://raw.githubusercontent.com/piraeusdatastore/piraeus-operator/v2/docs/upgrade/migration/collect-operator-v1-information.sh \\\n  | bash -s\n</code></pre> <p>The script will ask you if you want to keep modifications made with the deployed Piraeus Operator. For each modification, the script will show you the proposed change to the deployed resources and ask for confirmation.</p> <p>In addition, it will also inform you about values that cannot automatically be migrated, along with recommended actions should you need to keep the modification. The output looks like this:</p> <pre><code>Using kubectl context: kubernetes-admin@kubernetes\nFound LinstorControllers: [\"piraeus-cs\"]\nFound LinstorSatelliteSets: [\"piraeus-ns\"]\nFound LinstorCSIDrivers: [\"piraeus\"]\nFound additional environment variables passed to LINSTOR Controller\n--- Default resource\n+++ Updated resource\n@@ -143,6 +143,12 @@ kind: Deployment\n       - args:\n         - startController\n         env:\n+        - name: FOO\n+          value: bar\n+        - name: EXAMPLE\n+          valueFrom:\n+            fieldRef:\n+              fieldPath: status.podIP\n         - name: JAVA_OPTS\n           value: -Djdk.tls.acknowledgeCloseNotify=true\n         - name: K8S_AWAIT_ELECTION_ENABLED\nApply the patch (Y/n)? y\n...\n---------------------------------------------------------------------------------------------\n| After upgrading, apply the following resources. They have been saved to v2-resources.yaml |\n---------------------------------------------------------------------------------------------\n\napiVersion: piraeus.io/v1\nkind: LinstorCluster\nmetadata:\n  name: linstorcluster\nspec:\n  linstorPassphraseSecret: piraeus-passphrase\n  patches: []\n...\n</code></pre> <p>A copy of the identified resources is saved at <code>v2-resources.yaml</code>.</p>"},{"location":"upgrade/migration/2-collect-information/#collect-helm-generated-secrets","title":"Collect Helm-Generated Secrets","text":"<p>Helm automatically generates a passphrase for LINSTOR. Once LINSTOR is initialized with the passphrase, the LINSTOR Controller will not be able fully start without supplying the passphrase.</p> <p>To migrate the generated passphrase to Piraeus Operator v2, create a backup of the secret:</p> <pre><code>$ kubectl get secrets piraeus-op-passphrase -ogo-template='{{.data.MASTER_PASSPHRASE}}{{\"\\n\"}}'\nZVRxanl1cVBscXV1ZTk1cmEwVTk5b0ptd0F4OGFmWlVPUVA0NWNnUw==\n</code></pre> <p>Save the generated passphrase for later use.</p>"},{"location":"upgrade/migration/3-remove-operator-v1/","title":"Remove the Piraeus Operator v1 Deployment","text":"<p>Migrating to the new Piraeus Operator deployment requires temporarily removing the existing deployment.</p> <p>After this step no new volumes can be created and no existing volume can be attached or detached, until the new deployment is rolled out.</p> <p>This is the third step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"upgrade/migration/3-remove-operator-v1/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> </ul>"},{"location":"upgrade/migration/3-remove-operator-v1/#scale-down-the-operator-deployment","title":"Scale Down the Operator Deployment","text":"<p>To prevent modification of the existing cluster, scale down the existing Piraeus Operator deployment.</p> <pre><code>$ helm upgrade piraeus-op ./charts/piraeus --set operator.replicas=0\n$ kubectl rollout status -w deploy/piraeus-op-operator\ndeployment \"piraeus-op-operator\" successfully rolled out\n</code></pre>"},{"location":"upgrade/migration/3-remove-operator-v1/#remove-the-finalizers-from-the-piraeus-resources","title":"Remove the Finalizers from the Piraeus Resources","text":"<p>The Operator sets Finalizers on the resource it controls. This prevents the deletion of these resources when the Operator is not running. Remove the Finalizers by applying a patch:</p> <pre><code>$ kubectl patch linstorsatellitesets piraeus-op-ns --type merge --patch '{\"metadata\": {\"finalizers\": []}}'\nlinstorsatelliteset.piraeus.linbit.com/piraeus-op-ns patched\n$ kubectl patch linstorcontrollers piraeus-op-cs --type merge --patch '{\"metadata\": {\"finalizers\": []}}'\nlinstorcontroller.piraeus.linbit.com/piraeus-op-cs patched\n</code></pre>"},{"location":"upgrade/migration/3-remove-operator-v1/#remove-the-piraeus-resources","title":"Remove the Piraeus Resources","text":"<p>Having removed the Finalizers, you can delete the Piraeus Resources. This will stop the LINSTOR Cluster, and no new volumes can be created, and existing volumes will not attach or detach. Volumes already attached to a Pod will continue to replicate.</p> <pre><code>$ kubectl delete linstorcsidrivers/piraeus-op\n$ kubectl delete linstorsatellitesets/piraeus-op-ns\n$ kubectl delete linstorcontrollers/piraeus-op-cs\n</code></pre>"},{"location":"upgrade/migration/3-remove-operator-v1/#remove-the-piraeus-deployment","title":"Remove the Piraeus Deployment","text":"<p>As a last step, you can completely remove the helm deployment, deleting additional resources such as service accounts and RBAC resources. In addition, also clean up the Custom Resource Definitions:</p> <pre><code>$ helm uninstall piraeus-op\n$ kubectl delete crds linstorcsidrivers.piraeus.linbit.com linstorsatellitesets.piraeus.linbit.com linstorcontrollers.piraeus.linbit.com\n</code></pre>"},{"location":"upgrade/migration/3-remove-operator-v1/#optional-remove-additional-piraeus-components","title":"Optional: Remove additional Piraeus Components","text":"<p>If you have deployed additional components from Piraeus, such as the HA Controller or LINSTOR Affinity Controller, you will need to remove them, too. After completing the migration, you can install them again, if needed.</p> <pre><code>$ helm uninstall piraeus-ha-controller\n$ helm uninstall linstor-affinity-controller\n</code></pre>"},{"location":"upgrade/migration/4-install-operator-v2/","title":"Install Piraeus Operator v2","text":"<p>After removing the Piraeus Operator v1 deployment, you can install Piraeus Operator v2.</p> <p>You can either use the <code>kubectl</code> method to deploy Piraeus Operator, or alternatively deploy the Operator using Helm.</p> <p>This is the last step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2). Click here to get back to the overview.</p>"},{"location":"upgrade/migration/4-install-operator-v2/#prerequisites","title":"Prerequisites","text":"<ul> <li>Install <code>kubectl</code></li> <li>Install <code>helm</code></li> </ul>"},{"location":"upgrade/migration/4-install-operator-v2/#deploy-piraeus-operator-v2-using-kubectl","title":"Deploy Piraeus Operator v2 Using <code>kubectl</code>","text":"<p>You can use <code>kubectl</code> and the built-in <code>kustomize</code> feature to deploy Piraeus Operator v2.</p> <p>First, create a file named <code>kustomization.yaml</code>, referencing the latest Piraeus Operator release, and the namespace you which to deploy the Piraeus Operator in. The latest releases are available  on the release page.</p> <p>In the example below, the version is <code>v2.3.0</code>, and the namespace is <code>piraeus-datastore</code>.</p> <pre><code>apiVersion: kustomize.config.k8s.io/v1beta1\nkind: Kustomization\nresources:\n  - https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.3.0 # Change the version here\nnamespace: piraeus-datastore # Change the namespace here\n</code></pre> <p>Then, deploy the Operator using <code>kubectl</code> and wait for the deployment to complete:</p> <pre><code>$ kubectl apply -k . --server-side\n$ kubectl rollout status -n piraeus-datastore -w deploy/piraeus-operator-controller-manager\n</code></pre>"},{"location":"upgrade/migration/4-install-operator-v2/#deploy-piraeus-operator-v2-using-helm","title":"Deploy Piraeus Operator v2 Using Helm","text":"<p>To deploy Piraeus Operator v2 using Helm, clone the latest v2 release of Piraeus. The latest releases are available on the release page.</p> <p>To also install the necessary Custom Resource Definitions for Piraeus, set <code>installCRDs</code> to <code>true</code>.</p> <pre><code>$ git clone -b v2.3.0 https://github.com/piraeusdatastore/piraeus-operator.git\n$ cd piraeus-operator\n$ helm install piraeus-operator charts/piraeus --set installCRDs=true\n</code></pre>"},{"location":"upgrade/migration/4-install-operator-v2/#deploy-the-piraeus-datastore-cluster","title":"Deploy the Piraeus Datastore Cluster","text":"<p>Once the Operator is deployed, deploy the Cluster using the generated resources from step 2.</p> <p>First, create the secret used for the LINSTOR passphrase collected at the end of step 2.</p> <pre><code>$ cat &lt;&lt;-EOF | kubectl apply -f - --server-side\napiVersion: v1\nkind: Secret\nmetadata:\n  name: piraeus-op-passphrase\n  namespace: piraeus-datastore # Change the namespace here\ndata:\n  MASTER_PASSPHRASE: ZVRxanl1cVBscXV1ZTk1cmEwVTk5b0ptd0F4OGFmWlVPUVA0NWNnUw==\nEOF\n</code></pre> <p>Then, apply the resource generated by the script from step 2:</p> <pre><code>$ kubectl apply -f v2-resources.yaml --server-side\nlinstorcluster.piraeus.io/linstorcluster created\nlinstorsatelliteconfiguration.piraeus.io/host-networking created\nlinstorsatelliteconfiguration.piraeus.io/piraeus-op-ns created\n</code></pre> <p>Now the cluster will come up, using the existing data to restore the cluster state.</p>"},{"location":"upgrade/migration/4-install-operator-v2/#verifying-cluster-state","title":"Verifying Cluster State","text":"<p>You can check the Cluster state by using the <code>linstor</code> command line client:</p> <pre><code>$ kubectl exec deploy/linstor-controller -- linstor node list\n$ kubectl exec deploy/linstor-controller -- linstor storage-pool list\n$ kubectl exec deploy/linstor-controller -- linstor resource list-volumes\n$ kubectl exec deploy/linstor-controller -- linstor error-reports list\n</code></pre> <p>You can also provision new volumes, to verify that the cluster is operational.</p>"}]}
\ No newline at end of file
diff --git a/v2.7.1/sitemap.xml b/v2.7.1/sitemap.xml
index 0606855..cbb9a14 100644
--- a/v2.7.1/sitemap.xml
+++ b/v2.7.1/sitemap.xml
@@ -2,154 +2,154 @@
 <urlset xmlns="http://www.sitemaps.org/schemas/sitemap/0.9">
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/CHANGELOG/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/explanation/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/explanation/components/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/api-tls/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/drbd-host-networking/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/drbd-loader/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/drbd-tls/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/external-controller/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/flatcar/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/http-proxy/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/install-kernel-headers/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/internal-tls/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/k0s/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/linstor-affinity-controller/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/microk8s/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/monitoring/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/network-policy/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/openshift/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/restore-linstor-db/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/secure-boot/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
          <loc>https://piraeus.io/docs/v2.7.1/how-to/talos/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/how-to/upgrade/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/reference/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/how-to/upgrade/1-migrate-database/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/reference/linstorcluster/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/how-to/upgrade/2-collect-information/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/reference/linstornodeconnection/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/how-to/upgrade/3-remove-operator-v1/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/reference/linstorsatellite/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/how-to/upgrade/4-install-operator-v2/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/reference/linstorsatelliteconfiguration/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/how-to/upgrade/UPGRADE/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/tutorial/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/reference/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/tutorial/get-started/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/reference/linstorcluster/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/tutorial/replicated-volumes/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/reference/linstornodeconnection/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/tutorial/snapshots/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/reference/linstorsatellite/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/upgrade/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/reference/linstorsatelliteconfiguration/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/upgrade/migration/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/tutorial/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/upgrade/migration/1-migrate-database/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/tutorial/get-started/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/upgrade/migration/2-collect-information/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/tutorial/replicated-volumes/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/upgrade/migration/3-remove-operator-v1/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
     <url>
-         <loc>https://piraeus.io/docs/v2.7.1/tutorial/snapshots/</loc>
-         <lastmod>2024-11-27</lastmod>
+         <loc>https://piraeus.io/docs/v2.7.1/upgrade/migration/4-install-operator-v2/</loc>
+         <lastmod>2024-11-28</lastmod>
     </url>
 </urlset>
\ No newline at end of file
diff --git a/v2.7.1/sitemap.xml.gz b/v2.7.1/sitemap.xml.gz
index 8fd7e08..58d67cd 100644
Binary files a/v2.7.1/sitemap.xml.gz and b/v2.7.1/sitemap.xml.gz differ
diff --git a/v2.7.1/tutorial/get-started/index.html b/v2.7.1/tutorial/get-started/index.html
index ac6127d..e3a5c3c 100644
--- a/v2.7.1/tutorial/get-started/index.html
+++ b/v2.7.1/tutorial/get-started/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Getting Started - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/get-started.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Getting Started - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/get-started.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1436,8 +1436,6 @@
       
         
       
-        
-      
     
     
       
@@ -1455,7 +1453,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1485,31 +1483,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1531,35 +1512,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1580,7 +1571,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1601,7 +1592,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1622,7 +1613,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -2001,14 +1992,14 @@
   
 
 
-<h1 id="get-started">Get Started</h1>
+<h1 id="get-started">Get Started<a class="headerlink" href="#get-started" title="Permanent link">&para;</a></h1>
 <p>Learn about the ways to get started with Piraeus Datastore by deploying Piraeus Operator and provisioning your first volume.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="../../how-to/install-kernel-headers/">Install the Linux kernel headers on the hosts</a>.</li>
 <li><a href="https://kubernetes.io/docs/tasks/tools/">Install <code>kubectl</code> version <code>&gt;= 1.22</code></a></li>
 </ul>
-<h2 id="install-piraeus-operator">Install Piraeus Operator</h2>
+<h2 id="install-piraeus-operator">Install Piraeus Operator<a class="headerlink" href="#install-piraeus-operator" title="Permanent link">&para;</a></h2>
 <p>In this tutorial we will be using <code>kubectl</code> with the built-in <code>kustomize</code> feature to deploy Piraeus Operator.
 All resources needed to run Piraeus Operator are included in a single Kustomization.</p>
 <p>Install Piraeus Operator by running:</p>
@@ -2021,7 +2012,7 @@ <h2 id="install-piraeus-operator">Install Piraeus Operator</h2>
 <div class="highlight"><pre><span></span><code>$ kubectl wait pod --for=condition=Ready -n piraeus-datastore -l app.kubernetes.io/component=piraeus-operator
 pod/piraeus-operator-controller-manager-dd898f48c-bhbtv condition met
 </code></pre></div>
-<h2 id="deploy-piraeus-datastore">Deploy Piraeus Datastore</h2>
+<h2 id="deploy-piraeus-datastore">Deploy Piraeus Datastore<a class="headerlink" href="#deploy-piraeus-datastore" title="Permanent link">&para;</a></h2>
 <p>Now, we will deploy Piraeus Datastore using a new resource managed by Piraeus Operator. We create a <code>LinstorCluster</code>,
 which creates all the necessary resources (Deployments, Pods, and so on...) for our Datastore:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl apply -f - &lt;&lt;EOF
@@ -2054,7 +2045,7 @@ <h2 id="deploy-piraeus-datastore">Deploy Piraeus Datastore</h2>
 | n3.example.com | SATELLITE | 10.125.97.33:3366 (PLAIN)   | Online |
 +-------------------------------------------------------------------+
 </code></pre></div>
-<h2 id="configuring-storage">Configuring Storage</h2>
+<h2 id="configuring-storage">Configuring Storage<a class="headerlink" href="#configuring-storage" title="Permanent link">&para;</a></h2>
 <p>We have not yet configured any storage location for our volumes. This can be accomplished by creating a new
 <code>LinstorSatelliteConfiguration</code> resource. We will create a storage pool of type <code>fileThinPool</code> on each node.
 We chose <code>fileThinPool</code> as it does not require further configuration on the host.</p>
@@ -2094,7 +2085,7 @@ <h2 id="configuring-storage">Configuring Storage</h2>
 | pool1                | n3.example.com | FILE_THIN | /var/lib/piraeus-datastore/pool1 |    26.54 GiB |     49.30 GiB | True         | Ok    |            |
 +---------------------------------------------------------------------------------------------------------------------------------------------------------+
 </code></pre></div>
-<h2 id="using-piraeus-datastore">Using Piraeus Datastore</h2>
+<h2 id="using-piraeus-datastore">Using Piraeus Datastore<a class="headerlink" href="#using-piraeus-datastore" title="Permanent link">&para;</a></h2>
 <p>We now have successfully deployed and configured Piraeus Datastore, and are ready to create our first
 <a href="https://kubernetes.io/docs/concepts/storage/persistent-volumes/"><code>PersistentVolume</code></a> in Kubernetes.</p>
 <p>First, we will set up a new <a href="https://kubernetes.io/docs/concepts/storage/storage-classes/"><code>StorageClass</code></a> for our
diff --git a/v2.7.1/tutorial/index.html b/v2.7.1/tutorial/index.html
index b9b2648..2851095 100644
--- a/v2.7.1/tutorial/index.html
+++ b/v2.7.1/tutorial/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Tutorials - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/README.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Tutorials - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/README.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../how-to/upgrade/" class="md-tabs__link">
+        <a href="../upgrade/" class="md-tabs__link">
           
   
     
@@ -1351,8 +1351,6 @@
       
         
       
-        
-      
     
     
       
@@ -1370,7 +1368,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../how-to/upgrade/" class="md-nav__link ">
+            <a href="../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1400,31 +1398,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1446,35 +1427,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1495,7 +1486,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1516,7 +1507,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1537,7 +1528,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1898,13 +1889,13 @@
   
 
 
-<h1 id="tutorials">Tutorials</h1>
+<h1 id="tutorials">Tutorials<a class="headerlink" href="#tutorials" title="Permanent link">&para;</a></h1>
 <p>These tutorials help you get started with Piraeus Datastore</p>
-<h3 id="get-started"><a href="get-started/">Get Started</a></h3>
+<h3 id="get-started"><a href="get-started/">Get Started</a><a class="headerlink" href="#get-started" title="Permanent link">&para;</a></h3>
 <p>Get started with Piraeus Datastore by deploying Piraeus Operator and provisioning your first volume.</p>
-<h3 id="creating-replicated-volumes"><a href="replicated-volumes/">Creating Replicated Volumes</a></h3>
+<h3 id="creating-replicated-volumes"><a href="replicated-volumes/">Creating Replicated Volumes</a><a class="headerlink" href="#creating-replicated-volumes" title="Permanent link">&para;</a></h3>
 <p>Create replicated volumes, making your data accessible on any cluster node.</p>
-<h3 id="creating-and-restoring-from-snapshots"><a href="snapshots/">Creating and Restoring from Snapshots</a></h3>
+<h3 id="creating-and-restoring-from-snapshots"><a href="snapshots/">Creating and Restoring from Snapshots</a><a class="headerlink" href="#creating-and-restoring-from-snapshots" title="Permanent link">&para;</a></h3>
 <p>Create snapshots and restore a volume, safeguarding data against accidental deletion.</p>
 
 
diff --git a/v2.7.1/tutorial/replicated-volumes/index.html b/v2.7.1/tutorial/replicated-volumes/index.html
index 5b1b98e..be9fa46 100644
--- a/v2.7.1/tutorial/replicated-volumes/index.html
+++ b/v2.7.1/tutorial/replicated-volumes/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Creating Replicated Volumes - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/replicated-volumes.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Creating Replicated Volumes - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/replicated-volumes.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1427,8 +1427,6 @@
       
         
       
-        
-      
     
     
       
@@ -1446,7 +1444,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1476,31 +1474,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1522,35 +1503,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1571,7 +1562,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1592,7 +1583,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1613,7 +1604,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1983,16 +1974,16 @@
   
 
 
-<h1 id="creating-replicated-volumes">Creating Replicated Volumes</h1>
+<h1 id="creating-replicated-volumes">Creating Replicated Volumes<a class="headerlink" href="#creating-replicated-volumes" title="Permanent link">&para;</a></h1>
 <p>Learn about creating replicated volumes, making your data accessible on any cluster node.</p>
 <p>In this tutorial you will learn how to create a replicated volume, and verify that the data stays accessible when
 moving Pods from one node to another.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li>A Kubernetes Cluster with at least two nodes.</li>
 <li>An installed and configured Piraeus Datastore. Learn how to get started in our <a href="../get-started/">introduction tutorial</a></li>
 </ul>
-<h2 id="creating-the-volume">Creating the Volume</h2>
+<h2 id="creating-the-volume">Creating the Volume<a class="headerlink" href="#creating-the-volume" title="Permanent link">&para;</a></h2>
 <p>First, we will create a new <a href="https://kubernetes.io/docs/concepts/storage/storage-classes/"><code>StorageClass</code></a> for our
 replicated volumes. We will be using the <code>pool1</code> storage pool from the <a href="../get-started/">Get Started tutorial</a>, but
 this time also set the <code>placementCount</code> to 2, telling LINSTOR® to store the volume data on two nodes.</p>
@@ -2089,7 +2080,7 @@ <h2 id="creating-the-volume">Creating the Volume</h2>
 <div class="highlight"><pre><span></span><code>$ kubectl exec deploy/volume-logger -- cat /volume/hello
 Hello from volume-logger-84dd47f4cb-trh4l, running on n1.example.com, started at Fri Feb  3 08:53:47 UTC 2023
 </code></pre></div>
-<h2 id="testing-replication">Testing Replication</h2>
+<h2 id="testing-replication">Testing Replication<a class="headerlink" href="#testing-replication" title="Permanent link">&para;</a></h2>
 <p>Now, we will verify that when we move the Pod to another node, we still have access to the same data.</p>
 <p>To test this, we will disable scheduling on the node the Pod is currently running on. This forces Kubernetes to move the
 Pod to another node once we trigger a restart. In our examples, the Hello message tells us that the Pod was started on
@@ -2124,7 +2115,7 @@ <h2 id="testing-replication">Testing Replication</h2>
 +-------------------------------------------------------------------------------------------------------------------------------------------+
 </code></pre></div>
 <p>You have now successfully created a replicated volume and verified that the data is accessible from multiple nodes.</p>
-<h2 id="resetting-the-disabled-node">Resetting the Disabled Node</h2>
+<h2 id="resetting-the-disabled-node">Resetting the Disabled Node<a class="headerlink" href="#resetting-the-disabled-node" title="Permanent link">&para;</a></h2>
 <p>Now that we have verified replication works, we can reset the disabled node:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl uncordon n1.example.com
 node/n1.example.com uncordoned
diff --git a/v2.7.1/tutorial/snapshots/index.html b/v2.7.1/tutorial/snapshots/index.html
index 650650a..d2c35f1 100644
--- a/v2.7.1/tutorial/snapshots/index.html
+++ b/v2.7.1/tutorial/snapshots/index.html
@@ -6,7 +6,7 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
@@ -63,7 +63,7 @@
       
         <meta  property="og:title"  content="Creating Snapshots - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/snapshots.png" >
       
@@ -79,7 +79,7 @@
       
         <meta  name="twitter:title"  content="Creating Snapshots - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
         <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/tutorial/snapshots.png" >
       
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../how-to/upgrade/" class="md-tabs__link">
+        <a href="../../upgrade/" class="md-tabs__link">
           
   
     
@@ -1436,8 +1436,6 @@
       
         
       
-        
-      
     
     
       
@@ -1455,7 +1453,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../how-to/upgrade/" class="md-nav__link ">
+            <a href="../../upgrade/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1485,31 +1483,14 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../../how-to/upgrade/UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
   
   
     
     
+      
+        
+          
+        
       
         
       
@@ -1531,35 +1512,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="0">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../../upgrade/migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="0">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/1-migrate-database/" class="md-nav__link">
+      <a href="../../upgrade/migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1580,7 +1571,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/2-collect-information/" class="md-nav__link">
+      <a href="../../upgrade/migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1601,7 +1592,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/3-remove-operator-v1/" class="md-nav__link">
+      <a href="../../upgrade/migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1622,7 +1613,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../how-to/upgrade/4-install-operator-v2/" class="md-nav__link">
+      <a href="../../upgrade/migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -2001,14 +1992,14 @@
   
 
 
-<h1 id="creating-and-restoring-from-snapshots">Creating and Restoring From Snapshots</h1>
+<h1 id="creating-and-restoring-from-snapshots">Creating and Restoring From Snapshots<a class="headerlink" href="#creating-and-restoring-from-snapshots" title="Permanent link">&para;</a></h1>
 <p>Learn how to create snapshots of your data, and how you can restore the data in a snapshot.</p>
 <p>Snapshots create a copy of the volume content at a particular point in time. This copy remains untouched when you make
 modifications to the volume content. This, for example, enables you to create backups of your data before performing
 modifications or deletion on your data.</p>
 <p>Since a backup is useless, unless you have a way to restore it, this tutorial will teach you both how to create a
 snapshot, and how to restore in the case of accidental deletion of your data.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li>An installed and configured Piraeus Datastore. Learn how to get started in our <a href="../get-started/">introduction tutorial</a></li>
 <li>A storage pool supporting snapshots. LINSTOR supports snapshots for <code>LVM_THIN</code>, <code>FILE_THIN</code>, <code>ZFS</code> and <code>ZFS_THIN</code> pools.
@@ -2026,7 +2017,7 @@ <h2 id="prerequisites">Prerequisites</h2>
 kubectl apply -k https://github.com/kubernetes-csi/external-snapshotter//deploy/kubernetes/snapshot-controller
 </code></pre></div></li>
 </ul>
-<h2 id="creating-an-example-workload">Creating an Example Workload</h2>
+<h2 id="creating-an-example-workload">Creating an Example Workload<a class="headerlink" href="#creating-an-example-workload" title="Permanent link">&para;</a></h2>
 <p>We will be using the same workload as in the <a href="../replicated-volumes/">replicated volumes tutorial</a>. This workload
 will save the Pods name, the node it is running on, and a timestamp to our volume. By logging this information to our
 volume, we can easily keep track of our data.</p>
@@ -2101,7 +2092,7 @@ <h2 id="creating-an-example-workload">Creating an Example Workload</h2>
 $ kubectl exec deploy/volume-logger -- cat /volume/hello
 Hello from volume-logger-cbcd897b7-jrmks, running on n3.example.com, started at Mon Feb 13 15:32:46 UTC 2023
 </code></pre></div>
-<h2 id="creating-a-snapshot">Creating a Snapshot</h2>
+<h2 id="creating-a-snapshot">Creating a Snapshot<a class="headerlink" href="#creating-a-snapshot" title="Permanent link">&para;</a></h2>
 <p>Creating a snapshot requires the creation of a <a href="https://kubernetes.io/docs/concepts/storage/volume-snapshot-classes/"><code>SnapshotClass</code></a> first.
 The <code>SnapshotClass</code> specifies our <code>linstor.csi.linbit.com</code> provisioner, and sets the clean-up policy for our snapshots
 to <code>Delete</code>, meaning deleting the Kubernetes resources will also delete the snapshots in LINSTOR®.</p>
@@ -2141,7 +2132,7 @@ <h2 id="creating-a-snapshot">Creating a Snapshot</h2>
 | pvc-9c04b307-d22d-454f-8f24-ed5837fe4426 | snapshot-a8757c1d-cd37-42d2-9557-a24b1222d118 | n3.example.com | 0: 1 GiB | 2023-02-13 15:36:18 | Successful |
 +---------------------------------------------------------------------------------------------------------------------------------------------------------+
 </code></pre></div>
-<h2 id="modifying-the-data">Modifying the Data</h2>
+<h2 id="modifying-the-data">Modifying the Data<a class="headerlink" href="#modifying-the-data" title="Permanent link">&para;</a></h2>
 <p>Now we want to simulate a situation where we accidentally delete some important data. The important data in our example
 workload is the log of Pod name, Node name and timestamp. We will manually delete the file on the volume to simulate
 accidental removal of an important file on a persistent volume:</p>
@@ -2150,7 +2141,7 @@ <h2 id="modifying-the-data">Modifying the Data</h2>
 cat: can&#39;t open &#39;/volume/hello&#39;: No such file or directory
 command terminated with exit code 1
 </code></pre></div>
-<h2 id="restoring-from-a-snapshot">Restoring From a Snapshot</h2>
+<h2 id="restoring-from-a-snapshot">Restoring From a Snapshot<a class="headerlink" href="#restoring-from-a-snapshot" title="Permanent link">&para;</a></h2>
 <p>This is the exact situation where snapshots can come in handy. Since we created a snapshot before we made removed the
 file, we can create a new volume to recover our data. We will be replacing the existing <code>data-volume</code> with a new version
 based on the snapshot.</p>
diff --git a/v2.7.1/how-to/upgrade/UPGRADE/index.html b/v2.7.1/upgrade/index.html
similarity index 86%
rename from v2.7.1/how-to/upgrade/UPGRADE/index.html
rename to v2.7.1/upgrade/index.html
index 53bae0d..71c67bf 100644
--- a/v2.7.1/how-to/upgrade/UPGRADE/index.html
+++ b/v2.7.1/upgrade/index.html
@@ -6,34 +6,34 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
       
       
-        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/how-to/upgrade/UPGRADE/">
+        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/upgrade/">
       
       
-        <link rel="prev" href="../">
+        <link rel="prev" href="../how-to/restore-linstor-db/">
       
       
-        <link rel="next" href="../1-migrate-database/">
+        <link rel="next" href="migration/">
       
       
-      <link rel="icon" href="../../../assets/favicon.png">
+      <link rel="icon" href="../assets/favicon.png">
       <meta name="generator" content="mkdocs-1.6.1, mkdocs-material-9.5.44">
     
     
       
-        <title>Upgrading from v2 to v2 - Piraeus Datastore</title>
+        <title>Upgrades - Piraeus Datastore</title>
       
     
     
-      <link rel="stylesheet" href="../../../assets/stylesheets/main.0253249f.min.css">
+      <link rel="stylesheet" href="../assets/stylesheets/main.0253249f.min.css">
       
         
-        <link rel="stylesheet" href="../../../assets/stylesheets/palette.06af60db.min.css">
+        <link rel="stylesheet" href="../assets/stylesheets/palette.06af60db.min.css">
       
       
 
@@ -52,7 +52,7 @@
       
     
     
-    <script>__md_scope=new URL("../../..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script>
+    <script>__md_scope=new URL("..",location),__md_hash=e=>[...e].reduce(((e,_)=>(e<<5)-e+_.charCodeAt(0)),0),__md_get=(e,_=localStorage,t=__md_scope)=>JSON.parse(_.getItem(t.pathname+"."+e)),__md_set=(e,_,t=localStorage,a=__md_scope)=>{try{t.setItem(a.pathname+"."+e,JSON.stringify(_))}catch(e){}}</script>
     
       
 
@@ -61,11 +61,11 @@
       
         <meta  property="og:type"  content="website" >
       
-        <meta  property="og:title"  content="Upgrading from v2 to v2 - Piraeus Datastore" >
+        <meta  property="og:title"  content="Upgrades - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/UPGRADE.png" >
+        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/README.png" >
       
         <meta  property="og:image:type"  content="image/png" >
       
@@ -73,15 +73,15 @@
       
         <meta  property="og:image:height"  content="630" >
       
-        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/how-to/upgrade/UPGRADE/" >
+        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/upgrade/" >
       
         <meta  name="twitter:card"  content="summary_large_image" >
       
-        <meta  name="twitter:title"  content="Upgrading from v2 to v2 - Piraeus Datastore" >
+        <meta  name="twitter:title"  content="Upgrades - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/UPGRADE.png" >
+        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/README.png" >
       
     
     
@@ -142,7 +142,7 @@
         <div class="md-header__topic" data-md-component="header-topic">
           <span class="md-ellipsis">
             
-              Upgrading from v2 to v2
+              Upgrades
             
           </span>
         </div>
@@ -266,7 +266,7 @@
   
   
     <li class="md-tabs__item">
-      <a href="../../.." class="md-tabs__link">
+      <a href=".." class="md-tabs__link">
         
   
     
@@ -285,7 +285,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../../tutorial/" class="md-tabs__link">
+        <a href="../tutorial/" class="md-tabs__link">
           
   
     
@@ -305,7 +305,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../" class="md-tabs__link">
+        <a href="../how-to/" class="md-tabs__link">
           
   
     
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item md-tabs__item--active">
-        <a href="../" class="md-tabs__link">
+        <a href="./" class="md-tabs__link">
           
   
     
@@ -347,7 +347,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../../explanation/" class="md-tabs__link">
+        <a href="../explanation/" class="md-tabs__link">
           
   
     
@@ -367,7 +367,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../../reference/" class="md-tabs__link">
+        <a href="../reference/" class="md-tabs__link">
           
   
     
@@ -385,7 +385,7 @@
   
   
     <li class="md-tabs__item">
-      <a href="../../../CHANGELOG/" class="md-tabs__link">
+      <a href="../CHANGELOG/" class="md-tabs__link">
         
   
     
@@ -449,7 +449,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../.." class="md-nav__link">
+      <a href=".." class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -498,7 +498,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../../tutorial/" class="md-nav__link ">
+            <a href="../tutorial/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -531,7 +531,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../tutorial/get-started/" class="md-nav__link">
+      <a href="../tutorial/get-started/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -552,7 +552,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../tutorial/replicated-volumes/" class="md-nav__link">
+      <a href="../tutorial/replicated-volumes/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -573,7 +573,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../tutorial/snapshots/" class="md-nav__link">
+      <a href="../tutorial/snapshots/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -634,7 +634,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../" class="md-nav__link ">
+            <a href="../how-to/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -715,7 +715,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../external-controller/" class="md-nav__link">
+      <a href="../how-to/external-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -736,7 +736,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-loader/" class="md-nav__link">
+      <a href="../how-to/drbd-loader/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -757,7 +757,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../install-kernel-headers/" class="md-nav__link">
+      <a href="../how-to/install-kernel-headers/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -836,7 +836,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../internal-tls/" class="md-nav__link">
+      <a href="../how-to/internal-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -857,7 +857,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../api-tls/" class="md-nav__link">
+      <a href="../how-to/api-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -878,7 +878,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-tls/" class="md-nav__link">
+      <a href="../how-to/drbd-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -899,7 +899,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../secure-boot/" class="md-nav__link">
+      <a href="../how-to/secure-boot/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -980,7 +980,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../openshift/" class="md-nav__link">
+      <a href="../how-to/openshift/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1001,7 +1001,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../talos/" class="md-nav__link">
+      <a href="../how-to/talos/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1022,7 +1022,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../flatcar/" class="md-nav__link">
+      <a href="../how-to/flatcar/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1043,7 +1043,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../microk8s/" class="md-nav__link">
+      <a href="../how-to/microk8s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1064,7 +1064,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../k0s/" class="md-nav__link">
+      <a href="../how-to/k0s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1141,7 +1141,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../http-proxy/" class="md-nav__link">
+      <a href="../how-to/http-proxy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1162,7 +1162,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../network-policy/" class="md-nav__link">
+      <a href="../how-to/network-policy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1183,7 +1183,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-host-networking/" class="md-nav__link">
+      <a href="../how-to/drbd-host-networking/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1260,7 +1260,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../monitoring/" class="md-nav__link">
+      <a href="../how-to/monitoring/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1281,7 +1281,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../linstor-affinity-controller/" class="md-nav__link">
+      <a href="../how-to/linstor-affinity-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1302,7 +1302,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../restore-linstor-db/" class="md-nav__link">
+      <a href="../how-to/restore-linstor-db/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1346,8 +1346,6 @@
           
         
       
-        
-      
         
       
     
@@ -1370,7 +1368,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../" class="md-nav__link ">
+            <a href="./" class="md-nav__link md-nav__link--active">
               
   
   <span class="md-ellipsis">
@@ -1381,7 +1379,7 @@
             </a>
             
               
-              <label class="md-nav__link " for="__nav_4" id="__nav_4_label" tabindex="">
+              <label class="md-nav__link md-nav__link--active" for="__nav_4" id="__nav_4_label" tabindex="">
                 <span class="md-nav__icon md-icon"></span>
               </label>
             
@@ -1400,41 +1398,14 @@
                 
   
   
-    
-  
   
   
-    <li class="md-nav__item md-nav__item--active">
-      
-      <input class="md-nav__toggle md-toggle" type="checkbox" id="__toc">
-      
+    
+    
       
         
-      
-      
-      <a href="./" class="md-nav__link md-nav__link--active">
+          
         
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-      
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
-  
-  
-    
-    
       
         
       
@@ -1459,35 +1430,45 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" >
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="migration/" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="false">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
   
   
     <li class="md-nav__item">
-      <a href="../1-migrate-database/" class="md-nav__link">
+      <a href="migration/1-migrate-database/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1508,7 +1489,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../2-collect-information/" class="md-nav__link">
+      <a href="migration/2-collect-information/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1529,7 +1510,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../3-remove-operator-v1/" class="md-nav__link">
+      <a href="migration/3-remove-operator-v1/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1550,7 +1531,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../4-install-operator-v2/" class="md-nav__link">
+      <a href="migration/4-install-operator-v2/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1611,7 +1592,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../../explanation/" class="md-nav__link ">
+            <a href="../explanation/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1644,7 +1625,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../explanation/components/" class="md-nav__link">
+      <a href="../explanation/components/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1703,7 +1684,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../../reference/" class="md-nav__link ">
+            <a href="../reference/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1736,7 +1717,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../reference/linstorcluster/" class="md-nav__link">
+      <a href="../reference/linstorcluster/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1757,7 +1738,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../reference/linstorsatelliteconfiguration/" class="md-nav__link">
+      <a href="../reference/linstorsatelliteconfiguration/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1778,7 +1759,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../reference/linstornodeconnection/" class="md-nav__link">
+      <a href="../reference/linstornodeconnection/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1799,7 +1780,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../reference/linstorsatellite/" class="md-nav__link">
+      <a href="../reference/linstorsatellite/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1827,7 +1808,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../../CHANGELOG/" class="md-nav__link">
+      <a href="../CHANGELOG/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1876,7 +1857,7 @@
   
 
 
-<h1 id="general-notes">General notes</h1>
+<h1 id="general-notes">General notes<a class="headerlink" href="#general-notes" title="Permanent link">&para;</a></h1>
 <p>During the upgrade process, provisioning of volumes and attach/detach operations might not work. Existing
 volumes and volumes already in use by a pod will continue to work without interruption.</p>
 <p>To upgrade, apply the resource of the latest release. Use the same method that was used to create the initial deployment
@@ -1886,55 +1867,55 @@ <h1 id="general-notes">General notes</h1>
 <div class="highlight"><pre><span></span><code>$ kubectl apply --server-side -k &quot;https://github.com/piraeusdatastore/piraeus-operator//config/default?ref=v2.7.1&quot;
 $ kubectl wait pod --for=condition=Ready -n piraeus-datastore --all
 </code></pre></div>
-<h1 id="upgrades-from-v26-to-v27">Upgrades from v2.6 to v2.7</h1>
+<h1 id="upgrades-from-v26-to-v27">Upgrades from v2.6 to v2.7<a class="headerlink" href="#upgrades-from-v26-to-v27" title="Permanent link">&para;</a></h1>
 <p>Generally, no special steps required.</p>
 <p>LINSTOR Satellites now try to automatically detect the LVM configuration on the host. Any patch targeting the Satellites
 /etc/lvm/lvm.conf file may need to be adapted.</p>
-<h1 id="upgrades-from-v25-to-v26">Upgrades from v2.5 to v2.6</h1>
+<h1 id="upgrades-from-v25-to-v26">Upgrades from v2.5 to v2.6<a class="headerlink" href="#upgrades-from-v25-to-v26" title="Permanent link">&para;</a></h1>
 <p>No special steps required.</p>
-<h1 id="upgrades-from-v24-to-v25">Upgrades from v2.4 to v2.5</h1>
+<h1 id="upgrades-from-v24-to-v25">Upgrades from v2.4 to v2.5<a class="headerlink" href="#upgrades-from-v24-to-v25" title="Permanent link">&para;</a></h1>
 <p>No special steps required.</p>
-<h1 id="upgrades-from-v23-to-v24">Upgrades from v2.3 to v2.4</h1>
+<h1 id="upgrades-from-v23-to-v24">Upgrades from v2.3 to v2.4<a class="headerlink" href="#upgrades-from-v23-to-v24" title="Permanent link">&para;</a></h1>
 <p>Generally, no special steps required.</p>
 <p>LINSTOR Satellites are now managed via DaemonSet resources. Any patch targeting a <code>satellite</code> Pod resources is
 automatically converted to the equivalent DaemonSet resource patch. In the Pod list, you will see these Pods using
 a new <code>linstor-satellite</code> prefix.</p>
-<h1 id="upgrades-from-v22-to-v23">Upgrades from v2.2 to v2.3</h1>
+<h1 id="upgrades-from-v22-to-v23">Upgrades from v2.2 to v2.3<a class="headerlink" href="#upgrades-from-v22-to-v23" title="Permanent link">&para;</a></h1>
 <p>Removed the <code>NetworkPolicy</code> resource from default deployment. It can be reapplied as a
-<a href="../../network-policy/">separate step</a>.</p>
-<h1 id="upgrades-from-v21-to-v22">Upgrades from v2.1 to v2.2</h1>
+<a href="../how-to/network-policy/">separate step</a>.</p>
+<h1 id="upgrades-from-v21-to-v22">Upgrades from v2.1 to v2.2<a class="headerlink" href="#upgrades-from-v21-to-v22" title="Permanent link">&para;</a></h1>
 <p>Removed the dependency on cert-manager for the initial deployment. To clean up an existing <code>Certificate</code> resource,
 run the following commands:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl delete certificate -n piraeus-datastore piraeus-operator-serving-cert
 </code></pre></div>
-<h1 id="upgrades-from-v20-to-v21">Upgrades from v2.0 to v2.1</h1>
+<h1 id="upgrades-from-v20-to-v21">Upgrades from v2.0 to v2.1<a class="headerlink" href="#upgrades-from-v20-to-v21" title="Permanent link">&para;</a></h1>
 <p>No special steps required.</p>
-<h1 id="upgrades-from-v1-to-v2">Upgrades from v1 to v2</h1>
-<p>Please follow the specialized <a href="../">upgrade guides</a>.</p>
-<h1 id="upgrade-from-v19-to-v110">Upgrade from v1.9 to v1.10</h1>
+<h1 id="upgrades-from-v1-to-v2">Upgrades from v1 to v2<a class="headerlink" href="#upgrades-from-v1-to-v2" title="Permanent link">&para;</a></h1>
+<p>Please follow the specialized <a href="migration/">upgrade guides</a>.</p>
+<h1 id="upgrade-from-v19-to-v110">Upgrade from v1.9 to v1.10<a class="headerlink" href="#upgrade-from-v19-to-v110" title="Permanent link">&para;</a></h1>
 <p>If you want to share DRBD configuration directories with the host, please update the CRDs before upgrading using helm:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl replace -f ./charts/piraeus/crds
 </code></pre></div>
-<h1 id="upgrade-from-v18-to-v19">Upgrade from v1.8 to v1.9</h1>
+<h1 id="upgrade-from-v18-to-v19">Upgrade from v1.8 to v1.9<a class="headerlink" href="#upgrade-from-v18-to-v19" title="Permanent link">&para;</a></h1>
 <p>If you want to protect metrics endpoints, take a look on <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v1.9.0/doc/security.md">guide on enabling rbac-proxy sidecars</a>.</p>
 <p>We've also disabled the <code>haController</code> component in our chart. The replacement is available from
 <a href="https://artifacthub.io/packages/helm/piraeus-charts/piraeus-ha-controller">artifacthub.io</a>, containing much needed
 improvements in robustness and fail-over speed. If you want to still use the old version, set
 <code>haController.enabled=true</code>.</p>
-<h1 id="upgrade-from-v17-to-v18">Upgrade from v1.7 to v1.8</h1>
+<h1 id="upgrade-from-v17-to-v18">Upgrade from v1.7 to v1.8<a class="headerlink" href="#upgrade-from-v17-to-v18" title="Permanent link">&para;</a></h1>
 <p>If you need to set the number of worker threads, or you need to set the log level of LINSTOR components, please update
 the CRDs before upgrading using helm:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl replace -f ./charts/piraeus/crds
 </code></pre></div>
 <p>In case if you have SSL enabled installation, you need to regenerate your certificates in PEM format.
 Read the <a href="https://github.com/piraeusdatastore/piraeus-operator/tree/v1.8.0/doc/security.md">guide on securing the deployment</a> and repeat the described steps.</p>
-<h1 id="upgrade-from-v16-to-v17">Upgrade from v1.6 to v1.7</h1>
+<h1 id="upgrade-from-v16-to-v17">Upgrade from v1.6 to v1.7<a class="headerlink" href="#upgrade-from-v16-to-v17" title="Permanent link">&para;</a></h1>
 <p>Node labels are now automatically applied to LINSTOR satellites as "Auxiliary Properties". That means you can reuse your
 existing Kubernetes Topology information (for example <code>topology.kubernetes.io/zone</code> labels) when scheduling volumes
 using the <code>replicasOnSame</code> and <code>replicasOnDifferent</code> settings. However, this also means that the Operator will delete
 any existing auxiliary properties that were already applied. To apply auxiliary properties to satellites, you <em>have to</em>
 apply a label to the Kubernetes node object.</p>
-<h1 id="upgrade-from-v15-to-v16">Upgrade from v1.5 to v1.6</h1>
+<h1 id="upgrade-from-v15-to-v16">Upgrade from v1.5 to v1.6<a class="headerlink" href="#upgrade-from-v15-to-v16" title="Permanent link">&para;</a></h1>
 <p>The <code>csi-snapshotter</code> subchart was removed from this repository. Users who relied on it for their snapshot support
 should switch to the seperate charts provided by the Piraeus team
 on <a href="https://artifacthub.io/packages/search?repo=piraeus-charts">artifacthub.io</a>
@@ -1942,7 +1923,7 @@ <h1 id="upgrade-from-v15-to-v16">Upgrade from v1.5 to v1.6</h1>
 <p>To support the new <code>csi.kubeletPath</code> option an update to the LinstorCSIDriver CRD is required:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl replace -f ./charts/piraeus/crds
 </code></pre></div>
-<h1 id="upgrade-from-v14-to-v15">Upgrade from v1.4 to v1.5</h1>
+<h1 id="upgrade-from-v14-to-v15">Upgrade from v1.4 to v1.5<a class="headerlink" href="#upgrade-from-v14-to-v15" title="Permanent link">&para;</a></h1>
 <p>To make use of the new <code>monitoringImage</code> value in the LinstorSatelliteSet CRD, you need to replace the existing CRDs
 before running the upgrade. If the CRDs are not upgraded, the operator will not deploy the monitoring container
 alongside the satellites.</p>
@@ -1951,7 +1932,7 @@ <h1 id="upgrade-from-v14-to-v15">Upgrade from v1.4 to v1.5</h1>
 <p>Then run the upgrade:</p>
 <div class="highlight"><pre><span></span><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;
 </code></pre></div>
-<h1 id="upgrade-from-v13-to-v14">Upgrade from v1.3 to v1.4</h1>
+<h1 id="upgrade-from-v13-to-v14">Upgrade from v1.3 to v1.4<a class="headerlink" href="#upgrade-from-v13-to-v14" title="Permanent link">&para;</a></h1>
 <p>No special steps required, unless using the newly introduced <code>additionalEnv</code> and <code>additionalProperties</code> overrides.</p>
 <p>If you plan to use the new overrides, replace the CustomResourceDefinitions before running the upgrade</p>
 <div class="highlight"><pre><span></span><code>$ kubectl replace -f ./charts/piraeus/crds
@@ -1959,11 +1940,11 @@ <h1 id="upgrade-from-v13-to-v14">Upgrade from v1.3 to v1.4</h1>
 <p>Then run the upgrade:</p>
 <div class="highlight"><pre><span></span><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;
 </code></pre></div>
-<h1 id="upgrade-from-v12-to-v13">Upgrade from v1.2 to v1.3</h1>
+<h1 id="upgrade-from-v12-to-v13">Upgrade from v1.2 to v1.3<a class="headerlink" href="#upgrade-from-v12-to-v13" title="Permanent link">&para;</a></h1>
 <p>No special steps required. After checking out the new repo, run a simple helm upgrade:</p>
 <div class="highlight"><pre><span></span><code>helm upgrade piraeus-op ./charts/piraeus -f &lt;overrides&gt;
 </code></pre></div>
-<h1 id="upgrade-from-v11-to-v12">Upgrade from v1.1 to v1.2</h1>
+<h1 id="upgrade-from-v11-to-v12">Upgrade from v1.1 to v1.2<a class="headerlink" href="#upgrade-from-v11-to-v12" title="Permanent link">&para;</a></h1>
 <p>Piraeus v1.2 is supported on Kubernetes 1.17+. If you are using an older Kubernetes distribution, you may need
 to change the default settings (for
 example <a href="https://kubernetes-csi.github.io/docs/external-provisioner.html">the CSI provisioner</a>)</p>
@@ -1981,7 +1962,7 @@ <h1 id="upgrade-from-v11-to-v12">Upgrade from v1.1 to v1.2</h1>
 operator.</p>
 <p>After a short wait, all pods should be running and ready. Check that no errors are listed in the status section of
 LinstorControllers, LinstorSatelliteSets and LinstorCSIDrivers.</p>
-<h1 id="upgrade-from-v10-to-v11">Upgrade from v1.0 to v1.1</h1>
+<h1 id="upgrade-from-v10-to-v11">Upgrade from v1.0 to v1.1<a class="headerlink" href="#upgrade-from-v10-to-v11" title="Permanent link">&para;</a></h1>
 <ul>
 <li>The LINSTOR controller image given in <code>operator.controller.controllerImage</code> has to have
   its entrypoint set to <a href="https://github.com/LINBIT/k8s-await-election/"><code>k8s-await-election v0.2.0</code></a>
@@ -1990,7 +1971,7 @@ <h1 id="upgrade-from-v10-to-v11">Upgrade from v1.0 to v1.1</h1>
 <p>Older images will not work, as the <code>Service</code> will not automatically pick up on the active pod.</p>
 <p>To upgrade, first update the deployed LINSTOR image to a compatible version, then upgrade the
   operator.</p>
-<h1 id="upgrade-to-v10">Upgrade to v1.0</h1>
+<h1 id="upgrade-to-v10">Upgrade to v1.0<a class="headerlink" href="#upgrade-to-v10" title="Permanent link">&para;</a></h1>
 <p>Upgrades from v0.* versions to v1.0 are best-effort only. The following guide assumes
 an upgrade from v0.5.0.</p>
 <ul>
@@ -2070,7 +2051,7 @@ <h1 id="upgrade-to-v10">Upgrade to v1.0</h1>
   If old settings are used, Helm will return an error.</p>
 </li>
 </ul>
-<h1 id="upgrade-between-v0-versions">Upgrade between v0.* versions</h1>
+<h1 id="upgrade-between-v0-versions">Upgrade between v0.* versions<a class="headerlink" href="#upgrade-between-v0-versions" title="Permanent link">&para;</a></h1>
 <p>While the API version was <code>v1alpha1</code>, this project did not maintain
 stability of or provide conversion of the Custom Resource Definitions.</p>
 <p>If you are using the Helm deployment, you may find that upgrades fail with
@@ -2122,7 +2103,7 @@ <h1 id="upgrade-between-v0-versions">Upgrade between v0.* versions</h1>
       <nav class="md-footer__inner md-grid" aria-label="Footer" >
         
           
-          <a href="../" class="md-footer__link md-footer__link--prev" aria-label="Previous: Upgrades">
+          <a href="../how-to/restore-linstor-db/" class="md-footer__link md-footer__link--prev" aria-label="Previous: Restore a LINSTOR Database Backup">
             <div class="md-footer__button md-icon">
               
               <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg>
@@ -2132,20 +2113,20 @@ <h1 id="upgrade-between-v0-versions">Upgrade between v0.* versions</h1>
                 Previous
               </span>
               <div class="md-ellipsis">
-                Upgrades
+                Restore a LINSTOR Database Backup
               </div>
             </div>
           </a>
         
         
           
-          <a href="../1-migrate-database/" class="md-footer__link md-footer__link--next" aria-label="Next: Migrating the LINSTOR Database">
+          <a href="migration/" class="md-footer__link md-footer__link--next" aria-label="Next: Upgrading from v1 to v2">
             <div class="md-footer__title">
               <span class="md-footer__direction">
                 Next
               </span>
               <div class="md-ellipsis">
-                Migrating the LINSTOR Database
+                Upgrading from v1 to v2
               </div>
             </div>
             <div class="md-footer__button md-icon">
@@ -2209,10 +2190,10 @@ <h1 id="upgrade-between-v0-versions">Upgrade between v0.* versions</h1>
     </div>
     
     
-    <script id="__config" type="application/json">{"base": "../../..", "features": ["content.code.annotate", "content.code.copy", "content.tooltips", "navigation.footer", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.top", "navigation.tracking", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../../../assets/javascripts/workers/search.6ce7567c.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": "stable", "provider": "mike"}}</script>
+    <script id="__config" type="application/json">{"base": "..", "features": ["content.code.annotate", "content.code.copy", "content.tooltips", "navigation.footer", "navigation.indexes", "navigation.sections", "navigation.tabs", "navigation.top", "navigation.tracking", "search.highlight", "search.share", "search.suggest", "toc.follow"], "search": "../assets/javascripts/workers/search.6ce7567c.min.js", "translations": {"clipboard.copied": "Copied to clipboard", "clipboard.copy": "Copy to clipboard", "search.result.more.one": "1 more on this page", "search.result.more.other": "# more on this page", "search.result.none": "No matching documents", "search.result.one": "1 matching document", "search.result.other": "# matching documents", "search.result.placeholder": "Type to start searching", "search.result.term.missing": "Missing", "select.version": "Select version"}, "version": {"alias": true, "default": "stable", "provider": "mike"}}</script>
     
     
-      <script src="../../../assets/javascripts/bundle.83f73b43.min.js"></script>
+      <script src="../assets/javascripts/bundle.83f73b43.min.js"></script>
       
     
   </body>
diff --git a/v2.7.1/how-to/upgrade/1-migrate-database/index.html b/v2.7.1/upgrade/migration/1-migrate-database/index.html
similarity index 94%
rename from v2.7.1/how-to/upgrade/1-migrate-database/index.html
rename to v2.7.1/upgrade/migration/1-migrate-database/index.html
index 6830c9e..bfa5515 100644
--- a/v2.7.1/how-to/upgrade/1-migrate-database/index.html
+++ b/v2.7.1/upgrade/migration/1-migrate-database/index.html
@@ -6,16 +6,16 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
       
       
-        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/how-to/upgrade/1-migrate-database/">
+        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/upgrade/migration/1-migrate-database/">
       
       
-        <link rel="prev" href="../UPGRADE/">
+        <link rel="prev" href="../">
       
       
         <link rel="next" href="../2-collect-information/">
@@ -63,9 +63,9 @@
       
         <meta  property="og:title"  content="Migrating the LINSTOR Database - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/1-migrate-database.png" >
+        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/1-migrate-database.png" >
       
         <meta  property="og:image:type"  content="image/png" >
       
@@ -73,15 +73,15 @@
       
         <meta  property="og:image:height"  content="630" >
       
-        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/how-to/upgrade/1-migrate-database/" >
+        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/upgrade/migration/1-migrate-database/" >
       
         <meta  name="twitter:card"  content="summary_large_image" >
       
         <meta  name="twitter:title"  content="Migrating the LINSTOR Database - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/1-migrate-database.png" >
+        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/1-migrate-database.png" >
       
     
     
@@ -305,7 +305,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../" class="md-tabs__link">
+        <a href="../../../how-to/" class="md-tabs__link">
           
   
     
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item md-tabs__item--active">
-        <a href="../" class="md-tabs__link">
+        <a href="../../" class="md-tabs__link">
           
   
     
@@ -634,7 +634,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../" class="md-nav__link ">
+            <a href="../../../how-to/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -715,7 +715,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../external-controller/" class="md-nav__link">
+      <a href="../../../how-to/external-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -736,7 +736,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-loader/" class="md-nav__link">
+      <a href="../../../how-to/drbd-loader/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -757,7 +757,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../install-kernel-headers/" class="md-nav__link">
+      <a href="../../../how-to/install-kernel-headers/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -836,7 +836,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../internal-tls/" class="md-nav__link">
+      <a href="../../../how-to/internal-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -857,7 +857,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../api-tls/" class="md-nav__link">
+      <a href="../../../how-to/api-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -878,7 +878,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-tls/" class="md-nav__link">
+      <a href="../../../how-to/drbd-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -899,7 +899,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../secure-boot/" class="md-nav__link">
+      <a href="../../../how-to/secure-boot/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -980,7 +980,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../openshift/" class="md-nav__link">
+      <a href="../../../how-to/openshift/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1001,7 +1001,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../talos/" class="md-nav__link">
+      <a href="../../../how-to/talos/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1022,7 +1022,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../flatcar/" class="md-nav__link">
+      <a href="../../../how-to/flatcar/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1043,7 +1043,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../microk8s/" class="md-nav__link">
+      <a href="../../../how-to/microk8s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1064,7 +1064,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../k0s/" class="md-nav__link">
+      <a href="../../../how-to/k0s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1141,7 +1141,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../http-proxy/" class="md-nav__link">
+      <a href="../../../how-to/http-proxy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1162,7 +1162,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../network-policy/" class="md-nav__link">
+      <a href="../../../how-to/network-policy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1183,7 +1183,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-host-networking/" class="md-nav__link">
+      <a href="../../../how-to/drbd-host-networking/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1260,7 +1260,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../monitoring/" class="md-nav__link">
+      <a href="../../../how-to/monitoring/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1281,7 +1281,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../linstor-affinity-controller/" class="md-nav__link">
+      <a href="../../../how-to/linstor-affinity-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1302,7 +1302,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../restore-linstor-db/" class="md-nav__link">
+      <a href="../../../how-to/restore-linstor-db/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1346,8 +1346,6 @@
           
         
       
-        
-      
         
       
     
@@ -1370,7 +1368,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../" class="md-nav__link ">
+            <a href="../../" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1400,27 +1398,6 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
     
   
   
@@ -1429,6 +1406,10 @@
     
       
         
+          
+        
+      
+        
       
         
       
@@ -1451,28 +1432,38 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" checked>
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" checked>
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="true">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="true">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
@@ -2108,17 +2099,17 @@
   
 
 
-<h1 id="migrating-the-linstor-controller-database-to-use-the-k8s-backend">Migrating the LINSTOR Controller Database to Use the <code>k8s</code> Backend</h1>
+<h1 id="migrating-the-linstor-controller-database-to-use-the-k8s-backend">Migrating the LINSTOR Controller Database to Use the <code>k8s</code> Backend<a class="headerlink" href="#migrating-the-linstor-controller-database-to-use-the-k8s-backend" title="Permanent link">&para;</a></h1>
 <p>This document guides you through the process of migrating an existing LINSTOR® Cluster to use the <code>k8s</code> database
 backend.</p>
 <p>This is the optional first step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2).
 <a href="../">Click here to get back to the overview</a>.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://kubernetes.io/docs/tasks/tools/">Install <code>kubectl</code></a></li>
 <li><a href="https://docs.helm.sh/docs/intro/install/">Install <code>helm</code></a></li>
 </ul>
-<h2 id="when-to-migrate-the-linstor-controller-database-to-the-k8s-backend">When to Migrate the LINSTOR Controller Database to the <code>k8s</code> Backend</h2>
+<h2 id="when-to-migrate-the-linstor-controller-database-to-the-k8s-backend">When to Migrate the LINSTOR Controller Database to the <code>k8s</code> Backend<a class="headerlink" href="#when-to-migrate-the-linstor-controller-database-to-the-k8s-backend" title="Permanent link">&para;</a></h2>
 <p>LINSTOR can use different database backends to store important state, such as the available volumes and where
 they are deployed. The available backends are:</p>
 <ul>
@@ -2141,10 +2132,10 @@ <h2 id="when-to-migrate-the-linstor-controller-database-to-the-k8s-backend">When
 </code></pre></div>
 <p>If the <code>connection_url</code> value starts with <code>etcd://</code> you are using the etcd backend and should consider
 migrating.</p>
-<h2 id="migrating-the-linstor-controller-database">Migrating the LINSTOR Controller Database</h2>
+<h2 id="migrating-the-linstor-controller-database">Migrating the LINSTOR Controller Database<a class="headerlink" href="#migrating-the-linstor-controller-database" title="Permanent link">&para;</a></h2>
 <p>During the migration, the LINSTOR Controller needs to be stopped. This means that provisioning and deletion
 of volumes will not work for the duration of the migration. Existing volumes will continue working normally.</p>
-<h3 id="1-stop-the-linstor-controller">1. Stop the LINSTOR Controller</h3>
+<h3 id="1-stop-the-linstor-controller">1. Stop the LINSTOR Controller<a class="headerlink" href="#1-stop-the-linstor-controller" title="Permanent link">&para;</a></h3>
 <p>To prevent unwanted modifications to the database during the migration, you need to stop the LINSTOR Controller.
 To stop the LINSTOR Controller, set the expected replicas for the controller to zero.</p>
 <p>First, find the currently deployed Piraeus Datastore release. For this guide, it is 1.10.8:</p>
@@ -2159,7 +2150,7 @@ <h3 id="1-stop-the-linstor-controller">1. Stop the LINSTOR Controller</h3>
 $ kubectl rollout status deploy/piraeus-op-cs-controller -w
 deployment &quot;piraeus-op-cs-controller&quot; successfully rolled out
 </code></pre></div>
-<h3 id="2-prepare-a-pod-for-running-the-migration">2. Prepare a Pod for Running the Migration</h3>
+<h3 id="2-prepare-a-pod-for-running-the-migration">2. Prepare a Pod for Running the Migration<a class="headerlink" href="#2-prepare-a-pod-for-running-the-migration" title="Permanent link">&para;</a></h3>
 <p>To run the migration, you need access to the <code>linstor-database</code> tool, which comes preinstalled with the LINSTOR
 Controller image. The following command displays the LINSTOR Controller image, the name of the ConfigMap storing the
 LINSTOR Configuration, and the service account for LINSTOR Controller. Take note of them, as they will be used for the
@@ -2201,7 +2192,7 @@ <h3 id="2-prepare-a-pod-for-running-the-migration">2. Prepare a Pod for Running
 <span class="w">      </span><span class="nt">configMap</span><span class="p">:</span>
 <span class="w">        </span><span class="nt">name</span><span class="p">:</span><span class="w"> </span><span class="l l-Scalar l-Scalar-Plain">$CONFIG_MAP</span>
 </code></pre></div>
-<h3 id="3-create-a-database-backup">3. Create a Database Backup</h3>
+<h3 id="3-create-a-database-backup">3. Create a Database Backup<a class="headerlink" href="#3-create-a-database-backup" title="Permanent link">&para;</a></h3>
 <p>Using the newly created migration Pod, create a database backup using the <code>linstor-database</code> tool.</p>
 <div class="highlight"><pre><span></span><code>$ kubectl exec linstor-database-migration -- /usr/share/linstor-server/bin/linstor-database export-db -c /etc/linstor /backup/backup-before-migration.json
 Loading configuration file &quot;/etc/linstor/linstor.toml&quot;
@@ -2220,7 +2211,7 @@ <h3 id="3-create-a-database-backup">3. Create a Database Backup</h3>
 <p>Then, copy the just created backup to permanent storage, so that it is not lost should the migration pod restart:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl cp linstor-database-migration:/backup/backup-before-migration.json backup-before-migration.json
 </code></pre></div>
-<h3 id="4-update-the-linstor-configuration-to-point-to-the-new-database-backend">4. Update the LINSTOR Configuration to Point to the New Database Backend</h3>
+<h3 id="4-update-the-linstor-configuration-to-point-to-the-new-database-backend">4. Update the LINSTOR Configuration to Point to the New Database Backend<a class="headerlink" href="#4-update-the-linstor-configuration-to-point-to-the-new-database-backend" title="Permanent link">&para;</a></h3>
 <p>After creating and storing the backup it is safe to change the LINSTOR configuration. This is done by running another
 <code>helm upgrade</code>, changing the database configuration for the LINSTOR Controller. Once again, ensure that you apply the
 chart version currently deployed, so that no accidental upgrade happens:</p>
@@ -2232,7 +2223,7 @@ <h3 id="4-update-the-linstor-configuration-to-point-to-the-new-database-backend"
 [db]
   connection_url = &quot;k8s&quot;
 </code></pre></div>
-<h3 id="5-import-the-database-from-the-backup">5. Import the Database from the Backup</h3>
+<h3 id="5-import-the-database-from-the-backup">5. Import the Database from the Backup<a class="headerlink" href="#5-import-the-database-from-the-backup" title="Permanent link">&para;</a></h3>
 <p>After changing the configuration, you can again use the <code>linstor-database</code> tool to restore the database backup to the
 new backend.</p>
 <div class="highlight"><pre><span></span><code>$ kubectl exec linstor-database-migration -- /usr/share/linstor-server/bin/linstor-database import-db -c /etc/linstor /backup/backup-before-migration.json
@@ -2249,7 +2240,7 @@ <h3 id="5-import-the-database-from-the-backup">5. Import the Database from the B
 15:39:43.307 [main] INFO LINSTOR/linstor-db -- SYSTEM - Kubernetes-CRD connection URL is &quot;k8s&quot;
 15:40:22.418 [main] INFO LINSTOR/linstor-db -- SYSTEM - Import finished
 </code></pre></div>
-<h3 id="6-start-the-linstor-controller">6. Start the LINSTOR Controller</h3>
+<h3 id="6-start-the-linstor-controller">6. Start the LINSTOR Controller<a class="headerlink" href="#6-start-the-linstor-controller" title="Permanent link">&para;</a></h3>
 <p>Now that the new database backend is initialized, it is safe to start the LINSTOR Controller again. Simply change the
 number of replicas for the LINSTOR Controller back to the original value before starting the migration. Once again,
 ensure that you apply the chart version currently deployed, so that no accidental upgrade happens:</p>
@@ -2263,7 +2254,7 @@ <h3 id="6-start-the-linstor-controller">6. Start the LINSTOR Controller</h3>
 $ kubectl exec deploy/piraeus-op-cs-controller -- linstor resource list-volumes
 $ kubectl exec deploy/piraeus-op-cs-controller -- linstor error-reports list
 </code></pre></div>
-<h3 id="7-clean-up-migration-resources">7. Clean up Migration Resources</h3>
+<h3 id="7-clean-up-migration-resources">7. Clean up Migration Resources<a class="headerlink" href="#7-clean-up-migration-resources" title="Permanent link">&para;</a></h3>
 <p>After successful migration, you can clean up left over resources.</p>
 <p>First, you can remove the <code>linstor-database-migration</code> Pod:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl delete pod linstor-database-migration
@@ -2309,7 +2300,7 @@ <h3 id="7-clean-up-migration-resources">7. Clean up Migration Resources</h3>
       <nav class="md-footer__inner md-grid" aria-label="Footer" >
         
           
-          <a href="../UPGRADE/" class="md-footer__link md-footer__link--prev" aria-label="Previous: Upgrading from v2 to v2">
+          <a href="../" class="md-footer__link md-footer__link--prev" aria-label="Previous: Upgrading from v1 to v2">
             <div class="md-footer__button md-icon">
               
               <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg>
@@ -2319,7 +2310,7 @@ <h3 id="7-clean-up-migration-resources">7. Clean up Migration Resources</h3>
                 Previous
               </span>
               <div class="md-ellipsis">
-                Upgrading from v2 to v2
+                Upgrading from v1 to v2
               </div>
             </div>
           </a>
diff --git a/v2.7.1/how-to/upgrade/2-collect-information/index.html b/v2.7.1/upgrade/migration/2-collect-information/index.html
similarity index 94%
rename from v2.7.1/how-to/upgrade/2-collect-information/index.html
rename to v2.7.1/upgrade/migration/2-collect-information/index.html
index d8ac3b2..be9f597 100644
--- a/v2.7.1/how-to/upgrade/2-collect-information/index.html
+++ b/v2.7.1/upgrade/migration/2-collect-information/index.html
@@ -6,13 +6,13 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
       
       
-        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/how-to/upgrade/2-collect-information/">
+        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/upgrade/migration/2-collect-information/">
       
       
         <link rel="prev" href="../1-migrate-database/">
@@ -63,9 +63,9 @@
       
         <meta  property="og:title"  content="Collect Information - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/2-collect-information.png" >
+        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/2-collect-information.png" >
       
         <meta  property="og:image:type"  content="image/png" >
       
@@ -73,15 +73,15 @@
       
         <meta  property="og:image:height"  content="630" >
       
-        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/how-to/upgrade/2-collect-information/" >
+        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/upgrade/migration/2-collect-information/" >
       
         <meta  name="twitter:card"  content="summary_large_image" >
       
         <meta  name="twitter:title"  content="Collect Information - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/2-collect-information.png" >
+        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/2-collect-information.png" >
       
     
     
@@ -305,7 +305,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../" class="md-tabs__link">
+        <a href="../../../how-to/" class="md-tabs__link">
           
   
     
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item md-tabs__item--active">
-        <a href="../" class="md-tabs__link">
+        <a href="../../" class="md-tabs__link">
           
   
     
@@ -634,7 +634,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../" class="md-nav__link ">
+            <a href="../../../how-to/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -715,7 +715,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../external-controller/" class="md-nav__link">
+      <a href="../../../how-to/external-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -736,7 +736,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-loader/" class="md-nav__link">
+      <a href="../../../how-to/drbd-loader/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -757,7 +757,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../install-kernel-headers/" class="md-nav__link">
+      <a href="../../../how-to/install-kernel-headers/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -836,7 +836,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../internal-tls/" class="md-nav__link">
+      <a href="../../../how-to/internal-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -857,7 +857,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../api-tls/" class="md-nav__link">
+      <a href="../../../how-to/api-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -878,7 +878,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-tls/" class="md-nav__link">
+      <a href="../../../how-to/drbd-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -899,7 +899,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../secure-boot/" class="md-nav__link">
+      <a href="../../../how-to/secure-boot/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -980,7 +980,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../openshift/" class="md-nav__link">
+      <a href="../../../how-to/openshift/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1001,7 +1001,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../talos/" class="md-nav__link">
+      <a href="../../../how-to/talos/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1022,7 +1022,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../flatcar/" class="md-nav__link">
+      <a href="../../../how-to/flatcar/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1043,7 +1043,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../microk8s/" class="md-nav__link">
+      <a href="../../../how-to/microk8s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1064,7 +1064,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../k0s/" class="md-nav__link">
+      <a href="../../../how-to/k0s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1141,7 +1141,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../http-proxy/" class="md-nav__link">
+      <a href="../../../how-to/http-proxy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1162,7 +1162,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../network-policy/" class="md-nav__link">
+      <a href="../../../how-to/network-policy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1183,7 +1183,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-host-networking/" class="md-nav__link">
+      <a href="../../../how-to/drbd-host-networking/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1260,7 +1260,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../monitoring/" class="md-nav__link">
+      <a href="../../../how-to/monitoring/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1281,7 +1281,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../linstor-affinity-controller/" class="md-nav__link">
+      <a href="../../../how-to/linstor-affinity-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1302,7 +1302,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../restore-linstor-db/" class="md-nav__link">
+      <a href="../../../how-to/restore-linstor-db/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1346,8 +1346,6 @@
           
         
       
-        
-      
         
       
     
@@ -1370,7 +1368,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../" class="md-nav__link ">
+            <a href="../../" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1400,27 +1398,6 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
     
   
   
@@ -1429,6 +1406,10 @@
     
       
         
+          
+        
+      
+        
       
         
       
@@ -1451,28 +1432,38 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" checked>
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" checked>
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="true">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="true">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
@@ -1970,23 +1961,23 @@
   
 
 
-<h1 id="collect-information-before-performing-the-upgrade">Collect Information before Performing the Upgrade</h1>
+<h1 id="collect-information-before-performing-the-upgrade">Collect Information before Performing the Upgrade<a class="headerlink" href="#collect-information-before-performing-the-upgrade" title="Permanent link">&para;</a></h1>
 <p>Before performing the upgrade and removing the old deployment, collect information on the state of your cluster.
 This ensures the upgraded deployment will have a compatible configuration.</p>
 <p>This is the second step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2).
 <a href="../">Click here to get back to the overview</a>.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://kubernetes.io/docs/tasks/tools/">Install <code>kubectl</code></a></li>
 <li><a href="https://docs.helm.sh/docs/intro/install/">Install <code>helm</code></a></li>
 <li><a href="https://jqlang.github.io/jq/download/">Install <code>jq</code></a></li>
 </ul>
-<h2 id="run-the-data-collection-script">Run the Data Collection Script</h2>
+<h2 id="run-the-data-collection-script">Run the Data Collection Script<a class="headerlink" href="#run-the-data-collection-script" title="Permanent link">&para;</a></h2>
 <p>To collect the necessary information for the migration, run the script provided at
-<code>docs/how-to/upgrade/collect-operator-v1-information.sh</code>. You can run the script either from a checked out repository,
+<code>docs/upgrade/migration/collect-operator-v1-information.sh</code>. You can run the script either from a checked out repository,
 or directly from GitHub:</p>
 <div class="highlight"><pre><span></span><code>$ curl --proto &#39;=https&#39; --tlsv1.2 -sSf \
-  https://raw.githubusercontent.com/piraeusdatastore/piraeus-operator/v2/docs/how-to/upgrade/collect-operator-v1-information.sh \
+  https://raw.githubusercontent.com/piraeusdatastore/piraeus-operator/v2/docs/upgrade/migration/collect-operator-v1-information.sh \
   | bash -s
 </code></pre></div>
 <p>The script will ask you if you want to keep modifications made with the deployed Piraeus Operator.
@@ -2030,7 +2021,7 @@ <h2 id="run-the-data-collection-script">Run the Data Collection Script</h2>
 ...
 </code></pre></div>
 <p>A copy of the identified resources is saved at <code>v2-resources.yaml</code>.</p>
-<h2 id="collect-helm-generated-secrets">Collect Helm-Generated Secrets</h2>
+<h2 id="collect-helm-generated-secrets">Collect Helm-Generated Secrets<a class="headerlink" href="#collect-helm-generated-secrets" title="Permanent link">&para;</a></h2>
 <p>Helm automatically generates a passphrase for LINSTOR. Once LINSTOR is initialized with the passphrase, the LINSTOR
 Controller will not be able fully start without supplying the passphrase.</p>
 <p>To migrate the generated passphrase to Piraeus Operator v2, create a backup of the secret:</p>
diff --git a/v2.7.1/how-to/upgrade/3-remove-operator-v1/index.html b/v2.7.1/upgrade/migration/3-remove-operator-v1/index.html
similarity index 94%
rename from v2.7.1/how-to/upgrade/3-remove-operator-v1/index.html
rename to v2.7.1/upgrade/migration/3-remove-operator-v1/index.html
index b54b7c6..baeac7a 100644
--- a/v2.7.1/how-to/upgrade/3-remove-operator-v1/index.html
+++ b/v2.7.1/upgrade/migration/3-remove-operator-v1/index.html
@@ -6,13 +6,13 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
       
       
-        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/how-to/upgrade/3-remove-operator-v1/">
+        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/upgrade/migration/3-remove-operator-v1/">
       
       
         <link rel="prev" href="../2-collect-information/">
@@ -63,9 +63,9 @@
       
         <meta  property="og:title"  content="Remove Operator v1 - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/3-remove-operator-v1.png" >
+        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/3-remove-operator-v1.png" >
       
         <meta  property="og:image:type"  content="image/png" >
       
@@ -73,15 +73,15 @@
       
         <meta  property="og:image:height"  content="630" >
       
-        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/how-to/upgrade/3-remove-operator-v1/" >
+        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/upgrade/migration/3-remove-operator-v1/" >
       
         <meta  name="twitter:card"  content="summary_large_image" >
       
         <meta  name="twitter:title"  content="Remove Operator v1 - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/3-remove-operator-v1.png" >
+        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/3-remove-operator-v1.png" >
       
     
     
@@ -305,7 +305,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../" class="md-tabs__link">
+        <a href="../../../how-to/" class="md-tabs__link">
           
   
     
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item md-tabs__item--active">
-        <a href="../" class="md-tabs__link">
+        <a href="../../" class="md-tabs__link">
           
   
     
@@ -634,7 +634,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../" class="md-nav__link ">
+            <a href="../../../how-to/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -715,7 +715,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../external-controller/" class="md-nav__link">
+      <a href="../../../how-to/external-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -736,7 +736,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-loader/" class="md-nav__link">
+      <a href="../../../how-to/drbd-loader/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -757,7 +757,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../install-kernel-headers/" class="md-nav__link">
+      <a href="../../../how-to/install-kernel-headers/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -836,7 +836,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../internal-tls/" class="md-nav__link">
+      <a href="../../../how-to/internal-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -857,7 +857,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../api-tls/" class="md-nav__link">
+      <a href="../../../how-to/api-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -878,7 +878,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-tls/" class="md-nav__link">
+      <a href="../../../how-to/drbd-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -899,7 +899,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../secure-boot/" class="md-nav__link">
+      <a href="../../../how-to/secure-boot/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -980,7 +980,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../openshift/" class="md-nav__link">
+      <a href="../../../how-to/openshift/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1001,7 +1001,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../talos/" class="md-nav__link">
+      <a href="../../../how-to/talos/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1022,7 +1022,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../flatcar/" class="md-nav__link">
+      <a href="../../../how-to/flatcar/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1043,7 +1043,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../microk8s/" class="md-nav__link">
+      <a href="../../../how-to/microk8s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1064,7 +1064,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../k0s/" class="md-nav__link">
+      <a href="../../../how-to/k0s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1141,7 +1141,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../http-proxy/" class="md-nav__link">
+      <a href="../../../how-to/http-proxy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1162,7 +1162,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../network-policy/" class="md-nav__link">
+      <a href="../../../how-to/network-policy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1183,7 +1183,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-host-networking/" class="md-nav__link">
+      <a href="../../../how-to/drbd-host-networking/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1260,7 +1260,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../monitoring/" class="md-nav__link">
+      <a href="../../../how-to/monitoring/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1281,7 +1281,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../linstor-affinity-controller/" class="md-nav__link">
+      <a href="../../../how-to/linstor-affinity-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1302,7 +1302,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../restore-linstor-db/" class="md-nav__link">
+      <a href="../../../how-to/restore-linstor-db/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1346,8 +1346,6 @@
           
         
       
-        
-      
         
       
     
@@ -1370,7 +1368,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../" class="md-nav__link ">
+            <a href="../../" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1400,27 +1398,6 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
     
   
   
@@ -1429,6 +1406,10 @@
     
       
         
+          
+        
+      
+        
       
         
       
@@ -1451,28 +1432,38 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" checked>
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" checked>
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="true">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="true">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
@@ -2024,24 +2015,24 @@
   
 
 
-<h1 id="remove-the-piraeus-operator-v1-deployment">Remove the Piraeus Operator v1 Deployment</h1>
+<h1 id="remove-the-piraeus-operator-v1-deployment">Remove the Piraeus Operator v1 Deployment<a class="headerlink" href="#remove-the-piraeus-operator-v1-deployment" title="Permanent link">&para;</a></h1>
 <p>Migrating to the new Piraeus Operator deployment requires temporarily removing the existing deployment.</p>
 <p>After this step no new volumes can be created and no existing volume can be attached or detached, until the
 new deployment is rolled out.</p>
 <p>This is the third step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2).
 <a href="../">Click here to get back to the overview</a>.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://kubernetes.io/docs/tasks/tools/">Install <code>kubectl</code></a></li>
 <li><a href="https://docs.helm.sh/docs/intro/install/">Install <code>helm</code></a></li>
 </ul>
-<h2 id="scale-down-the-operator-deployment">Scale Down the Operator Deployment</h2>
+<h2 id="scale-down-the-operator-deployment">Scale Down the Operator Deployment<a class="headerlink" href="#scale-down-the-operator-deployment" title="Permanent link">&para;</a></h2>
 <p>To prevent modification of the existing cluster, scale down the existing Piraeus Operator deployment.</p>
 <div class="highlight"><pre><span></span><code>$ helm upgrade piraeus-op ./charts/piraeus --set operator.replicas=0
 $ kubectl rollout status -w deploy/piraeus-op-operator
 deployment &quot;piraeus-op-operator&quot; successfully rolled out
 </code></pre></div>
-<h2 id="remove-the-finalizers-from-the-piraeus-resources">Remove the Finalizers from the Piraeus Resources</h2>
+<h2 id="remove-the-finalizers-from-the-piraeus-resources">Remove the Finalizers from the Piraeus Resources<a class="headerlink" href="#remove-the-finalizers-from-the-piraeus-resources" title="Permanent link">&para;</a></h2>
 <p>The Operator sets Finalizers on the resource it controls. This prevents the deletion of these resources when the
 Operator is not running. Remove the Finalizers by applying a patch:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl patch linstorsatellitesets piraeus-op-ns --type merge --patch &#39;{&quot;metadata&quot;: {&quot;finalizers&quot;: []}}&#39;
@@ -2049,7 +2040,7 @@ <h2 id="remove-the-finalizers-from-the-piraeus-resources">Remove the Finalizers
 $ kubectl patch linstorcontrollers piraeus-op-cs --type merge --patch &#39;{&quot;metadata&quot;: {&quot;finalizers&quot;: []}}&#39;
 linstorcontroller.piraeus.linbit.com/piraeus-op-cs patched
 </code></pre></div>
-<h2 id="remove-the-piraeus-resources">Remove the Piraeus Resources</h2>
+<h2 id="remove-the-piraeus-resources">Remove the Piraeus Resources<a class="headerlink" href="#remove-the-piraeus-resources" title="Permanent link">&para;</a></h2>
 <p>Having removed the Finalizers, you can delete the Piraeus Resources. This will stop the LINSTOR Cluster, and no
 new volumes can be created, and existing volumes will not attach or detach. Volumes already attached to a Pod will
 continue to replicate.</p>
@@ -2057,13 +2048,13 @@ <h2 id="remove-the-piraeus-resources">Remove the Piraeus Resources</h2>
 $ kubectl delete linstorsatellitesets/piraeus-op-ns
 $ kubectl delete linstorcontrollers/piraeus-op-cs
 </code></pre></div>
-<h2 id="remove-the-piraeus-deployment">Remove the Piraeus Deployment</h2>
+<h2 id="remove-the-piraeus-deployment">Remove the Piraeus Deployment<a class="headerlink" href="#remove-the-piraeus-deployment" title="Permanent link">&para;</a></h2>
 <p>As a last step, you can completely remove the helm deployment, deleting additional resources such as service accounts
 and RBAC resources. In addition, also clean up the Custom Resource Definitions:</p>
 <div class="highlight"><pre><span></span><code>$ helm uninstall piraeus-op
 $ kubectl delete crds linstorcsidrivers.piraeus.linbit.com linstorsatellitesets.piraeus.linbit.com linstorcontrollers.piraeus.linbit.com
 </code></pre></div>
-<h2 id="optional-remove-additional-piraeus-components">Optional: Remove additional Piraeus Components</h2>
+<h2 id="optional-remove-additional-piraeus-components">Optional: Remove additional Piraeus Components<a class="headerlink" href="#optional-remove-additional-piraeus-components" title="Permanent link">&para;</a></h2>
 <p>If you have deployed additional components from Piraeus, such as the HA Controller or LINSTOR Affinity Controller, you
 will need to remove them, too. After completing the migration, you can install them again, if needed.</p>
 <div class="highlight"><pre><span></span><code>$ helm uninstall piraeus-ha-controller
diff --git a/v2.7.1/how-to/upgrade/4-install-operator-v2/index.html b/v2.7.1/upgrade/migration/4-install-operator-v2/index.html
similarity index 94%
rename from v2.7.1/how-to/upgrade/4-install-operator-v2/index.html
rename to v2.7.1/upgrade/migration/4-install-operator-v2/index.html
index fe61181..61b7796 100644
--- a/v2.7.1/how-to/upgrade/4-install-operator-v2/index.html
+++ b/v2.7.1/upgrade/migration/4-install-operator-v2/index.html
@@ -6,13 +6,13 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
       
       
-        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/how-to/upgrade/4-install-operator-v2/">
+        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/upgrade/migration/4-install-operator-v2/">
       
       
         <link rel="prev" href="../3-remove-operator-v1/">
@@ -63,9 +63,9 @@
       
         <meta  property="og:title"  content="Install Operator v2 - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/4-install-operator-v2.png" >
+        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/4-install-operator-v2.png" >
       
         <meta  property="og:image:type"  content="image/png" >
       
@@ -73,15 +73,15 @@
       
         <meta  property="og:image:height"  content="630" >
       
-        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/how-to/upgrade/4-install-operator-v2/" >
+        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/upgrade/migration/4-install-operator-v2/" >
       
         <meta  name="twitter:card"  content="summary_large_image" >
       
         <meta  name="twitter:title"  content="Install Operator v2 - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/4-install-operator-v2.png" >
+        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/4-install-operator-v2.png" >
       
     
     
@@ -305,7 +305,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../../" class="md-tabs__link">
+        <a href="../../../how-to/" class="md-tabs__link">
           
   
     
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item md-tabs__item--active">
-        <a href="../" class="md-tabs__link">
+        <a href="../../" class="md-tabs__link">
           
   
     
@@ -634,7 +634,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../../" class="md-nav__link ">
+            <a href="../../../how-to/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -715,7 +715,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../external-controller/" class="md-nav__link">
+      <a href="../../../how-to/external-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -736,7 +736,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-loader/" class="md-nav__link">
+      <a href="../../../how-to/drbd-loader/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -757,7 +757,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../install-kernel-headers/" class="md-nav__link">
+      <a href="../../../how-to/install-kernel-headers/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -836,7 +836,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../internal-tls/" class="md-nav__link">
+      <a href="../../../how-to/internal-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -857,7 +857,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../api-tls/" class="md-nav__link">
+      <a href="../../../how-to/api-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -878,7 +878,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-tls/" class="md-nav__link">
+      <a href="../../../how-to/drbd-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -899,7 +899,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../secure-boot/" class="md-nav__link">
+      <a href="../../../how-to/secure-boot/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -980,7 +980,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../openshift/" class="md-nav__link">
+      <a href="../../../how-to/openshift/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1001,7 +1001,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../talos/" class="md-nav__link">
+      <a href="../../../how-to/talos/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1022,7 +1022,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../flatcar/" class="md-nav__link">
+      <a href="../../../how-to/flatcar/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1043,7 +1043,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../microk8s/" class="md-nav__link">
+      <a href="../../../how-to/microk8s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1064,7 +1064,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../k0s/" class="md-nav__link">
+      <a href="../../../how-to/k0s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1141,7 +1141,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../http-proxy/" class="md-nav__link">
+      <a href="../../../how-to/http-proxy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1162,7 +1162,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../network-policy/" class="md-nav__link">
+      <a href="../../../how-to/network-policy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1183,7 +1183,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../drbd-host-networking/" class="md-nav__link">
+      <a href="../../../how-to/drbd-host-networking/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1260,7 +1260,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../monitoring/" class="md-nav__link">
+      <a href="../../../how-to/monitoring/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1281,7 +1281,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../linstor-affinity-controller/" class="md-nav__link">
+      <a href="../../../how-to/linstor-affinity-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1302,7 +1302,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../../restore-linstor-db/" class="md-nav__link">
+      <a href="../../../how-to/restore-linstor-db/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1346,8 +1346,6 @@
           
         
       
-        
-      
         
       
     
@@ -1370,7 +1368,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../" class="md-nav__link ">
+            <a href="../../" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1400,27 +1398,6 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="../UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
-  
     
   
   
@@ -1429,6 +1406,10 @@
     
       
         
+          
+        
+      
+        
       
         
       
@@ -1451,28 +1432,38 @@
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" checked>
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" checked>
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="../" class="md-nav__link ">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link " for="__nav_4_2" id="__nav_4_2_label" tabindex="">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="true">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="true">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
@@ -2006,17 +1997,17 @@
   
 
 
-<h1 id="install-piraeus-operator-v2">Install Piraeus Operator v2</h1>
+<h1 id="install-piraeus-operator-v2">Install Piraeus Operator v2<a class="headerlink" href="#install-piraeus-operator-v2" title="Permanent link">&para;</a></h1>
 <p>After removing the Piraeus Operator v1 deployment, you can install Piraeus Operator v2.</p>
 <p>You can either use the <code>kubectl</code> method to deploy Piraeus Operator, or alternatively deploy the Operator using Helm.</p>
 <p>This is the last step when migrating Piraeus Operator from version 1 (v1) to version 2 (v2).
 <a href="../">Click here to get back to the overview</a>.</p>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <ul>
 <li><a href="https://kubernetes.io/docs/tasks/tools/">Install <code>kubectl</code></a></li>
 <li><a href="https://docs.helm.sh/docs/intro/install/">Install <code>helm</code></a></li>
 </ul>
-<h2 id="deploy-piraeus-operator-v2-using-kubectl">Deploy Piraeus Operator v2 Using <code>kubectl</code></h2>
+<h2 id="deploy-piraeus-operator-v2-using-kubectl">Deploy Piraeus Operator v2 Using <code>kubectl</code><a class="headerlink" href="#deploy-piraeus-operator-v2-using-kubectl" title="Permanent link">&para;</a></h2>
 <p>You can use <code>kubectl</code> and the built-in <code>kustomize</code> feature to deploy Piraeus Operator v2.</p>
 <p>First, create a file named <code>kustomization.yaml</code>, referencing the latest Piraeus Operator release, and the
 namespace you which to deploy the Piraeus Operator in. The latest releases are available  on the <a href="https://github.com/piraeusdatastore/piraeus-operator/releases">release page</a>.</p>
@@ -2031,7 +2022,7 @@ <h2 id="deploy-piraeus-operator-v2-using-kubectl">Deploy Piraeus Operator v2 Usi
 <div class="highlight"><pre><span></span><code>$ kubectl apply -k . --server-side
 $ kubectl rollout status -n piraeus-datastore -w deploy/piraeus-operator-controller-manager
 </code></pre></div>
-<h2 id="deploy-piraeus-operator-v2-using-helm">Deploy Piraeus Operator v2 Using Helm</h2>
+<h2 id="deploy-piraeus-operator-v2-using-helm">Deploy Piraeus Operator v2 Using Helm<a class="headerlink" href="#deploy-piraeus-operator-v2-using-helm" title="Permanent link">&para;</a></h2>
 <p>To deploy Piraeus Operator v2 using Helm, clone the latest v2 release of Piraeus. The latest releases are available
 on the <a href="https://github.com/piraeusdatastore/piraeus-operator/releases">release page</a>.</p>
 <p>To also install the necessary Custom Resource Definitions for Piraeus, set <code>installCRDs</code> to <code>true</code>.</p>
@@ -2039,7 +2030,7 @@ <h2 id="deploy-piraeus-operator-v2-using-helm">Deploy Piraeus Operator v2 Using
 $ cd piraeus-operator
 $ helm install piraeus-operator charts/piraeus --set installCRDs=true
 </code></pre></div>
-<h2 id="deploy-the-piraeus-datastore-cluster">Deploy the Piraeus Datastore Cluster</h2>
+<h2 id="deploy-the-piraeus-datastore-cluster">Deploy the Piraeus Datastore Cluster<a class="headerlink" href="#deploy-the-piraeus-datastore-cluster" title="Permanent link">&para;</a></h2>
 <p>Once the Operator is deployed, deploy the Cluster using the generated resources from <a href="../2-collect-information/#run-the-data-collection-script">step 2</a>.</p>
 <p>First, create the secret used for the LINSTOR passphrase collected at the <a href="../2-collect-information/#collect-helm-generated-secrets">end of step 2</a>.</p>
 <div class="highlight"><pre><span></span><code>$ cat &lt;&lt;-EOF | kubectl apply -f - --server-side
@@ -2059,7 +2050,7 @@ <h2 id="deploy-the-piraeus-datastore-cluster">Deploy the Piraeus Datastore Clust
 linstorsatelliteconfiguration.piraeus.io/piraeus-op-ns created
 </code></pre></div>
 <p>Now the cluster will come up, using the existing data to restore the cluster state.</p>
-<h2 id="verifying-cluster-state">Verifying Cluster State</h2>
+<h2 id="verifying-cluster-state">Verifying Cluster State<a class="headerlink" href="#verifying-cluster-state" title="Permanent link">&para;</a></h2>
 <p>You can check the Cluster state by using the <code>linstor</code> command line client:</p>
 <div class="highlight"><pre><span></span><code>$ kubectl exec deploy/linstor-controller -- linstor node list
 $ kubectl exec deploy/linstor-controller -- linstor storage-pool list
diff --git a/v2.7.1/upgrade/migration/collect-operator-v1-information.sh b/v2.7.1/upgrade/migration/collect-operator-v1-information.sh
new file mode 100644
index 0000000..616a7bd
--- /dev/null
+++ b/v2.7.1/upgrade/migration/collect-operator-v1-information.sh
@@ -0,0 +1,618 @@
+#!/usr/bin/env bash
+
+set -eo pipefail
+
+if [ -n "$V" ]; then
+	set -x
+fi
+
+# Change to the root of the repository
+if [ -n "${BASH_SOURCE[0]}" ]; then
+	SCRIPT_DIR="$( cd -- "$( dirname -- "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"
+	cd "$SCRIPT_DIR/../../.."
+fi
+
+# Print the provided error message and exit with exit-code set to 1
+die() {
+	echo "$@" >&2
+	exit 1
+}
+
+# Read the json value from STDIN and format it as a patch for kustomization to STDOUT
+#
+# Takes three parameters:
+# * The kind of the resource that is patched
+# * The name of the resource that is patched
+# * The jq expression that converts STDIN into either a strategic merge patch (i.e. partial Kubernetes resource) or
+#   a RFC 6902 JSON patch
+#
+# Example:
+# $ echo '{"replicas": 3}' | format_patch Deployment example '{"spec": {"replicas" .replicas}}'
+# {
+#  "target": {
+#    "kind": "Deployment",
+#    "name": "example"
+#  },
+#  "patch": "{\"spec\":{\"replicas\":3}}"
+#}
+format_patch() {
+	local KIND="$1"
+	local NAME="$2"
+	local EXPR="$3"
+	jq --arg KIND "$KIND" --arg NAME "$NAME" "$EXPR | {\"target\": {\"kind\": \$KIND, \"name\": \$NAME}, \"patch\": (. | tostring) }"
+}
+
+# Append the kustomize patch from STDIN to the kustomize configuration in the provided directory.
+# This will write the updated kustomization.yaml to STDOUT
+append_patch() {
+	jq -s --slurpfile KUSTOMIZATION "$1/kustomization.yaml" '. as $INPUT | $KUSTOMIZATION[0] | .patches += $INPUT'
+}
+
+# Compare the kustomization read from STDIN to the one provided in the first argument.
+#
+# This will print a diff of the read kustomization to the one read from the provided directory.
+#
+# The optional second argument is used when displaying the patch: instead of diffing the output of the two
+# kustomizations, diff the result of applying the patches to the Operator resources.
+#
+# Afterwards, there will be a temporary "KUSTOMIZATION.tmp", holding an updated copy of the directory provided in
+# the first argument.
+diff_patch() {
+	local KUSTOMIZATION="$1"
+	local OPERATOR_RESOURCE="$2"
+
+	# Make of copy of the existing kustomization and update it with the new value read from STDIN.
+	cp -a "$KUSTOMIZATION" "$KUSTOMIZATION.tmp"
+	cat > "$KUSTOMIZATION.tmp/kustomization.yaml"
+
+	if [ -n "$OPERATOR_SOURCE" ] && [ -n "$OPERATOR_RESOURCE" ]; then
+		# The patch we got only adds a "spec.patches" entry on the resulting resource: Instead of displaying the additional
+		# entry, we show the result of applying this added patch to the Operator resources
+		mkdir "$KUSTOMIZATION.tmp/old" "$KUSTOMIZATION.tmp/new"
+		# Create new kustomizations, using only the .spec.patches and apply them to the raw Operator resources
+		jq -r '.patches[].patch' "$KUSTOMIZATION/kustomization.yaml" \
+		  | jq '.[] | select(.path == "/spec/patches/-") | .value' \
+		  | jq --slurp --arg RESOURCES "../../../$OPERATOR_SOURCE/$OPERATOR_RESOURCE" '{"resources": [$RESOURCES], "patches": .}' > "$KUSTOMIZATION.tmp/old/kustomization.yaml"
+		jq -r '.patches[].patch' "$KUSTOMIZATION.tmp/kustomization.yaml" \
+		  | jq '.[] | select(.path == "/spec/patches/-") | .value' \
+		  | jq --slurp --arg RESOURCES "../../../$OPERATOR_SOURCE/$OPERATOR_RESOURCE" '{"resources": [$RESOURCES], "patches": .}' > "$KUSTOMIZATION.tmp/new/kustomization.yaml"
+		# Render the result of comparing the kustomizations on the Operator resources
+		diff --unified --label "Default resource" --label "Updated resource" --show-function-line='^kind:' <(kubectl kustomize "$KUSTOMIZATION.tmp/old") <(kubectl kustomize "$KUSTOMIZATION.tmp/new") || true
+	else
+		# Just render the new kustomization and compare it to the existing one
+		diff --unified --label "Default resource" --label "Updated resource" --show-function-line='^kind:' <(kubectl kustomize "$KUSTOMIZATION") <(kubectl kustomize "$KUSTOMIZATION.tmp") || true
+	fi
+}
+
+# Ask the user to confirm or discard a proposed change
+#
+# This assumes that diff_patch was called previously, so in addition to the directory provided in the first argument,
+# there is the updated copy located at "$DIRECTORY.tmp".
+#
+# The second argument is the default argument if the user does not provide any input, either "n" or "y".
+confirm_patch() {
+	if [ "$2" == y ]; then
+		YN="Y/n"
+	else
+		YN="y/N"
+	fi
+
+	while true; do
+		read -rp "Apply the patch ($YN)? " CHOICE < "$READ_FROM" || true
+		case "${CHOICE:-$2}" in
+			y|Y )
+				mv "$1.tmp/kustomization.yaml" "$1/kustomization.yaml"
+				break
+				;;
+			n|N )
+				break
+				;;
+			* )
+				;;
+		esac
+	done
+
+	rm -rf "$1.tmp"
+}
+
+# Fetch the sources for the operator so diffing shows useful results
+get_sources() {
+	if [ -d pkg/resources/cluster/controller ] && [ -d pkg/resources/cluster/csi-controller ] && [ -d pkg/resources/cluster/csi-node ] && [ -d pkg/resources/satellite/satellite ]; then
+		echo "."
+		return
+	fi
+
+	if ! command -v curl >/dev/null ; then
+		echo "Could not find optional tool \"curl\", cannot show rich diffs." >&2
+		return
+	fi
+
+	if ! command -v tar >/dev/null ; then
+		echo "Could not find optional tool \"tar\", cannot show rich diffs." >&2
+		return
+	fi
+
+	if curl -fsSL https://github.com/piraeusdatastore/piraeus-operator/archive/refs/heads/v2.tar.gz | tar -xzC "$1" 2>/dev/null ; then
+		echo "$1/piraeus-operator-2"
+	else
+		echo "Could not download operator sources, not showing rich diffs." >&2
+	fi
+}
+
+### Step 1: Sanity checks
+
+if ! command -v kubectl >/dev/null ; then
+	die Could not find required tool \"kubectl\"
+fi
+
+if ! command -v jq >/dev/null ; then
+	die Could not find required tool \"jq\"
+fi
+
+echo "Using kubectl context: $(kubectl config current-context)"
+
+TEMPDIR="$(mktemp -d .v1-information.XXXXXX)"
+if [ -n "$KEEP_TMP" ]; then
+	echo "TEMPDIR: $TEMPDIR"
+else
+	trap 'rm -rf "$TEMPDIR"' EXIT
+fi
+
+OPERATOR_SOURCE="${OPERATOR_SOURCE:-$(get_sources "$TEMPDIR")}"
+READ_FROM=/dev/stdin
+if [ ! -t 0 ] && [ -e /dev/tty ]; then
+	READ_FROM=/dev/tty
+fi
+
+mkdir -p "$TEMPDIR/linstorcluster" "$TEMPDIR/linstorsatelliteconfiguration"
+
+if ! kubectl get linstorcontrollers -A -ojson > "$TEMPDIR/linstorcontrollers.json" ; then
+	die "No LinstorController API available, are you sure kubectl points at the right cluster?"
+fi
+
+if ! kubectl get linstorsatellitesets -A -ojson > "$TEMPDIR/linstorsatellitesets.json" ; then
+	die "No LinstorSatelliteSet API available, are you sure kubectl points at the right cluster?"
+fi
+
+if ! kubectl get linstorcsidrivers -A -ojson > "$TEMPDIR/linstorcsidrivers.json" ; then
+	die "No LinstorCSIDriver API available, are you sure kubectl points at the right cluster?"
+fi
+
+echo "Found LinstorControllers: $(jq -c '.items | map(.metadata.name)' $TEMPDIR/linstorcontrollers.json)"
+NR_CONTROLLERS="$(jq '.items | length' $TEMPDIR/linstorcontrollers.json)"
+if [ "$NR_CONTROLLERS" -ne 1 ]; then
+	die "Expected exactly one LinstorController resource, got $NR_CONTROLLERS"
+fi
+
+echo "Found LinstorSatelliteSets: $(jq -c '.items | map(.metadata.name)' $TEMPDIR/linstorsatellitesets.json)"
+NR_SATELLITESETS="$(jq '.items | length' $TEMPDIR/linstorsatellitesets.json)"
+if [ "$NR_SATELLITESETS" -lt 1 ]; then
+	die "Expected at least one LinstorSatelliteSets resource, got $NR_SATELLITESETS"
+fi
+
+echo "Found LinstorCSIDrivers: $(jq -c '.items | map(.metadata.name)' $TEMPDIR/linstorcsidrivers.json)"
+NR_LINSTOR_CSI_DRIVERS="$(jq '.items | length' $TEMPDIR/linstorcsidrivers.json)"
+if [ "$NR_LINSTOR_CSI_DRIVERS" -ne 1 ]; then
+	die "Expected exactly one LinstorCSIDriver resource, got $NR_LINSTOR_CSI_DRIVERS"
+fi
+
+EXPECTED_CONTROLLER_ENDPOINT="http://$(jq -r '.items[0].metadata.name' "$TEMPDIR/linstorcontrollers.json").$(jq -r '.items[0].metadata.namespace' "$TEMPDIR/linstorcontrollers.json").svc:3370"
+
+jq -n '{"apiVersion": "piraeus.io/v1", "kind": "LinstorCluster", "metadata": {"name": "linstorcluster"}, "spec": {"patches": []}}' > "$TEMPDIR/linstorcluster/linstorcluster.yaml"
+jq -n '{"apiVersion": "kustomize.config.k8s.io/v1beta1", "kind": "Kustomization", "resources": ["linstorcluster.yaml"], "patches": []}' > "$TEMPDIR/linstorcluster/kustomization.yaml"
+jq -n '{"apiVersion": "kustomize.config.k8s.io/v1beta1", "kind": "Kustomization", "resources": [], "patches": []}' > "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml"
+jq -n '{"apiVersion": "kustomize.config.k8s.io/v1beta1", "kind": "Kustomization", "resources": ["linstorcluster", "linstorsatelliteconfiguration"]}' > "$TEMPDIR/kustomization.yaml"
+
+if [ "$(jq '.items[0].spec.additionalEnv | length' "$TEMPDIR/linstorcontrollers.json")" -gt 0 ]; then
+	echo "Found additional environment variables passed to LINSTOR Controller"
+	jq '.items[0].spec.additionalEnv' "$TEMPDIR/linstorcontrollers.json" \
+	  | format_patch Deployment linstor-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-controller"}, "spec": {"template": {"spec": {"containers": [{"name": "linstor-controller", "env": .}]}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/controller
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ "$(jq '.items[0].spec.additionalProperties | length' "$TEMPDIR/linstorcontrollers.json")" -gt 0 ]; then
+	echo "Found additional properties configured on LINSTOR Controller"
+	jq '.items[0].spec.additionalProperties | to_entries | map({"name": .key, "value": .value})' "$TEMPDIR/linstorcontrollers.json" \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/properties", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster"
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ "$(jq '.items[0].spec.affinity | length' "$TEMPDIR/linstorcontrollers.json")" -gt 0 ]; then
+	echo "Found custom affinity set on LINSTOR Controller"
+	jq '.items[0].spec.affinity' "$TEMPDIR/linstorcontrollers.json" \
+		| format_patch Deployment linstor-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-controller"}, "spec": {"template": {"spec": {"affinity": . }}}}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq -r '.items[0].spec.dbConnectionURL' "$TEMPDIR/linstorcontrollers.json")" != "k8s" ]; then
+	echo "Found custom LINSTOR Controller Database connection"
+	printf '[db]\n  connection_url = "%s"\n' "$(jq -r '.items[0].spec.dbConnectionURL' "$TEMPDIR/linstorcontrollers.json")" \
+		| jq --raw-input --slurp . \
+		| format_patch ConfigMap linstor-controller-config '{"apiVersion": "v1", "kind": "ConfigMap", "metadata": {"name": "linstor-controller-config"}, "data": {"linstor.toml": .}}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/controller
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ "$(jq -r '.items[0].spec.extraVolumes | length' "$TEMPDIR/linstorcontrollers.json")" -gt 0 ]; then
+	echo "Found extra volumes for LINSTOR Controller Pod"
+	jq '.items[0].spec.extraVolumes' "$TEMPDIR/linstorcontrollers.json" \
+		| format_patch Deployment linstor-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-controller"}, "spec": {"template": {"spec": {"volumes": . }}}}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ -n "$(jq -r '.items[0].spec.linstorHttpsClientSecret' "$TEMPDIR/linstorcontrollers.json")" ] || [ -n "$(jq -r '.items[0].spec.linstorHttpsControllerSecret' "$TEMPDIR/linstorcontrollers.json")" ]; then
+	echo "Found LINSTOR Controller HTTPS configuration"
+	EXPECTED_CONTROLLER_ENDPOINT="https://$(jq -r '.items[0].metadata.name' "$TEMPDIR/linstorcontrollers.json").$(jq -r '.items[0].metadata.namespace' "$TEMPDIR/linstorcontrollers.json").svc:3371"
+	jq '{"clientSecretName": .items[0].spec.linstorHttpsClientSecret, "apiSecretName": .items[0].spec.linstorHttpsControllerSecret}' "$TEMPDIR/linstorcontrollers.json" \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/apiTLS", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster"
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ -n "$(jq -r '.items[0].spec.luksSecret' "$TEMPDIR/linstorcontrollers.json")" ]; then
+	echo "Found LINSTOR Controller passphrase secret"
+	jq '.items[0].spec.luksSecret' "$TEMPDIR/linstorcontrollers.json" \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/linstorPassphraseSecret", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster"
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ "$(jq -r '.items[0].spec.sidecars | length' "$TEMPDIR/linstorcontrollers.json")" -gt 0 ]; then
+	echo "Found LINSTOR Controller sidecars"
+	jq '.items[0].spec.sidecars' "$TEMPDIR/linstorcontrollers.json" \
+		| format_patch Deployment linstor-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-controller"}, "spec": {"template": {"spec": {"containers": .}}}}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ -n "$(jq -r '.items[0].spec.sslSecret // ""' "$TEMPDIR/linstorcontrollers.json")" ]; then
+	echo "Found LINSTOR Controller internal TLS configuration"
+	jq '{"secretName": .items[0].spec.sslSecret}' "$TEMPDIR/linstorcontrollers.json" \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/internalTLS", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster"
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ -n "$(jq -r '.items[0].spec.tolerations' "$TEMPDIR/linstorcontrollers.json")" ]; then
+	echo "Found LINSTOR Controller Pod tolerations"
+	jq '.items[0].spec.tolerations' "$TEMPDIR/linstorcontrollers.json" \
+		| format_patch Deployment linstor-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-controller"}, "spec": {"template": {"spec": {"tolerations": .}}}}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+### Check LinstorCSIDriver
+
+if [ "$(jq '.items[0].spec.controllerAffinity | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found custom affinity set on LINSTOR CSI Controller"
+	jq '.items[0].spec.controllerAffinity' "$TEMPDIR/linstorcsidrivers.json" \
+		| format_patch Deployment linstor-csi-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-csi-controller"}, "spec": {"template": {"spec": {"affinity": . }}}}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq '.items[0].spec.controllerReplicas' "$TEMPDIR/linstorcsidrivers.json")" -ne 1 ] || [ "$(jq '.items[0].spec.controllerStrategy | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found custom replica settings for LINSTOR CSI Controller"
+	jq '{"replicas": .items[0].spec.controllerReplicas, "strategy": .items[0].spec.controllerStrategy}' "$TEMPDIR/linstorcsidrivers.json" \
+		| format_patch Deployment linstor-csi-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-csi-controller"}, "spec": .}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-controller
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ "$(jq '.items[0].spec.controllerTolerations | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found custom tolerations for LINSTOR CSI Controller"
+	jq '.items[0].spec.controllerTolerations' "$TEMPDIR/linstorcsidrivers.json" \
+		| format_patch Deployment linstor-csi-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-csi-controller"}, "spec": {"template": {"spec": {"tolerations": .}}}}' \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq '.items[0].spec.extraVolumes | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found additional volumes for LINSTOR CSI Controller"
+	jq '.items[0].spec.extraVolumes' "$TEMPDIR/linstorcsidrivers.json" \
+	  | format_patch Deployment linstor-csi-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-csi-controller"}, "spec": {"template": {"spec": {"volumes": .}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq '.items[0].spec.sidecars | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found additional containers for LINSTOR CSI Controller"
+	jq '.items[0].spec.sidecars' "$TEMPDIR/linstorcsidrivers.json" \
+	  | format_patch Deployment linstor-csi-controller '{"apiVersion": "apps/v1", "kind": "Deployment", "metadata": {"name": "linstor-csi-controller"}, "spec": {"template": {"spec": {"containers": .}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-controller
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq -r '.items[0].spec.kubeletPath' "$TEMPDIR/linstorcsidrivers.json")" != "/var/lib/kubelet" ]; then
+	echo "Found non-standard kubelet path"
+	jq '.items[0].spec.kubeletPath' "$TEMPDIR/linstorcsidrivers.json" \
+	  | format_patch DaemonSet linstor-csi-node '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-csi-node"}, "spec": {"template": {"spec": {"containers": [{"name": "linstor-csi", "volumeMounts": [{"name": "publish-dir", "mountPath": "/var/lib/kubelet", "$patch": "delete"}, {"name": "publish-dir", "mountPath": ., "mountPropagation": "Bidirectional"}]}]}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-node
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ -n "$(jq -r '.items[0].spec.linstorHttpsClientSecret' "$TEMPDIR/linstorcsidrivers.json")" ]; then
+	echo "Found LINSTOR CSI Client HTTPS configuration"
+	jq '.items[0].spec.linstorHttpsClientSecret' "$TEMPDIR/linstorcsidrivers.json" \
+		| format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/apiTLS/csiControllerSecretName", "value": .}, {"op": "add", "path": "/spec/apiTLS/csiNodeSecretName", "value": .}]' \
+		| append_patch "$TEMPDIR/linstorcluster" \
+		| diff_patch "$TEMPDIR/linstorcluster"
+	confirm_patch "$TEMPDIR/linstorcluster" y
+fi
+
+if [ "$(jq '.items[0].spec.nodeAffinity | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found custom affinity set on LINSTOR CSI Nodes"
+	jq '.items[0].spec.nodeAffinity' "$TEMPDIR/linstorcsidrivers.json" \
+	  | format_patch DaemonSet linstor-csi-node '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-csi-node"}, "spec": {"template": {"spec": {"affinity": .}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-node
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq '.items[0].spec.nodeExtraVolumes | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found additional volumes for LINSTOR CSI Nodes"
+	jq '.items[0].spec.nodeExtraVolumes' "$TEMPDIR/linstorcsidrivers.json" \
+	  | format_patch DaemonSet linstor-csi-node '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-csi-node"}, "spec": {"template": {"spec": {"volumes": .}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-node
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq '.items[0].spec.nodeSidecars | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found additional containers for LINSTOR CSI Nodes"
+	jq '.items[0].spec.nodeSidecars' "$TEMPDIR/linstorcsidrivers.json" \
+	  | format_patch DaemonSet linstor-csi-node '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-csi-node"}, "spec": {"template": {"spec": {"containers": .}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-node
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+if [ "$(jq '.items[0].spec.nodeTolerations | length' "$TEMPDIR/linstorcsidrivers.json")" -gt 0 ]; then
+	echo "Found custom tolerations for LINSTOR CSI Nodes"
+	jq '.items[0].spec.nodeTolerations' "$TEMPDIR/linstorcsidrivers.json" \
+	  | format_patch DaemonSet linstor-csi-node '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-csi-node"}, "spec": {"template": {"spec": {"tolerations": .}}}}' \
+	  | format_patch LinstorCluster linstorcluster '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+	  | append_patch "$TEMPDIR/linstorcluster" \
+	  | diff_patch "$TEMPDIR/linstorcluster" pkg/resources/cluster/csi-node
+	confirm_patch "$TEMPDIR/linstorcluster" n
+fi
+
+jq -n '{"apiVersion": "piraeus.io/v1", "kind": "LinstorSatelliteConfiguration", "metadata": {"name": "host-networking"}, "spec": {"patches": []}}' > "$TEMPDIR/linstorsatelliteconfiguration/host-networking.yaml"
+jq '.resources += ["host-networking.yaml"]' "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml" > "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml.new"
+mv "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml.new" "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml"
+
+echo "For compatibility, applying host-networking to all satellites"
+jq -n '{}' \
+	| format_patch LinstorSatelliteConfiguration "host-networking" '[{"op": "add", "path": "/spec/podTemplate", "value": {"spec": {"hostNetwork": true}}}]' \
+	| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+	| diff_patch "$TEMPDIR/linstorsatelliteconfiguration"
+confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" y
+
+jq_item() {
+	jq ".items[$IDX]" "$TEMPDIR/linstorsatellitesets.json" | jq "$@"
+}
+
+for IDX in $(seq 0 "$(jq '.items | length - 1' "$TEMPDIR/linstorsatellitesets.json")"); do
+	NAME="$(jq_item -r '.metadata.name')"
+	jq -n --arg NAME "$NAME" '{"apiVersion": "piraeus.io/v1", "kind": "LinstorSatelliteConfiguration", "metadata": {"name": $NAME}, "spec": {"patches": [], "storagePools": []}}' > "$TEMPDIR/linstorsatelliteconfiguration/$NAME.yaml"
+	jq --arg CONFIG "$NAME.yaml" '.resources += [$CONFIG]' "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml" > "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml.new"
+	mv "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml.new" "$TEMPDIR/linstorsatelliteconfiguration/kustomization.yaml"
+
+	if [ "$(jq_item '.spec.affinity?.nodeAffinity?.requiredDuringSchedulingIgnoredDuringExecution | length')" -gt 0 ]; then
+		jq_item '.spec.affinity.nodeAffinity.requiredDuringSchedulingIgnoredDuringExecution' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/nodeAffinity", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration"
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" y
+	fi
+
+	if [ "$(jq_item -c '.spec.additionalEnv')" != '[{"name":"LB_SELINUX_AS","value":"modules_object_t"}]' ]; then
+		echo "Found additional environment variables passed to LINSTOR Satellite"
+		jq_item '.spec.additionalEnv' \
+			| format_patch DaemonSet linstor-satellite '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-satellite"}, "spec": {"template": {"spec": {"containers": [{"name": "linstor-satellite", "env": .}]}}}}' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration" pkg/resources/satellite/satellite
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" y
+	fi
+
+	if [ "$(jq_item '.spec.dnsPolicy | length')" -gt 0 ]; then
+		echo "Found custom DNS policy for LINSTOR Satellite Pod"
+		jq_item '.spec.dnsPolicy' \
+			| format_patch DaemonSet linstor-satellite '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-satellite"}, "spec": {"template": {"spec": {"dnsPolicy": .}}}}' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration" pkg/resources/satellite/satellite
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" n
+	fi
+
+	if [ "$(jq_item '.spec.extraVolumes | length')" -gt 0 ]; then
+		echo "Found additional volumes for LINSTOR Satellite Pod"
+		jq_item '.spec.extraVolumes' \
+			| format_patch DaemonSet linstor-satellite '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-satellite"}, "spec": {"template": {"spec": {"volumes": .}}}}' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration" pkg/resources/satellite/satellite
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" n
+	fi
+
+	if [ "$(jq_item '.spec.mountDrbdResourceDirectoriesFromHost')" == "true" ]; then
+		echo "Found DRBD config mount for LINSTOR Satellite Pod"
+		jq -n '{}' \
+			| format_patch DaemonSet linstor-satellite '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-satellite"}, "spec": {"template": {"spec": {"volumes": [{"name": "etc-drbd-conf", "hostPath": {"path": "/etc/drbd.conf", "type": "File"}}, {"name": "etc-drbd-d", "hostPath": {"path": "/etc/drbd.d", "type": "Directory"}}], "containers": [{"name": "linstor-satellite", "volumeMounts": [{"name": "etc-drbd-conf", "mountPath": "/etc/drbd.conf", "readOnly": true}, {"name": "etc-drbd-d", "mountPath": "/etc/drbd.d", "readOnly": true}]}]}}}}' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration" pkg/resources/satellite/satellite
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" n
+	fi
+
+	if [ "$(jq_item '.spec.sidecars | length')" -gt 0 ]; then
+		echo "Found additional containers for LINSTOR Satellite Pod"
+		jq_item '.spec.sidecars' \
+			| format_patch DaemonSet linstor-satellite '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-satellite"}, "spec": {"template": {"spec": {"containers": .}}}}' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration" pkg/resources/satellite/satellite
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" n
+	fi
+
+	if [ -n "$(jq_item -r '.spec.sslSecret // ""')" ]; then
+		echo "Found TLS secret for LINSTOR Satellite"
+		jq_item '.spec.sslSecret' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/internalTLS", "value": {"secretName": .}}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration"
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" y
+	fi
+
+	if [ "$(jq_item '.spec.tolerations | length')" -gt 0 ]; then
+		echo "Found custom tolerations for LINSTOR Satellite Pod"
+		jq_item '.spec.tolerations' \
+			| format_patch DaemonSet linstor-satellite '{"apiVersion": "apps/v1", "kind": "DaemonSet", "metadata": {"name": "linstor-satellite"}, "spec": {"template": {"spec": {"tolerations": .}}}}' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/patches/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration" pkg/resources/satellite/satellite
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" n
+	fi
+
+	if [ "$(jq_item '.spec.storagePools.lvmPools | length')" -gt 0 ]; then
+		echo "Found LVM storage pool"
+		jq_item '.spec.storagePools.lvmPools[]' \
+		  | jq '.devicePaths as $PATHS | .volumeGroup as $VG | {"name": .name, "lvmPool": {}} | if $VG != "" then .lvmPool.volumeGroup = $VG else . end | if $PATHS | length > 0 then .source = {"hostDevices": $PATHS} else . end' \
+		  | format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/storagePools/-", "value": .}]' \
+		  | append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+		  | diff_patch "$TEMPDIR/linstorsatelliteconfiguration"
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" y
+	fi
+
+	if [ "$(jq_item '.spec.storagePools.lvmThinPools | length')" -gt 0 ]; then
+		echo "Found LVM THIN storage pool"
+		jq_item '.spec.storagePools.lvmThinPools[]' \
+			| jq '.devicePaths as $PATHS | .volumeGroup as $VG | .thinVolume as $LV | {"name": .name, "lvmThinPool": {}} | if $VG != "" then .lvmThinPool.volumeGroup = $VG else . end | if $LV != "" then .lvmThinPool.thinPool = $LV else . end | if $PATHS | length > 0 then .source = {"hostDevices": $PATHS} else . end' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/storagePools/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration"
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" y
+	fi
+
+	if [ "$(jq_item '.spec.storagePools.zfsPools | length')" -gt 0 ]; then
+		echo "Found ZFS storage pool"
+		jq_item '.spec.storagePools.zfsPools[]' \
+			| jq '{"name": .name, "\(if .thin then "zfsThinPool" else "zfsPool" end)": {"zPool": .zPool}}' \
+			| format_patch LinstorSatelliteConfiguration "$NAME" '[{"op": "add", "path": "/spec/storagePools/-", "value": .}]' \
+			| append_patch "$TEMPDIR/linstorsatelliteconfiguration" \
+			| diff_patch "$TEMPDIR/linstorsatelliteconfiguration"
+		confirm_patch "$TEMPDIR/linstorsatelliteconfiguration" y
+	fi
+done
+
+print_row() {
+	printf "| %-19.19s | %-30.30s | %-51.51s | %-50.50s | \n" "$1" "$2" "$3" "$4"
+}
+
+echo
+echo "-------------------------------------------------------------------------------------------------------------------------------------------------------------------"
+echo "| The following non-default values have not been converted:                                                                                                       |"
+echo "|-----------------------------------------------------------------------------------------------------------------------------------------------------------------|"
+echo "| Resource            | Key                            | Recommended Action                                  | Value                                              |"
+echo "|---------------------|--------------------------------|-----------------------------------------------------|----------------------------------------------------|"
+
+[[ "$(jq -r '.items[0].spec.controllerImage' "$TEMPDIR/linstorcontrollers.json")" == quay.io/piraeusdatastore/piraeus-server:* ]] || print_row LinstorCluster .spec.controllerImage "Adjust image configuration" "$(jq -r '.items[0].spec.controllerImage' "$TEMPDIR/linstorcontrollers.json")"
+[ -z "$(jq -r '.items[0].spec.dbCertSecret // ""' "$TEMPDIR/linstorcontrollers.json")" ] || print_row LinstorController .spec.dbCertSecret "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.dbCertSecret' "$TEMPDIR/linstorcontrollers.json")"
+[ "$(jq -r '.items[0].spec.dbUseClientCert' "$TEMPDIR/linstorcontrollers.json")" == "false" ] || print_row LinstorController .spec.dbUseClientCert "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.dbUseClientCert' "$TEMPDIR/linstorcontrollers.json")"
+[ -z "$(jq -r '.items[0].spec.drbdRepoCred' "$TEMPDIR/linstorcontrollers.json")" ] || print_row LinstorController .spec.drbdRepoCred "Use pull secret to deploy the operator" "$(jq -r '.items[0].spec.drbdRepoCred' "$TEMPDIR/linstorcontrollers.json")"
+[ -z "$(jq -r '.items[0].spec.httpBindAddress // ""' "$TEMPDIR/linstorcontrollers.json")" ] || print_row LinstorController .spec.httpBindAddress "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.httpBindAddress' "$TEMPDIR/linstorcontrollers.json")"
+[ -z "$(jq -r '.items[0].spec.httpsBindAddress // ""' "$TEMPDIR/linstorcontrollers.json")" ] || print_row LinstorController .spec.httpsBindAddress "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.httpsBindAddress' "$TEMPDIR/linstorcontrollers.json")"
+[ "$(jq -r '.items[0].spec.imagePullPolicy' "$TEMPDIR/linstorcontrollers.json")" == "IfNotPresent" ] || print_row LinstorController .spec.imagePullPolicy "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.imagePullPolicy' "$TEMPDIR/linstorcontrollers.json")"
+[ "$(jq -r '.items[0].spec.logLevel // "info"' "$TEMPDIR/linstorcontrollers.json")" == "info" ] || print_row LinstorController .spec.logLevel "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.logLevel' "$TEMPDIR/linstorcontrollers.json")"
+[ -z "$(jq -r '.items[0].spec.priorityClassName' "$TEMPDIR/linstorcontrollers.json")" ] || print_row LinstorController .spec.priorityClassName "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.priorityClassName' "$TEMPDIR/linstorcontrollers.json")"
+[ "$(jq '.items[0].spec.replicas' "$TEMPDIR/linstorcontrollers.json")" -eq 1 ] || print_row LinstorController .spec.replicas "Keep at one" "$(jq '.items[0].spec.replicas' "$TEMPDIR/linstorcontrollers.json")"
+[ "$(jq '.items[0].spec.resources | length' "$TEMPDIR/linstorcontrollers.json")" -eq 0 ] || print_row LinstorController .spec.resources "Use LinstorCluster.spec.patches" "$(jq -c '.items[0].spec.resources' "$TEMPDIR/linstorcontrollers.json")"
+[ -z "$(jq -r '.items[0].spec.serviceAccountName // ""' "$TEMPDIR/linstorcontrollers.json")" ] || print_row LinstorController .spec.serviceAccountName "Let Operator manage RBAC" "$(jq -r '.items[0].spec.serviceAccountName' "$TEMPDIR/linstorcontrollers.json")"
+
+[ "$(jq -r '.items[0].spec.controllerEndpoint' "$TEMPDIR/linstorcsidrivers.json")" == "$EXPECTED_CONTROLLER_ENDPOINT" ] || print_row LinstorCSIDriver .spec.controllerEndpoint "Set LinstorCluster.spec.externalController" "$(jq -r '.items[0].spec.controllerEndpoint' "$TEMPDIR/linstorcsidrivers.json")"
+[[ "$(jq -r '.items[0].spec.csiAttacherImage' "$TEMPDIR/linstorcsidrivers.json")" == registry.k8s.io/sig-storage/csi-attacher:* ]] || print_row LinstorCSIDriver .spec.csiAttacherImage "Adjust image configuration" "$(jq -r '.items[0].spec.csiAttacherImage' "$TEMPDIR/linstorcsidrivers.json")"
+[[ "$(jq -r '.items[0].spec.csiLivenessProbeImage' "$TEMPDIR/linstorcsidrivers.json")" == registry.k8s.io/sig-storage/livenessprobe:* ]] || print_row LinstorCSIDriver .spec.csiLivenessProbeImage "Adjust image configuration" "$(jq -r '.items[0].spec.csiLivenessProbeImage' "$TEMPDIR/linstorcsidrivers.json")"
+[[ "$(jq -r '.items[0].spec.csiNodeDriverRegistrarImage' "$TEMPDIR/linstorcsidrivers.json")" == registry.k8s.io/sig-storage/csi-node-driver-registrar:* ]] || print_row LinstorCSIDriver .spec.csiNodeDriverRegistrarImage "Adjust image configuration" "$(jq -r '.items[0].spec.csiNodeDriverRegistrarImage' "$TEMPDIR/linstorcsidrivers.json")"
+[[ "$(jq -r '.items[0].spec.csiProvisionerImage' "$TEMPDIR/linstorcsidrivers.json")" == registry.k8s.io/sig-storage/csi-provisioner:* ]] || print_row LinstorCSIDriver .spec.csiProvisionerImage "Adjust image configuration" "$(jq -r '.items[0].spec.csiProvisionerImage' "$TEMPDIR/linstorcsidrivers.json")"
+[[ "$(jq -r '.items[0].spec.csiResizerImage' "$TEMPDIR/linstorcsidrivers.json")" == registry.k8s.io/sig-storage/csi-resizer:* ]] || print_row LinstorCSIDriver .spec.csiResizerImage "Adjust image configuration" "$(jq -r '.items[0].spec.csiResizerImage' "$TEMPDIR/linstorcsidrivers.json")"
+[[ "$(jq -r '.items[0].spec.csiSnapshotterImage' "$TEMPDIR/linstorcsidrivers.json")" == registry.k8s.io/sig-storage/csi-snapshotter:* ]] || print_row LinstorCSIDriver .spec.csiSnapshotterImage "Adjust image configuration" "$(jq -r '.items[0].spec.csiSnapshotterImage' "$TEMPDIR/linstorcsidrivers.json")"
+[[ "$(jq -r '.items[0].spec.linstorPluginImage' "$TEMPDIR/linstorcsidrivers.json")" == quay.io/piraeusdatastore/piraeus-csi:* ]] || print_row LinstorCSIDriver .spec.linstorPluginImage "Adjust image configuration" "$(jq -r '.items[0].spec.linstorPluginImage' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq '.items[0].spec.resources | length' "$TEMPDIR/linstorcsidrivers.json")" -eq 0 ] || print_row LinstorCSIDriver .spec.resources "Use LinstorCluster.spec.patches" "$(jq -c '.items[0].spec.resources' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq -r '.items[0].spec.csiControllerServiceAccountName' "$TEMPDIR/linstorcsidrivers.json")" == "csi-controller" ] || print_row LinstorCSIDriver .spec.csiControllerServiceAccountName "Let Operator manage RBAC" "$(jq -r '.items[0].spec.csiControllerServiceAccountName' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq -r '.items[0].spec.csiNodeServiceAccountName' "$TEMPDIR/linstorcsidrivers.json")" == "csi-node" ] || print_row LinstorCSIDriver .spec.csiNodeServiceAccountName "Let Operator manage RBAC" "$(jq -r '.items[0].spec.csiNodeServiceAccountName' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq '.items[0].spec.csiAttacherWorkerThreads // 10' "$TEMPDIR/linstorcsidrivers.json")" -eq 10 ] || print_row LinstorCSIDriver .spec.csiAttacherWorkerThreads "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.csiAttacherWorkerThreads' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq '.items[0].spec.csiProvisionerWorkerThreads // 10' "$TEMPDIR/linstorcsidrivers.json")" -eq 10 ] || print_row LinstorCSIDriver .spec.csiProvisionerWorkerThreads "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.csiProvisionerWorkerThreads' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq '.items[0].spec.csiResizerWorkerThreads // 10' "$TEMPDIR/linstorcsidrivers.json")" -eq 10 ] || print_row LinstorCSIDriver .spec.csiResizerWorkerThreads "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.csiResizerWorkerThreads' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq '.items[0].spec.csiSnapshotterWorkerThreads // 10' "$TEMPDIR/linstorcsidrivers.json")" -eq 10 ] || print_row LinstorCSIDriver .spec.csiSnapshotterWorkerThreads "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.csiSnapshotterWorkerThreads' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq '.items[0].spec.enableTopology' "$TEMPDIR/linstorcsidrivers.json")" == "true" ] || print_row LinstorCSIDriver .spec.enableTopology "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.enableTopology' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq -r '.items[0].spec.imagePullPolicy' "$TEMPDIR/linstorcsidrivers.json")" == "IfNotPresent" ] || print_row LinstorCSIDriver .spec.imagePullPolicy "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.imagePullPolicy' "$TEMPDIR/linstorcsidrivers.json")"
+[ -z "$(jq -r '.items[0].spec.imagePullSecret' "$TEMPDIR/linstorcsidrivers.json")" ] || print_row LinstorCSIDriver .spec.imagePullSecret "Use pull secret to deploy the operator" "$(jq -r '.items[0].spec.imagePullSecret' "$TEMPDIR/linstorcsidrivers.json")"
+[ "$(jq -r '.items[0].spec.logLevel // "info"' "$TEMPDIR/linstorcsidrivers.json")" == "info" ] || print_row LinstorCSIDriver .spec.logLevel "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.logLevel' "$TEMPDIR/linstorcsidrivers.json")"
+[ -z "$(jq -r '.items[0].spec.priorityClassName' "$TEMPDIR/linstorcsidrivers.json")" ] || print_row LinstorCSIDriver .spec.priorityClassName "Use LinstorCluster.spec.patches" "$(jq -r '.items[0].spec.priorityClassName' "$TEMPDIR/linstorcsidrivers.json")"
+
+for IDX in $(seq 0 "$(jq '.items | length - 1' "$TEMPDIR/linstorsatellitesets.json")"); do
+	[ "$(jq_item '.spec.affinity?.nodeAffinity?.preferredDuringSchedulingIgnoredDuringExecution | length')" -eq 0 ] || print_row LinstorSatelliteSet .spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution "Use LinstorSatelliteConfiguration.spec.nodeAffinity" "$(jq_item -c '.spec.affinity.nodeAffinity.preferredDuringSchedulingIgnoredDuringExecution')"
+	[ "$(jq_item '.spec.affinity?.podAffinity | length')" -eq 0 ] || print_row LinstorSatelliteSet .spec.affinity.podAffinity "Use LinstorSatelliteConfiguration.spec.nodeAffinity" "$(jq_item -c '.spec.affinity.podAffinity')"
+	[ "$(jq_item '.spec.affinity?.podAntiAffinity | length')" -eq 0 ] || print_row LinstorSatelliteSet .spec.affinity.podAntiAffinity "Use LinstorSatelliteConfiguration.spec.nodeAffinity" "$(jq_item -c '.spec.affinity.podAntiAffinity')"
+	[ "$(jq_item -r '.spec.automaticStorageType')" == "None" ] || print_row LinstorSatelliteSet .spec.automaticStorageType "Use LinstorSatelliteConfiguration.spec.storagePools" "$(jq_item -r '.spec.automaticStorageType')"
+	[ "$(jq_item -r '.spec.controllerEndpoint')" == "$EXPECTED_CONTROLLER_ENDPOINT" ] || print_row LinstorSatelliteSet .spec.controllerEndpoint "Set LinstorCluster.spec.externalController" "$(jq_item -r '.spec.controllerEndpoint')"
+	[ -z "$(jq_item -r '.spec.drbdRepoCred')" ] || print_row LinstorSatelliteSet .spec.drbdRepoCred "Use pull secret to deploy the operator" "$(jq_item -r '.spec.drbdRepoCred')"
+	[ "$(jq_item -r '.spec.imagePullPolicy')" == "IfNotPresent" ] || print_row LinstorSatelliteSet .spec.imagePullPolicy "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -r '.spec.imagePullPolicy')"
+	[ -z "$(jq_item -r '.spec.kernelModuleInjectionAdditionalSourceDirectory // ""')" ] || print_row LinstorSatelliteSet .spec.kernelModuleInjectionAdditionalSourceDirectory "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -r '.spec.kernelModuleInjectionAdditionalSourceDirectory')"
+	[ "$(jq_item -r '.spec.kernelModuleInjectionExtraVolumeMounts | length')" -eq 0 ] || print_row LinstorSatelliteSet .spec.kernelModuleInjectionExtraVolumeMounts "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -c '.spec.kernelModuleInjectionExtraVolumeMounts')"
+	[[ "$(jq_item -r '.spec.kernelModuleInjectionImage')" == quay.io/piraeusdatastore/drbd9-* ]] || print_row LinstorSatelliteSet .spec.kernelModuleInjectionImage "Adjust image configuration" "$(jq_item -r '.spec.kernelModuleInjectionImage')"
+	[ "$(jq_item -r '.spec.kernelModuleInjectionMode')" == "Compile" ] || print_row LinstorSatelliteSet .spec.kernelModuleInjectionMode "Adjust image configuration" "$(jq_item -r '.spec.kernelModuleInjectionMode')"
+	[ "$(jq_item -r '.spec.kernelModuleInjectionResources | length')" -eq 0 ] || print_row LinstorSatelliteSet .spec.kernelModuleInjectionResources "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -c '.spec.kernelModuleInjectionResources')"
+	[ "$(jq_item -r '.spec.logLevel // "info"')" == "info" ] || print_row LinstorSatelliteSet .spec.logLevel "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -r '.spec.logLevel')"
+	[ -z "$(jq_item -r '.spec.monitoringBindAddress // ""')" ] || print_row LinstorSatelliteSet .spec.monitoringBindAddress "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -r '.spec.monitoringBindAddress')"
+	[[ "$(jq_item -r '.spec.monitoringImage')" == quay.io/piraeusdatastore/drbd-reactor:* ]] || print_row LinstorSatelliteSet .spec.monitoringImage "Adjust image configuration" "$(jq_item -r '.spec.monitoringImage')"
+	[ -z "$(jq_item -r '.spec.priorityClassName')" ] || print_row LinstorSatelliteSet .spec.priorityClassName "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -r '.spec.priorityClassName')"
+	[[ "$(jq_item -r '.spec.satelliteImage')" == quay.io/piraeusdatastore/piraeus-server:* ]] || print_row LinstorSatelliteSet .spec.satelliteImage "Adjust image configuration" "$(jq_item -r '.spec.satelliteImage')"
+	[ "$(jq_item -r '.spec.resources | length')" -eq 0 ] || print_row LinstorSatelliteSet .spec.resources "Use LinstorSatelliteConfiguration.spec.patches" "$(jq_item -c '.spec.resources')"
+	[ -z "$(jq_item -r '.spec.serviceAccountName // ""')" ] || print_row LinstorSatelliteSet .spec.serviceAccountName "Let Operator manage RBAC" "$(jq_item -c '.spec.serviceAccountName')"
+done
+
+echo "-------------------------------------------------------------------------------------------------------------------------------------------------------------------"
+
+echo
+echo "---------------------------------------------------------------------------------------------"
+echo "| After upgrading, apply the following resources. They have been saved to v2-resources.yaml |"
+echo "---------------------------------------------------------------------------------------------"
+echo "---"
+kubectl kustomize "$TEMPDIR" | tee v2-resources.yaml
diff --git a/v2.7.1/how-to/upgrade/index.html b/v2.7.1/upgrade/migration/index.html
similarity index 92%
rename from v2.7.1/how-to/upgrade/index.html
rename to v2.7.1/upgrade/migration/index.html
index 0e5643e..30f623e 100644
--- a/v2.7.1/how-to/upgrade/index.html
+++ b/v2.7.1/upgrade/migration/index.html
@@ -6,19 +6,19 @@
       <meta charset="utf-8">
       <meta name="viewport" content="width=device-width,initial-scale=1">
       
-        <meta name="description" content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere.">
+        <meta name="description" content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere.">
       
       
         <meta name="author" content="The Piraeus Maintainers">
       
       
-        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/how-to/upgrade/">
+        <link rel="canonical" href="https://piraeus.io/docs/v2.7.1/upgrade/migration/">
       
       
-        <link rel="prev" href="../restore-linstor-db/">
+        <link rel="prev" href="../">
       
       
-        <link rel="next" href="UPGRADE/">
+        <link rel="next" href="1-migrate-database/">
       
       
       <link rel="icon" href="../../assets/favicon.png">
@@ -26,7 +26,7 @@
     
     
       
-        <title>Upgrades - Piraeus Datastore</title>
+        <title>Upgrading from v1 to v2 - Piraeus Datastore</title>
       
     
     
@@ -61,11 +61,11 @@
       
         <meta  property="og:type"  content="website" >
       
-        <meta  property="og:title"  content="Upgrades - Piraeus Datastore" >
+        <meta  property="og:title"  content="Upgrading from v1 to v2 - Piraeus Datastore" >
       
-        <meta  property="og:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  property="og:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/index.png" >
+        <meta  property="og:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/README.png" >
       
         <meta  property="og:image:type"  content="image/png" >
       
@@ -73,15 +73,15 @@
       
         <meta  property="og:image:height"  content="630" >
       
-        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/how-to/upgrade/" >
+        <meta  property="og:url"  content="https://piraeus.io/docs/v2.7.1/upgrade/migration/" >
       
         <meta  name="twitter:card"  content="summary_large_image" >
       
-        <meta  name="twitter:title"  content="Upgrades - Piraeus Datastore" >
+        <meta  name="twitter:title"  content="Upgrading from v1 to v2 - Piraeus Datastore" >
       
-        <meta  name="twitter:description"  content="An easy-using cloud native datastore for Kubernetes. 100% open source, run anywhere." >
+        <meta  name="twitter:description"  content="An easy-to-use cloud native datastore for Kubernetes. 100% open source, run anywhere." >
       
-        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/how-to/upgrade/index.png" >
+        <meta  name="twitter:image"  content="https://piraeus.io/docs/v2.7.1/assets/images/social/upgrade/migration/README.png" >
       
     
     
@@ -142,7 +142,7 @@
         <div class="md-header__topic" data-md-component="header-topic">
           <span class="md-ellipsis">
             
-              Upgrades
+              Upgrading from v1 to v2
             
           </span>
         </div>
@@ -305,7 +305,7 @@
     
     
       <li class="md-tabs__item">
-        <a href="../" class="md-tabs__link">
+        <a href="../../how-to/" class="md-tabs__link">
           
   
     
@@ -327,7 +327,7 @@
     
     
       <li class="md-tabs__item md-tabs__item--active">
-        <a href="./" class="md-tabs__link">
+        <a href="../" class="md-tabs__link">
           
   
     
@@ -634,7 +634,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="../" class="md-nav__link ">
+            <a href="../../how-to/" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -715,7 +715,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../external-controller/" class="md-nav__link">
+      <a href="../../how-to/external-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -736,7 +736,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../drbd-loader/" class="md-nav__link">
+      <a href="../../how-to/drbd-loader/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -757,7 +757,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../install-kernel-headers/" class="md-nav__link">
+      <a href="../../how-to/install-kernel-headers/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -836,7 +836,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../internal-tls/" class="md-nav__link">
+      <a href="../../how-to/internal-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -857,7 +857,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../api-tls/" class="md-nav__link">
+      <a href="../../how-to/api-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -878,7 +878,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../drbd-tls/" class="md-nav__link">
+      <a href="../../how-to/drbd-tls/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -899,7 +899,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../secure-boot/" class="md-nav__link">
+      <a href="../../how-to/secure-boot/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -980,7 +980,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../openshift/" class="md-nav__link">
+      <a href="../../how-to/openshift/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1001,7 +1001,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../talos/" class="md-nav__link">
+      <a href="../../how-to/talos/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1022,7 +1022,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../flatcar/" class="md-nav__link">
+      <a href="../../how-to/flatcar/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1043,7 +1043,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../microk8s/" class="md-nav__link">
+      <a href="../../how-to/microk8s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1064,7 +1064,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../k0s/" class="md-nav__link">
+      <a href="../../how-to/k0s/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1141,7 +1141,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../http-proxy/" class="md-nav__link">
+      <a href="../../how-to/http-proxy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1162,7 +1162,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../network-policy/" class="md-nav__link">
+      <a href="../../how-to/network-policy/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1183,7 +1183,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../drbd-host-networking/" class="md-nav__link">
+      <a href="../../how-to/drbd-host-networking/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1260,7 +1260,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../monitoring/" class="md-nav__link">
+      <a href="../../how-to/monitoring/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1281,7 +1281,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../linstor-affinity-controller/" class="md-nav__link">
+      <a href="../../how-to/linstor-affinity-controller/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1302,7 +1302,7 @@
   
   
     <li class="md-nav__item">
-      <a href="../restore-linstor-db/" class="md-nav__link">
+      <a href="../../how-to/restore-linstor-db/" class="md-nav__link">
         
   
   <span class="md-ellipsis">
@@ -1346,8 +1346,6 @@
           
         
       
-        
-      
         
       
     
@@ -1370,7 +1368,7 @@
           
           
           <div class="md-nav__link md-nav__container">
-            <a href="./" class="md-nav__link md-nav__link--active">
+            <a href="../" class="md-nav__link ">
               
   
   <span class="md-ellipsis">
@@ -1381,7 +1379,7 @@
             </a>
             
               
-              <label class="md-nav__link md-nav__link--active" for="__nav_4" id="__nav_4_label" tabindex="">
+              <label class="md-nav__link " for="__nav_4" id="__nav_4_label" tabindex="">
                 <span class="md-nav__icon md-icon"></span>
               </label>
             
@@ -1400,26 +1398,7 @@
                 
   
   
-  
-  
-    <li class="md-nav__item">
-      <a href="UPGRADE/" class="md-nav__link">
-        
-  
-  <span class="md-ellipsis">
-    Upgrading from v2 to v2
-  </span>
-  
-
-      </a>
-    </li>
-  
-
-              
-            
-              
-                
-  
+    
   
   
   
@@ -1427,6 +1406,10 @@
     
       
         
+          
+        
+      
+        
       
         
       
@@ -1445,32 +1428,42 @@
       
     
     
-    <li class="md-nav__item md-nav__item--section md-nav__item--nested">
+    <li class="md-nav__item md-nav__item--active md-nav__item--section md-nav__item--nested">
       
         
         
-        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_3" >
+        <input class="md-nav__toggle md-toggle " type="checkbox" id="__nav_4_2" checked>
         
           
-          <label class="md-nav__link" for="__nav_4_3" id="__nav_4_3_label" tabindex="">
-            
+          
+          <div class="md-nav__link md-nav__container">
+            <a href="./" class="md-nav__link md-nav__link--active">
+              
   
   <span class="md-ellipsis">
     Upgrading from v1 to v2
   </span>
   
 
-            <span class="md-nav__icon md-icon"></span>
-          </label>
+            </a>
+            
+              
+              <label class="md-nav__link md-nav__link--active" for="__nav_4_2" id="__nav_4_2_label" tabindex="">
+                <span class="md-nav__icon md-icon"></span>
+              </label>
+            
+          </div>
         
-        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_3_label" aria-expanded="false">
-          <label class="md-nav__title" for="__nav_4_3">
+        <nav class="md-nav" data-md-level="2" aria-labelledby="__nav_4_2_label" aria-expanded="true">
+          <label class="md-nav__title" for="__nav_4_2">
             <span class="md-nav__icon md-icon"></span>
             Upgrading from v1 to v2
           </label>
           <ul class="md-nav__list" data-md-scrollfix>
             
               
+            
+              
                 
   
   
@@ -1916,7 +1909,7 @@
   
 
 
-<h1 id="upgrading-piraeus-operator-from-version-1-to-version-2">Upgrading Piraeus Operator from Version 1 to Version 2</h1>
+<h1 id="upgrading-piraeus-operator-from-version-1-to-version-2">Upgrading Piraeus Operator from Version 1 to Version 2<a class="headerlink" href="#upgrading-piraeus-operator-from-version-1-to-version-2" title="Permanent link">&para;</a></h1>
 <p>The following document guides you through the upgrade process for Piraeus Operator from version 1 ("v1")
 to version 2 ("v2").</p>
 <p>Piraeus Operator v2 offers improved convenience and customization. This however made it necessary to make significant
@@ -1929,7 +1922,7 @@ <h1 id="upgrading-piraeus-operator-from-version-1-to-version-2">Upgrading Piraeu
 <li><a href="3-remove-operator-v1/">Step 3</a>: Remove the Piraeus Operator v1 deployment, keeping existing volumes untouched.</li>
 <li><a href="4-install-operator-v2/">Step 4</a>: Deploy Piraeus Operator v2 using the information gathered in step 2.</li>
 </ul>
-<h2 id="prerequisites">Prerequisites</h2>
+<h2 id="prerequisites">Prerequisites<a class="headerlink" href="#prerequisites" title="Permanent link">&para;</a></h2>
 <p>This guide assumes:</p>
 <ul>
 <li>You used Helm to create the original deployment and are familiar with upgrading Helm deployments.</li>
@@ -1940,16 +1933,16 @@ <h2 id="prerequisites">Prerequisites</h2>
 <li><a href="https://jqlang.github.io/jq/download/"><code>jq</code></a></li>
 <li>You are familiar with the <code>linstor</code> command line utility, specifically to verify the cluster state.</li>
 </ul>
-<h2 id="key-changes-between-operator-v1-and-v2">Key Changes Between Operator V1 and V2</h2>
-<h3 id="administrative-changes">Administrative Changes</h3>
+<h2 id="key-changes-between-operator-v1-and-v2">Key Changes Between Operator V1 and V2<a class="headerlink" href="#key-changes-between-operator-v1-and-v2" title="Permanent link">&para;</a></h2>
+<h3 id="administrative-changes">Administrative Changes<a class="headerlink" href="#administrative-changes" title="Permanent link">&para;</a></h3>
 <ul>
 <li>The resources <code>LinstorController</code>, <code>LinstorSatelliteSet</code> and <code>LinstorCSIDriver</code> have been replaced by
   <a href="../../reference/linstorcluster/"><code>LinstorCluster</code></a> and
   <a href="../../reference/linstorsatelliteconfiguration/"><code>LinstorSatelliteConfgiuration</code></a>.</li>
-<li>The default deployment runs the LINSTOR Satellite in the <a href="../drbd-host-networking/">container network</a>.
+<li>The default deployment runs the LINSTOR Satellite in the <a href="../../how-to/drbd-host-networking/">container network</a>.
   The migration script will propose changing to the host network.</li>
 </ul>
-<h3 id="operational-changes">Operational Changes</h3>
+<h3 id="operational-changes">Operational Changes<a class="headerlink" href="#operational-changes" title="Permanent link">&para;</a></h3>
 <ul>
 <li>In Operator v1, all labels on the Kubernetes node resource were replicated on the satellite, making them usable in the
   <code>replicasOnSame</code> and <code>replicasOnDifferent</code> parameters on the storage class. In Operator v2, only the following
@@ -2005,7 +1998,7 @@ <h3 id="operational-changes">Operational Changes</h3>
       <nav class="md-footer__inner md-grid" aria-label="Footer" >
         
           
-          <a href="../restore-linstor-db/" class="md-footer__link md-footer__link--prev" aria-label="Previous: Restore a LINSTOR Database Backup">
+          <a href="../" class="md-footer__link md-footer__link--prev" aria-label="Previous: Upgrades">
             <div class="md-footer__button md-icon">
               
               <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 24 24"><path d="M20 11v2H8l5.5 5.5-1.42 1.42L4.16 12l7.92-7.92L13.5 5.5 8 11z"/></svg>
@@ -2015,20 +2008,20 @@ <h3 id="operational-changes">Operational Changes</h3>
                 Previous
               </span>
               <div class="md-ellipsis">
-                Restore a LINSTOR Database Backup
+                Upgrades
               </div>
             </div>
           </a>
         
         
           
-          <a href="UPGRADE/" class="md-footer__link md-footer__link--next" aria-label="Next: Upgrading from v2 to v2">
+          <a href="1-migrate-database/" class="md-footer__link md-footer__link--next" aria-label="Next: Migrating the LINSTOR Database">
             <div class="md-footer__title">
               <span class="md-footer__direction">
                 Next
               </span>
               <div class="md-ellipsis">
-                Upgrading from v2 to v2
+                Migrating the LINSTOR Database
               </div>
             </div>
             <div class="md-footer__button md-icon">