https://khzaw.dev/tags/homelab/Recent content in Homelab on khzHugoen-usSat, 30 May 2026 00:00:00 +0800https://khzaw.dev/posts/how-i-access-the-things-i-self-host/Sat, 30 May 2026 00:00:00 +0800https://khzaw.dev/posts/how-i-access-the-things-i-self-host/<p>For the most part, all of the services that I self host in <a href="https://khzaw.dev/posts/rangoonpulse-homelab-origin/">my homelab cluster</a> are all deployed on their respective subdomains on my domain <code>khzaw.dev</code>.</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-text" data-lang="text"><span class="line"><span class="cl">jellyfin.khzaw.dev </span></span><span class="line"><span class="cl">grafana.khzaw.dev </span></span><span class="line"><span class="cl">vaultwarden.khzaw.dev </span></span><span class="line"><span class="cl">uptime.khzaw.dev </span></span></code></pre></div><p>Barring a few exceptions, all of these DNS would resolve to an internal private IP, <code>10.0.0.231</code>. Naturally, they are not accessible outside of my home LAN.</p> <h2 id="what-is-this-1000231-address">What is this <code>10.0.0.231</code> address?</h2> <p>This <code>10.0.0.231</code> address is the cluster&rsquo;s main entry point. It belongs to the <code>ingress-nginx-controller</code> service. The ingress controller is exposed as Kubernetes <code>Service</code> of type <code>LoadBalancer</code>.</p>https://khzaw.dev/posts/self-tuning-kubernetes-homelab/Sun, 22 Mar 2026 00:00:00 +0800https://khzaw.dev/posts/self-tuning-kubernetes-homelab/<p>Every so often, a pull request like this shows up.</p> <p><img src="https://khzaw.dev/img/self-tuning-kubernetes-homelab/pr-list_hu_356f2541029f30cc.webp" alt="A list of resource tuning pull requests opened automatically" loading="lazy" decoding="async" width="1332" height="540"></p> <p>The PR changes a handful of Kubernetes resource requests and limits in the HelmRelease manifests. The description spells out why each change got picked. It shows which containers look underfed, which ones sit on capacity they never touch, and whether the new state still fits on the nodes I actually have. None of that is me. I review it, merge it, and <a href="https://fluxcd.io/">Flux</a> rolls it out.</p>https://khzaw.dev/posts/rangoonpulse-homelab-origin/Fri, 20 Feb 2026 00:00:00 +0800https://khzaw.dev/posts/rangoonpulse-homelab-origin/<p>I have self-hosted things before, but none of it really stuck. A <a href="https://www.raspberrypi.com/products/raspberry-pi-4-model-b/">Raspberry Pi 4</a> ran <a href="https://pi-hole.net/">Pi-hole</a> for a while. Then an old laptop ran <a href="https://www.plex.tv/">Plex</a> for a while after that. Both were useful in the loose way side projects are useful. Something would break, I&rsquo;d shrug, it would fizzle out, and I&rsquo;d move on.</p> <p>This time I wanted something more serious. Small, but with room to grow in whatever direction I felt like, a testing ground for whatever I wanted to learn. I&rsquo;d GitOps it too. If I added a service, changed storage, or touched DNS, that change should 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 <a href="https://kubernetes.io/">Kubernetes</a> underneath to learn something while running it.</p>