<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Automation on khz</title><link>https://khzaw.dev/tags/automation/</link><description>Recent content in Automation on khz</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sun, 22 Mar 2026 00:00:00 +0800</lastBuildDate><atom:link href="https://khzaw.dev/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>A self-tuning homelab</title><link>https://khzaw.dev/posts/self-tuning-kubernetes-homelab/</link><pubDate>Sun, 22 Mar 2026 00:00:00 +0800</pubDate><guid>https://khzaw.dev/posts/self-tuning-kubernetes-homelab/</guid><description>&lt;p&gt;Every so often, a pull request like this shows up.&lt;/p&gt;
&lt;p&gt;&lt;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"&gt;&lt;/p&gt;
&lt;p&gt;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 &lt;a href="https://fluxcd.io/"&gt;Flux&lt;/a&gt; rolls it out.&lt;/p&gt;</description></item></channel></rss>