<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Cluster-Api on Anish Bista</title><link>https://anishbista.org/tags/cluster-api/</link><description>Recent content in Cluster-Api on Anish Bista</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 06 Nov 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://anishbista.org/tags/cluster-api/index.xml" rel="self" type="application/rss+xml"/><item><title>From Hosts to Clusters: Cluster API Provider Metal3 on KubeVirtBMC</title><link>https://anishbista.org/blog/capm3-on-kubevirtbmc/</link><pubDate>Fri, 06 Nov 2026 00:00:00 +0000</pubDate><guid>https://anishbista.org/blog/capm3-on-kubevirtbmc/</guid><description>&lt;p>I built a Kubernetes cluster on top of another Kubernetes cluster. The bottom cluster runs KubeVirt, its VMs act as bare metal servers, and everything from powering them on to upgrading the cluster is automated.&lt;/p>
&lt;p>In &lt;a href="https://www.cncf.io/blog/2026/09/02/metal3-meets-kubevirtbmc-provisioning-kubevirt-vms-like-bare-metal/">Metal3 meets KubeVirtBMC&lt;/a>, we took a single KubeVirt VM through the Metal3 BareMetalHost lifecycle. This post goes one layer up. You declare a Kubernetes cluster with Cluster API, and &lt;a href="https://github.com/metal3-io/cluster-api-provider-metal3">Cluster API Provider Metal3 (CAPM3)&lt;/a> picks hosts from a pool of KubeVirt &amp;ldquo;bare metal&amp;rdquo; servers, has Ironic write an OS image to them over Redfish virtual media, and runs kubeadm.&lt;/p></description></item></channel></rss>