replace kubevirt version

Author: lmandavi

modules/virt-about-runstrategies-vms.adoc

@@ -54,7 +54,7 @@ In {VirtProductName} clusters installed using installer-provisioned infrastructu
 
 [source,yaml]
 ----
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 spec:
   RunStrategy: Always <1>

modules/virt-configuring-masquerade-mode-dual-stack.adoc

@@ -21,7 +21,7 @@ When the virtual machine is running, incoming and outgoing traffic for the virtu
 +
 [source,yaml]
 ----
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 metadata:
   name: example-vm-ipv6

modules/virt-configuring-vm-live-migration-cli.adoc

@@ -24,7 +24,7 @@ $ oc edit vm <custom-vm> -n <my-namespace>
 
 [source,yaml]
 ----
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 metadata:
   name: custom-vm

modules/virt-creating-a-service-from-a-virtual-machine.adoc

@@ -44,7 +44,7 @@ This procedure presents an example of how to create, connect to, and expose a `S
 
 [source,yaml]
 ----
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 metadata:
   name: vm-ephemeral
@@ -171,7 +171,7 @@ vmservice   ClusterIP   172.30.3.149   <none>        27017/TCP   2m
 
 [source,yaml]
 ----
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 metadata:
   name: vm-connect

modules/virt-creating-new-vm-from-cloned-pvc-using-datavolumetemplate.adoc

@@ -39,7 +39,7 @@ For example:
 +
 [source,yaml]
 ----
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 metadata:
   labels:

modules/virt-example-vm-node-placement-node-affinity.adoc

@@ -14,7 +14,7 @@ If possible, the scheduler avoids nodes that have the label `example-node-label-
 ----
 metadata:
   name: example-vm-node-affinity
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 spec:
   affinity:
@@ -38,4 +38,4 @@ spec:
 ...
 ----
 <1> If you use the `requiredDuringSchedulingIgnoredDuringExecution` rule type, the VM is not scheduled if the constraint is not met.
-<2> If you use the `preferredDuringSchedulingIgnoredDuringExecution` rule type, the VM is still scheduled if the constraint is not met, as long as all required constraints are met.
+<2> If you use the `preferredDuringSchedulingIgnoredDuringExecution` rule type, the VM is still scheduled if the constraint is not met, as long as all required constraints are met.

modules/virt-example-vm-node-placement-node-selector.adoc

@@ -17,11 +17,11 @@ If there are no nodes that fit this description, the virtual machine is not sche
 ----
 metadata:
   name: example-vm-node-selector
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 spec:
   nodeSelector:
     example-key-1: example-value-1
     example-key-2: example-value-2
 ...
-----
+----

modules/virt-example-vm-node-placement-pod-affinity.adoc

@@ -14,7 +14,7 @@ If possible, the VM is not scheduled on a node that has any pod with the label `
 ----
 metadata:
   name: example-vm-pod-affinity
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 spec:
   affinity:
@@ -41,4 +41,4 @@ spec:
 ...
 ----
 <1> If you use the `requiredDuringSchedulingIgnoredDuringExecution` rule type, the VM is not scheduled if the constraint is not met.
-<2> If you use the `preferredDuringSchedulingIgnoredDuringExecution` rule type, the VM is still scheduled if the constraint is not met, as long as all required constraints are met.
+<2> If you use the `preferredDuringSchedulingIgnoredDuringExecution` rule type, the VM is still scheduled if the constraint is not met, as long as all required constraints are met.

modules/virt-example-vm-node-placement-tolerations.adoc

@@ -17,7 +17,7 @@ A virtual machine that tolerates a taint is not required to schedule onto a node
 ----
 metadata:
   name: example-vm-tolerations
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 spec:
   tolerations:
@@ -26,4 +26,4 @@ spec:
     value: "virtualization"
     effect: "NoSchedule"
 ...
-----
+----

modules/virt-importing-vm-datavolume.adoc

@@ -54,7 +54,7 @@ the virtual machine image you want to import. In this example, a Fedora image is
 +
 [source,yaml]
 ----
-apiVersion: kubevirt.io/v1alpha3
+apiVersion: kubevirt.io/v1
 kind: VirtualMachine
 metadata:
   creationTimestamp: null