This repository is an example of managing KubeVirt virtual machines and datavolumes using a GitOps workflow, specifically using ArgoCD as provided by OpenShift GitOps.
Where possible, namespaces and resource names have been left variable for portability, but since this is in support of an OpenShift blog, the default leans to OpenShift products and namespaces.
Under the setup directory, there are a number of scripts to help in an OpenShift GitOps deployment.
To run everything, use install.sh without any arguments.
This script will:
- Discover the ArgoCD namespace and configuration CR names.
- Install health check scripts that ArgoCD uses to better track status of custom resources.
More in-depth descriptions may be found in the README
Other directories in this repository are designed to support Applications in ArgoCD. Each of these directories contains a kustomization.yaml and an application.yaml.
Under the kubevirt directory is an ArgoCD application and manifests to install KubeVirt on a Kubernetes cluster.
Under virtualization are manifests to create an OpenShift Virtualization installation using the OpenShift Operator Lifecycle Manager (OLM).
The datavolumes directory contains DataVolume manifests which will download specific cloud images of Fedora and CentOS 8 Stream for use as boot sources for OpenShift Virtualization's included OS templates.
The vms directory works with the DataVolumes provided in datavolumes to create a Fedora and CentOS VM.
The win2k19 directory holds an application and manifests for creating a boot source image of a Microsoft Windows 2019 Server VM.
This application requires a MS Windows 2019 Server installation ISO be downloaded and shared using a local web service accessible only to the cluster. The URL for the ISO is found in install-iso.yaml and should be changed for the local environment. Alternatively, the ISO may be manually uploaded to the kubevirt-gitops namespace as a DV, and the install-iso.yaml entry removed from kustomization.yaml.
Installation scripts can be found in config, including a job script which runs once the ISO is available, creates the VM, waits for it to shut down, and then copies the installed root disk into the boot source namespace. A short script is provided at regen-configmap.sh that updates the ConfigMap supplied by the repo. If any changes are made, run the script to regenerate the ConfigMap, and make sure to check in any changes for ArgoCD to see them.