Hello all,
I have created an issue [1] and a PR [2] to Argo Project's Argo-CD to support adding health checks for KubeVirt custom resources, specifically VM, VMI, and CDI's DV.
This makes it possible to more accurately reflect the state of VMs and DataVolumes within ArgoCD's sync loop (and provides nice information in the UI).
For example, without the health check, a VM is considered healthy as soon as the manifest is applied to Kubernetes, regardless of whether there is an actual VMI running, scheduled, or unschedulable.
I would appreciate some reviews from the KubeVirt community. The goal here is not to be completely exhaustive in our edge case coverage, but to cover the major reasons why a synchronization may not be considered complete.
Thanks!
--
Chandler Wilkerson, RHCE, CKA
Sr. Software Engineer
Red Hat