<?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 victorhang</title><link>https://banh-canh.github.io/tags/cluster-api/</link><description>Recent content in Cluster-Api on victorhang</description><generator>Hugo</generator><language>en_US</language><lastBuildDate>Sun, 28 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://banh-canh.github.io/tags/cluster-api/index.xml" rel="self" type="application/rss+xml"/><item><title>Chihiro: A ConfigMap-Driven Web UI for Cluster API</title><link>https://banh-canh.github.io/posts/chihiro-forms/</link><pubDate>Sun, 28 Jun 2026 00:00:00 +0000</pubDate><guid>https://banh-canh.github.io/posts/chihiro-forms/</guid><description>&lt;p&gt;The &lt;a href="https://banh-canh.github.io/posts/rpcu-bootstrap/" &gt;previous post&lt;/a&gt; ended with a teaser: a follow-up on Chihiro, the web UI for creating and managing CAPI workload clusters. This is that post. It covers how Chihiro works under the hood, starting with the fact that the form itself is configuration, not code.&lt;/p&gt;
&lt;h2 id="the-starting-point"&gt;
 The starting point
 &lt;a class="heading-link" href="#the-starting-point"&gt;
 &lt;i class="fa-solid fa-link" aria-hidden="true" title="Link to heading"&gt;&lt;/i&gt;
 &lt;span class="sr-only"&gt;Link to heading&lt;/span&gt;
 &lt;/a&gt;
&lt;/h2&gt;
&lt;p&gt;Before Chihiro, creating a workload cluster meant writing a &lt;code&gt;Cluster&lt;/code&gt; manifest by hand and applying it with &lt;code&gt;kubectl&lt;/code&gt;. That works fine if you are the only user and you have the YAML memorized. It does not scale to a team, and it does not inspire confidence in people who would rather click a button than parse a CRD schema.&lt;/p&gt;</description></item></channel></rss>