Postsubmit site update from 7e2ffc8

Signed-off-by: kubevirt-bot <[email protected]>

compute/node_assignment/index.html

@@ -1867,6 +1867,15 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#live-update" class="md-nav__link">
+    <span class="md-ellipsis">
+      Live update
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -2714,6 +2723,15 @@
     </span>
   </a>
 
+</li>
+
+        <li class="md-nav__item">
+  <a href="#live-update" class="md-nav__link">
+    <span class="md-ellipsis">
+      Live update
+    </span>
+  </a>
+
 </li>
 
     </ul>
@@ -2890,6 +2908,13 @@ <h2 id="node-balancing-with-descheduler">Node balancing with Descheduler<a class
 <p>This annotation will cause, that the descheduler will be able to evict the VM's pod which can then be
 scheduled by scheduler on different nodes. A VirtualMachine will never restart or re-create a
 VirtualMachineInstance until the current instance of the VirtualMachineInstance is deleted from the cluster.</p>
+<h2 id="live-update">Live update<a class="headerlink" href="#live-update" title="Permanent link">&para;</a></h2>
+<p>When the <a href="../../user_workloads/vm_rollout_strategies/">VM rollout strategy</a> is set to <code>LiveUpdate</code>, changes to a VM's
+node selector or affinities will dynamically propagate to the VMI (unless the <code>RestartRequired</code> condition is set).
+Changes to tolerations will not dynamically propagate, and will trigger a <code>RestartRequired</code> condition if changed on a
+running VM.</p>
+<p>Modifications of the node selector / affinities will only take effect on next <a href="../live_migration/">migration</a>, the change
+alone will not trigger one.</p>