<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Automation on Beyond The Cert</title><link>https://beyondthecert.dev/tags/automation/</link><description>Recent content in Automation on Beyond The Cert</description><generator>Hugo</generator><language>en</language><lastBuildDate>Sun, 24 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://beyondthecert.dev/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>From 10 Days to 30 Minutes: Why I Automated My Bare Metal Kubernetes Cluster</title><link>https://beyondthecert.dev/posts/from-10-days-to-30-minutes/</link><pubDate>Sun, 24 May 2026 00:00:00 +0000</pubDate><guid>https://beyondthecert.dev/posts/from-10-days-to-30-minutes/</guid><description>&lt;p>When people ask me what made me decide to automate my homelab cluster, they expect a story about frustration — some late night where everything broke and I snapped. That&amp;rsquo;s not what happened.&lt;/p>
&lt;p>The first time I built a bare metal Kubernetes cluster manually, it took me a week and countless hours. Manual steps, configuration files, troubleshooting, and learning. And when it was done, I looked at it and thought: the next evolution of this is automation. Not because I was tired of doing it manually — but because I wanted to be able to reproduce it at a moment&amp;rsquo;s notice.&lt;/p></description></item></channel></rss>