VM Dashboard

How image tags stay current

Each entry in the dashboard reads the image tag straight from its Kubernetes manifest — KubeVirt VirtualMachine specs for the VM cards, the kasm-vpn Deployment for KASM workspaces, and the firecracker manifests for the microVM rows. Tags are pinned (no :latest), so what you see is exactly what’s running.

Bumps happen automatically: each tracked image has a version.toml + an MDX entry under /project/ referencing the manifest via deployment_yaml. After CI publishes a new tag, a post-publish chore PR rewrites the pin and ArgoCD rolls the pod. Card image strings (e.g.

kasm-void:0.0.1

) link back to the project page where the env knobs and recovery behaviour live.