Update pictures

Author: Martin Jackson

content/patterns/virtualization-starter-kit/getting-started.md

@@ -135,48 +135,26 @@ The screen should like this when installed via `make install`:
 
 * Check all applications are synchronised
 
-Under the project `virtualization-starter-kit-hub` click on the URL for the `hub`gitops`server`. All applications will sync, but this takes time as ODF has to completely install, and OpenShift Virtualization cannot provision VMs until the metal node has been fully provisioned and ready. Additionally, the Dynamic Provision Kiosk Template in AAP must complete; it can only start once the VMs have provisioned and are running:
+Open the Hub ArgoCD instance from the nine-grid links menu. All applications will sync, but this takes time as ODF has to completely install, and OpenShift Virtualization cannot provision VMs until at least one metal node has been fully provisioned and ready.
 
-![virtualization-starter-kit-applications](/images/virtualization-starter-kit/aeg-applications.png "Ansible Edge GitOps Applications")
+![virtualization-starter-kit-applications](/images/virtualization-starter-kit/vsk-applications.png "Virtualization Starter Kit Applications")
 
-* While the metal node is building, the VMs in OpenShift console will show as "Unschedulable." This is normal and expected, as the VMs themselves cannot run until the metal node completes provisioning and is ready.
+* While the metal node is building, the VMs in OpenShift console may not show up, or may show as "Unschedulable." This is normal and expected, as the VMs themselves cannot run until the metal node completes provisioning and is ready.
 
-![ansible-edge-vms-unschedulable](/images/virtualization-starter-kit/aeg-vm-unschedulable.png "Ansible Edge GitOps Unschedulable VMs")
+* Under Virtualization > Virtual Machines, the virtual machines will eventually show as "Running." No additional configuration is done to the VMs beyond instantiating them; they are provided so you can do things like LiveMigrate them or do other virtualization "day 2" activities.
 
-* Under Virtualization > Virtual Machines, the virtual machines will eventually show as "Running." Once they are in "Running" state the Provisioning workflow will run on them, and install Firefox, Kiosk mode, and the Ignition application on them:
-
-![virtualization-starter-kit-vmlist](/images/virtualization-starter-kit/aeg-openshift-vm-screen.png "Ansible Edge GitOps VM List")
-
-* Finally, the VM Consoles will show the Ignition introduction screen. You can choose any of these options; this tutorial assumes you chose "Ignition":
-
-![virtualization-starter-kit-ignition-options](/images/virtualization-starter-kit/aeg-vm-ignition-intro.png "Ansible Edge GitOps Ignition Options")
-
-* You should be able to login to the application with the userid "admin" and the password you specified as the GATEWAY_ADMIN_PASSWORD in `container_extra_params` in your values-secret.yaml file.
-
-![virtualization-starter-kit-vmconsole](/images/virtualization-starter-kit/aeg-openshift-vm-console.png "Ansible Edge GitOps VM Console")
+![virtualization-starter-kit-vmlist](/images/virtualization-starter-kit/vsk-openshift-vm-screen.png "Virtualization Starter Kit VM List")
 
 Please see [Installation Details](/virtualization-starter-kit/installation-details/) for more information on the steps of installation.
 
-Please see [Ansible Automation Platform](/virtualization-starter-kit/ansible-automation-platform/) for more information on how this pattern uses the Ansible Automation Platform Operator for OpenShift.
-
 Please see [OpenShift Virtualization](/virtualization-starter-kit/openshift-virtualization/) for more information on how this pattern uses OpenShift Virtualization.
 
 # Infrastructure Elements of this Pattern
 
-## [Ansible Automation Platform](https://www.redhat.com/en/technologies/management/ansible)
-
-A fully functional installation of the Ansible Automation Platform operator is installed on your OpenShift cluster to configure and maintain the VMs for this demo. AAP maintains a dynamic inventory of kiosk machines and can configure a VM from template to fully functional kiosk in about 10 minutes.
-
-## OpenShift [Virtualization](https://docs.openshift.com/container-platform/4.10/virt/about-virt.html)
+## OpenShift [Virtualization](https://docs.openshift.com/container-platform/4.18/virt/about-virt.html)
 
 OpenShift Virtualization is a Kubernetes-native way to run virtual machine workloads. It is used in this pattern to host VMs simulating an Edge environment; the chart that configures the VMs is designed to be flexible to allow easy customization to model different VM sizes, mixes, versions and profiles for future pattern development.
 
-## Inductive Automation [Ignition](https://inductiveautomation.com/)
-
-The goal of this pattern is to configure 2 VMs running Firefox in Kiosk mode displaying the demo version of the Ignition application running in a podman container. Ignition is a popular tool in use with Oil and Gas companies; it is included as a real-world example and as an item to spark imagination about what other applications could be installed and managed this way.
-
-The container used for this pattern is the container [image](https://hub.docker.com/r/inductiveautomation/ignition) published by Inductive Automation.
-
 ## HashiCorp [Vault](https://www.vaultproject.io/)
 
 Vault is used as the authoritative source for the Kiosk ssh pubkey via the External Secrets Operator.