Postsubmit site update from 719ad53

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

2018/CDI-DataVolumes.html

@@ -356,7 +356,7 @@ <h2 id="creating-a-virtualmachine-embedding-a-datavolume">Creating a VirtualMach
         <span class="na">source</span><span class="pi">:</span>
           <span class="na">http</span><span class="pi">:</span>
             <span class="na">url</span><span class="pi">:</span> <span class="s2">"</span><span class="s">https://cloud.centos.org/centos/7/images/CentOS-7-x86_64-GenericCloud.qcow2"</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2018/Deploying-VMs-on-Kubernetes-GlusterFS-KubeVirt.html

@@ -627,7 +627,7 @@ <h2 id="deploying-virtual-machines">Deploying Virtual Machines</h2>
     <span class="na">kubevirt.io/ovm</span><span class="pi">:</span> <span class="s">cirros</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">cirros</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">false</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Halted</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">creationTimestamp</span><span class="pi">:</span> <span class="no">null</span>

2018/KubeVirt-objects.html

@@ -633,19 +633,19 @@ <h2 id="offlinevirtualmachine">OfflineVirtualMachine</h2>
 
 <h3 id="what-is-running-in-offlinevirtualmachine">What is Running in OfflineVirtualMachine?</h3>
 
-<p><a href="https://kubevirt.io/api-reference/master/definitions.html#_v1_offlinevirtualmachinespec">.spec.running</a> controls whether the associated VirtualMachine object is created. In other words this changes the <a href="https://kubevirt.io/user-guide/virtual_machines/lifecycle/#stopping-a-virtual-machine">power status</a> of the virtual machine.</p>
+<p><a href="https://kubevirt.io/api-reference/master/definitions.html">.spec.runStrategy</a> controls whether and when the associated VirtualMachineInstance object is created. In other words this controls the <a href="https://kubevirt.io/user-guide/virtual_machines/lifecycle/#stopping-a-virtual-machine">power status</a> of the virtual machine.</p>
 
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>  running: true
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>  runStrategy: Always
 </code></pre></div></div>
 
-<p>This will create a <code class="language-plaintext highlighter-rouge">VirtualMachine</code> object which will instantiate and power on a virtual machine.</p>
+<p>This will create a <code class="language-plaintext highlighter-rouge">VirtualMachineInstance</code> object which will instantiate and power on a virtual machine.</p>
 
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>kubectl patch offlinevirtualmachine mongodb --type merge -p '{"spec":{"running":true }}' -n nodejs-ex
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>kubectl patch offlinevirtualmachine mongodb --type merge -p '{"spec":{"runStrategy": "Always"}}' -n nodejs-ex
 </code></pre></div></div>
 
-<p>This will delete the <code class="language-plaintext highlighter-rouge">VirtualMachine</code> object which will power off the virtual machine.</p>
+<p>This will delete the <code class="language-plaintext highlighter-rouge">VirtualMachineInstance</code> object which will power off the virtual machine.</p>
 
-<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>kubectl patch offlinevirtualmachine mongodb --type merge -p '{"spec":{"running":false }}' -n nodejs-ex
+<div class="language-plaintext highlighter-rouge"><div class="highlight"><pre class="highlight"><code>kubectl patch offlinevirtualmachine mongodb --type merge -p '{"spec":{"runStrategy": "Halted"}}' -n nodejs-ex
 </code></pre></div></div>
 
 <p>And if you would rather not have to remember the <code class="language-plaintext highlighter-rouge">kubectl patch</code> command above

2018/ignition-support.html

@@ -312,7 +312,7 @@ <h3 id="step-1">Step 1</h3>
 <span class="na">metadata</span><span class="pi">:</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">myvm1</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2019/How-To-Import-VM-into-Kubevirt.html

@@ -445,7 +445,7 @@ <h4 id="datavolume-vm-behavior">DataVolume VM Behavior</h4>
     <span class="na">kubevirt.io/vm</span><span class="pi">:</span> <span class="s">vm-alpine-datavolume</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">vm-alpine-datavolume</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">false</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Halted</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2019/More-about-Kubevirt-metrics.html

@@ -303,7 +303,7 @@ <h2 id="new-metrics">New metrics</h2>
     <span class="na">kubevirt.io/vm</span><span class="pi">:</span> <span class="s">vm-test-01</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">vm-test-01</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">false</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Halted</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">creationTimestamp</span><span class="pi">:</span> <span class="no">null</span>

