From VMs to GitOps: Managing KubeVirt Workloads Declaratively with ArgoCD
summary
Shows how KubeVirt VM manifests live in Git and are pushed by ArgoCD to provision, update, scale and live migrate VMs; demonstrates declarative specs for CPU/memory/storage, a concrete example of 50 Ubuntu VMs created from a manifest, and how ArgoCD detects drift, displays out‑of‑sync state and performs auto-sync and rollback. Covers integrating alerts/Prometheus, multi‑env overlays, and practical notes on attaching persistent volumes and external storage.
AI-written summary · about
chapters (12)
- 0:00GitOps for KubeVirt workloads
- 1:02Managing VMs like containers
- 2:28GitOps steps for KubeVirt
- 3:53VM lifecycle automation
- 5:17GitOps implementation details
- 6:23Multi-tenancy and consistency
- 7:26Eliminating configuration drift
- 8:51Safe rollback
- 9:55Modernizing with KubeVirt
- 11:20Key takeaways
- 12:24Mindset shift for VMs
- 13:07Q&A
related talks
39mGitOps — How to Marry Git and Kubernetes for Deployment and Operations
42mVirtual Machine Orchestration in Kubernetes Utilizing KubeVirt
30mManage your kubernetes cluster in the GITOPS way !!
18mKubeVirt Alchemy: Transform VMs into K8s Workloads
32mGitOps, an Elegant Tool for Hybrid Cloud Kubernetes
34mImplementing GitOps on Kubernetes: ArgoCD
43mMaking Running Virtual Machines in a Kubernetes Cluster a Mainstream Activity
27mExploring Argo