Merge pull request #91316 from sbeskin-redhat/CNV_20188_mass_machine_type_change_procedure

CNV-20188: Mass machine type change procedure

Author: mburke5678

modules/virt-updating-multiple-vms.adoc

@@ -0,0 +1,87 @@
+// Module included in the following assemblies:
+//
+// * virt/virtual_machines/virt-edit-vms.adoc
+
+:_mod-docs-content-type: PROCEDURE
+[id="virt-updating-multiple-vms_{context}"]
+= Updating multiple virtual machines
+
+You can use the command line interface (CLI) to update multiple virtual machines (VMs) at the same time.
+
+.Prerequisites
+
+* You installed the `oc` CLI.
+* You have access to the {product-title} cluster, and you have `cluster-admin` permissions.
+
+.Procedure
+
+. Create a privileged service account by running the following commands:
++
+[source,terminal]
+----
+$ oc adm new-project kubevirt-api-lifecycle-automation
+----
++
+[source,terminal]
+----
+$ oc create sa kubevirt-api-lifecycle-automation -n kubevirt-api-lifecycle-automation
+----
++
+[source,terminal]
+----
+$ oc create clusterrolebinding kubevirt-api-lifecycle-automation --clusterrole=cluster-admin --serviceaccount=kubevirt-api-lifecycle-automation:kubevirt-api-lifecycle-automation
+----
+
+. Determine the pull URL for the `kubevirt-api-lifecycle` image by running the following command:
++
+[source,terminal]
+----
+$ oc get csv -n openshift-cnv -l=operators.coreos.com/kubevirt-hyperconverged.openshift-cnv -ojson | jq '.items[0].spec.relatedImages[] | select(.name|test(".*kubevirt-api-lifecycle-automation.*")) | .image'
+----
+
+. Deploy `Kubevirt-Api-Lifecycle-Automation` by creating a job object as shown in the following example:
++
+[source,yaml]
+----
+apiVersion: batch/v1
+kind: Job
+metadata:
+ name: kubevirt-api-lifecycle-automation
+ namespace: kubevirt-api-lifecycle-automation
+spec:
+ template:
+  spec:
+   containers:
+   - name: kubevirt-api-lifecycle-automation
+     image: quay.io/openshift-virtualization/kubevirt-api-lifecycle-automation:v4.19 <1>
+     imagePullPolicy: Always
+     env:
+     - name: MACHINE_TYPE_GLOB <2>
+       value: smth-glob9.10.0
+     - name: RESTART_REQUIRED <3>
+       value: "true"
+     - name: NAMESPACE <4>
+       value: "default"
+     - name: LABEL_SELECTOR <5>
+       value: my-vm
+     securityContext:
+      allowPrivilegeEscalation: false
+      capabilities:
+       drop:
+       - ALL
+      privileged: false
+      runAsNonRoot: true
+      seccompProfile:
+       type: RuntimeDefault
+   restartPolicy: Never
+   serviceAccountName: kubevirt-api-lifecycle-automation
+----
+
+<1> Replace the image value with your pull URL for the image.
+<2> Replace the `MACHINE_TYPE_GLOB` value with your own pattern. This pattern is used to detect deprecated machine types that need to be upgraded.
+<3> If the `RESTART_REQUIRED` emvironment variable is set to `true`, VMs are restarted after the machine type is updated. If you do not want VMs to be restarted, set the value to `false`.
+<4> The `namespace` environment value indicates the namespace to look for VMs in. Leave the parameter empty for the job to go over all namespaces in the cluster.
+<5> You can use the `LABEL_SELECTOR` environment variable to select VMs that receive the job action. If you want the job to go over all VMs in the cluster, do not assign a value to the parameter.
+
+
+

virt/managing_vms/virt-edit-vms.adoc

@@ -30,6 +30,8 @@ include::modules/virt-mounting-windows-driver-disk-on-vm.adoc[leveloffset=+1]
 
 include::modules/virt-adding-secret-configmap-service-account-to-vm.adoc[leveloffset=+1]
 
+include::modules/virt-updating-multiple-vms.adoc[leveloffset=+1]
+
 [discrete]
 [id="additional-resources-configmaps"]
 [role="_additional-resources"]