2020/Common_templates.html

@@ -310,7 +310,7 @@ <h5 id="to-start-vm-from-created-object">To start VM from created object</h5>
 
 <p>An alternative way to start the VM is with the oc patch command. Example:</p>
 
-<p><code class="language-plaintext highlighter-rouge">$ oc patch virtualmachine rheltinyvm --type merge -p '{"spec":{"running":true}}'</code></p>
+<p><code class="language-plaintext highlighter-rouge">$ oc patch virtualmachine rheltinyvm --type merge -p '{"spec":{"runStrategy":"Always"}}'</code></p>
 
 <p>As soon as VM starts, openshift creates a new type of object - <code class="language-plaintext highlighter-rouge">VirtualMachineInstance</code>. It has a similar name to VirtualMachine.</p>
 

2020/KubeVirt-Architecture-Fundamentals.html

@@ -307,7 +307,7 @@ <h2 id="the-declarative-kubevirt-virtualization-api">The Declarative KubeVirt Vi
 
 <p>The Kubernetes core apis have this concept of layering objects on top of one another through the use of <strong>workload controllers</strong>. For example, the Kubernetes ReplicaSet is a workload controller layered on top of pods. The ReplicaSet controller manages ensuring that there are always ‘x’ number of pod replicas running within the cluster. If a ReplicaSet object declares that 5 pod replicas should be running, but a node dies bringing that total to 4, then the ReplicaSet workload controller manages spinning up a 5th pod in order to meet the declared replica count. The workload controller is always reconciling on the ReplicaSet objects desired state.</p>
 
-<p>Using this established Kubernetes pattern of layering objects on top of one another, we came up with our own virtualization specific API and corresponding workload controller called a <strong>“VirtualMachine”</strong> (big surprise there on the name, right?). Users declare a VirtualMachine object just like they would a pod by posting the VirtualMachine object’s manifest to the cluster. The big difference here that deviates from how pods are managed is that we allow VirtualMachine objects to be declared to exist in different states. For example, you can declare you want to “start” a virtual machine by setting “running: true” on the VirtualMachine object’s spec. Likewise you can declare you want to “stop” a virtual machine by setting “running: false” on the VirtualMachine object’s spec. Behind the scenes, setting the “running” field to true or false results in the workload controller creating or deleting a pod for the virtual machine to live in.</p>
+<p>Using this established Kubernetes pattern of layering objects on top of one another, we came up with our own virtualization specific API and corresponding workload controller called a <strong>“VirtualMachine”</strong> (big surprise there on the name, right?). Users declare a VirtualMachine object just like they would a pod by posting the VirtualMachine object’s manifest to the cluster. The big difference here that deviates from how pods are managed is that we allow VirtualMachine objects to be declared to exist in different states. For example, you can declare you want to “start” a virtual machine by setting “runStrategy: Always” on the VirtualMachine object’s spec. Likewise you can declare you want to “stop” a virtual machine by setting “runStrategy: Halted” on the VirtualMachine object’s spec. Behind the scenes, setting the “runStrategy” field results in the workload controller creating or deleting a pod for the virtual machine to live in.</p>
 
 <p>In the end, we essentially created the concept of an <strong>immortal VirtualMachine</strong> by laying our own custom API on top of mortal pods. Our API and controller knows how to resurrect a “stopped” VirtualMachine by constructing a pod with all the right network, storage volumes, cpu, and memory attached to in order to accurately bring the VirtualMachine back to life with the exact same state it stopped with.</p>
 

2020/KubeVirt-VM-Image-Usage-Patterns.html

@@ -620,7 +620,7 @@ <h2 id="example-launching-a-single-pet-vm-from-custom-image">Example: Launching
     <span class="na">kubevirt.io/vm</span><span class="pi">:</span> <span class="s">nginx</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">nginx</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2020/KubeVirt-installing_Microsoft_Windows_from_an_iso.html

@@ -298,7 +298,7 @@ <h2 id="preparation">Preparation</h2>
 <span class="na">metadata</span><span class="pi">:</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">win2k12-iso</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">false</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Halted</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>
