<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubevirt on Thomas Peters</title><link>https://www.sirmysterion.com/tags/kubevirt/</link><description>Recent content in Kubevirt on Thomas Peters</description><generator>Hugo</generator><language>en</language><managingEditor>thomas@tnepeters.com (Thomas Peters)</managingEditor><webMaster>thomas@tnepeters.com (Thomas Peters)</webMaster><copyright>&lt;a href="https://creativecommons.org/licenses/by-nc/4.0/" target="_blank" rel="noopener"&gt;CC BY-NC 4.0&lt;/a&gt;</copyright><lastBuildDate>Mon, 06 Jul 2026 22:20:34 -0600</lastBuildDate><atom:link href="https://www.sirmysterion.com/tags/kubevirt/index.xml" rel="self" type="application/rss+xml"/><item><title>KubeVirt on Bare-Metal Talos: One Platform for VMs and Containers</title><link>https://www.sirmysterion.com/posts/20260223-kubevirt/</link><pubDate>Mon, 23 Feb 2026 00:00:00 +0000</pubDate><author>thomas@tnepeters.com (Thomas Peters)</author><guid>https://www.sirmysterion.com/posts/20260223-kubevirt/</guid><description>&lt;h1 id="the-problem"&gt;The Problem&lt;/h1&gt;
&lt;p&gt;I have been slowly migrating my Proxmox infrastructure to Kubernetes on Talos Linux.
Most workloads containerize just fine, but some things stubbornly remain VMs - appliances, one-off test boxes, anything that wants a full kernel of its own.
Running a whole separate Proxmox host for a handful of VMs means two platforms to patch, two backup strategies, and two ways to do networking.&lt;/p&gt;
&lt;p&gt;KubeVirt solves this by making VMs first-class Kubernetes resources.
The VM definition lives in git next to everything else, ArgoCD deploys it, and the same storage and network stack applies to both pods and VMs.&lt;/p&gt;</description></item></channel></rss>