<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Talos on khz</title><link>https://blog.khzaw.dev/tags/talos/</link><description>Recent content in Talos on khz</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 20 Feb 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://blog.khzaw.dev/tags/talos/index.xml" rel="self" type="application/rss+xml"/><item><title>Building a homelab kubernetes cluster</title><link>https://blog.khzaw.dev/posts/rangoonpulse-homelab-origin/</link><pubDate>Fri, 20 Feb 2026 00:00:00 +0800</pubDate><guid>https://blog.khzaw.dev/posts/rangoonpulse-homelab-origin/</guid><description>&lt;p&gt;I have self-hosted things before, but none of it really stuck. A &lt;a href="https://www.raspberrypi.com/products/raspberry-pi-4-model-b/"&gt;Raspberry Pi 4&lt;/a&gt; ran &lt;a href="https://pi-hole.net/"&gt;Pi-hole&lt;/a&gt; for a while, then an old laptop ran &lt;a href="https://www.plex.tv/"&gt;Plex&lt;/a&gt; for a while after that. Both were useful in the loose way side projects are useful. Every now and then, something would break, I would usually shrug, things fizzle out and I would just move on.&lt;/p&gt;
&lt;p&gt;This time round, I wanted to start something more serious. Something small, but with plenty of room to grow in whatever direction I felt like taking it, a testing ground for all sorts of learning experiments. I&amp;rsquo;d also GitOps it, so if I added a service, changed storage, or touched DNS, I wanted that change to live somewhere more durable than a vague memory of what I typed into a terminal. Nothing fancy, no rack, no enterprise gear. Just a small cluster for the services I actually use, with enough &lt;a href="https://kubernetes.io/"&gt;Kubernetes&lt;/a&gt; underneath it for me to learn something while running it.&lt;/p&gt;</description></item></channel></rss>