@@ -427,7 +427,7 @@ <h2 id="preparation">Preparation</h2>
 <span class="na">metadata</span><span class="pi">:</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">win2k12-iso</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">false</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Halted</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2020/Monitoring-KubeVirt-VMs-from-the-inside.html

@@ -385,7 +385,7 @@ <h2 id="deploying-a-virtualmachine-with-persistent-storage">Deploying a VirtualM
 <span class="na">metadata</span><span class="pi">:</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">monitorable-vm</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">name</span><span class="pi">:</span> <span class="s">monitorable-vm</span>

2020/Multiple-Network-Attachments-with-bridge-CNI.html

@@ -765,7 +765,7 @@ <h3 id="start-a-pair-of-vms-on-different-nodes-using-the-multus-configuration-to
 <span class="na">metadata</span><span class="pi">:</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">vma</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">spec</span><span class="pi">:</span>
       <span class="na">nodeSelector</span><span class="pi">:</span>
@@ -819,7 +819,7 @@ <h3 id="start-a-pair-of-vms-on-different-nodes-using-the-multus-configuration-to
 <span class="na">metadata</span><span class="pi">:</span>
   <span class="na">name</span><span class="pi">:</span> <span class="s">vmb</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">spec</span><span class="pi">:</span>
       <span class="na">nodeSelector</span><span class="pi">:</span>

2020/run_strategies.html

@@ -284,6 +284,7 @@ <h3 id="four-runstrategies-currently-exist">Four RunStrategies currently exist</
 <ul>
   <li>Always: If a VM is stopped for any reason, a new instance will be spawned.</li>
   <li>RerunOnFailure: If a VM ends execution in an error state, a new instance will be spawned. This addressed the second concern listed above. If a user halts a VM manually a new instance will not be spawned.</li>
+  <li>Once: The VM will run once and not be restarted upon completion regardless if the completion is of phase Failure or Success.</li>
   <li>Manual: This is exactly what it means. KubeVirt will neither attempt to start or stop a VM. In order to change state, the user must invoke start/stop/restart from the API. There exist convenience functions in the virtctl command line client as well.</li>
   <li>Halted: The VM will be stopped if it’s running, and will remain off.</li>
 </ul>

2021/Automated-Windows-Installation-With-Tekton-Pipelines.html

@@ -766,7 +766,7 @@ <h2 id="inspecting-the-output">Inspecting the output</h2>
           <span class="na">pvc</span><span class="pi">:</span>
             <span class="na">name</span><span class="pi">:</span> <span class="s">PVC_NAME</span>
             <span class="na">namespace</span><span class="pi">:</span> <span class="s">PVC_NAMESPACE</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">false</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Halted</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2021/Running-Realtime-Workloads.html

@@ -340,7 +340,7 @@ <h2 id="the-manifest">The Manifest</h2>
   <span class="na">name</span><span class="pi">:</span> <span class="s">fedora-realtime</span>
   <span class="na">namespace</span><span class="pi">:</span> <span class="s">poc</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2021/intel-vgpu-kubevirt.html

@@ -634,7 +634,7 @@ <h2 id="install-windows">Install Windows</h2>
 metadata:
   name: win10vm1
 spec:
-  running: false
+  runStrategy: Halted
   template:
     metadata:
       creationTimestamp: null

2022/Virtual-Machines-with-MetalLB.html

@@ -382,7 +382,7 @@ <h4 id="spin-up-a-virtual-machine-running-nginx">Spin up a Virtual Machine runni
   <span class="na">labels</span><span class="pi">:</span>
     <span class="na">metallb-service</span><span class="pi">:</span> <span class="s">nginx</span>
 <span class="na">spec</span><span class="pi">:</span>
-  <span class="na">running</span><span class="pi">:</span> <span class="no">true</span>
+  <span class="na">runStrategy</span><span class="pi">:</span> <span class="s">Always</span>
   <span class="na">template</span><span class="pi">:</span>
     <span class="na">metadata</span><span class="pi">:</span>
       <span class="na">labels</span><span class="pi">:</span>

2023/KubeVirt-on-autoscaling-nodes.html

@@ -588,7 +588,7 @@ <h2 id="deploy-a-vm-to-test">Deploy a VM to test</h2>
 metadata:
   name: testvm
 spec:
-  running: true
+  runStrategy: Always
   template:
     spec:
       domain: