<?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 heezy.blog</title><link>https://heezy.blog/tags/automation/</link><description>Recent content in Automation on heezy.blog</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 13 Apr 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://heezy.blog/tags/automation/index.xml" rel="self" type="application/rss+xml"/><item><title>About This Site</title><link>https://heezy.blog/posts/about-this-site/</link><pubDate>Mon, 13 Apr 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/about-this-site/</guid><description>&lt;p&gt;This site is built with &lt;a href="https://gohugo.io"&gt;Hugo&lt;/a&gt; using the &lt;a href="https://github.com/panr/hugo-theme-terminal"&gt;Terminal&lt;/a&gt; theme. The Hugo static site is compiled inside a Docker
multi-stage build, bundled into a &lt;a href="https://github.com/linuxserver/docker-swag"&gt;SWAG&lt;/a&gt; container image, pushed to Amazon ECR, and deployed to a MicroK8s cluster
via GitHub Actions. Source content lives in a Git repo and a push to main triggers the full build-and-deploy pipeline
automatically.&lt;/p&gt;</description></item><item><title>The Heezy: A Homelab That Got Out of Hand</title><link>https://heezy.blog/posts/the-heezy-architecture/</link><pubDate>Tue, 10 Mar 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/the-heezy-architecture/</guid><description>&lt;h2 id="contents"&gt;Contents&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#what-even-is-a-heezy"&gt;What Even Is a Heezy&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-network"&gt;The Network&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-kubernetes-cluster"&gt;The Kubernetes Cluster&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#what-runs-on-the-cluster"&gt;What Runs on the Cluster&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-dmz"&gt;The DMZ&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#monitoring"&gt;Monitoring&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#dns"&gt;DNS&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#infrastructure-as-code"&gt;Infrastructure as Code&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-aws-bootstrap-cdk-first-everything-else-after"&gt;The AWS Bootstrap: CDK First, Everything Else After&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#secrets"&gt;Secrets&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#what-id-do-differently"&gt;What I&amp;rsquo;d Do Differently&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://heezy.blog/posts/the-heezy-architecture/#the-name"&gt;The Name&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="what-even-is-a-heezy"&gt;What Even Is a Heezy&lt;/h2&gt;
&lt;p&gt;If you grew up in the early 2000s, you probably remember when Snoop Dogg had everyone adding &amp;ldquo;-izzle&amp;rdquo; to everything. &amp;ldquo;For sheezy&amp;rdquo; was peak vocabulary for a 12-year-old who spent too much time on Counter-Strike and not enough time on homework. &amp;ldquo;Heezy&amp;rdquo; rhymes with &amp;ldquo;easy,&amp;rdquo; which is what I told myself this project would be. It was not easy. But the name stuck, and now my entire infrastructure is named after slang that peaked in 2003. No regrets.&lt;/p&gt;</description></item><item><title>Running 25+ Services on a 5-Node MicroK8s Cluster</title><link>https://heezy.blog/posts/kubernetes-cluster-build-and-operations/</link><pubDate>Fri, 20 Feb 2026 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/kubernetes-cluster-build-and-operations/</guid><description>&lt;p&gt;This is the full story of building a MicroK8s cluster from scratch, migrating a Docker Compose stack onto it, and all the things that broke along the way. If you&amp;rsquo;re thinking about running Kubernetes at home for self-hosted services, this is what it actually looks like.&lt;/p&gt;</description></item><item><title>Terraform, Ansible, and the Automation That Runs Everything</title><link>https://heezy.blog/posts/terraform-ansible-automation/</link><pubDate>Sat, 20 Dec 2025 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/terraform-ansible-automation/</guid><description>&lt;p&gt;This is the story of taking a homelab that was 100% manually configured and turning it into something where every change is a git commit, every deployment is a GitHub Actions run, and I never SSH into a box to make a &amp;ldquo;quick fix&amp;rdquo; again. It took a lot of hours, a lot of broken credential chains, and one memorable incident where I leaked secrets because of echo output. But it works now, and it works well.&lt;/p&gt;</description></item><item><title>Lab Modernization: From Manual Configs to Full Automation</title><link>https://heezy.blog/posts/lab-modernization-journal/</link><pubDate>Thu, 18 Sep 2025 00:00:00 +0000</pubDate><guid>https://heezy.blog/posts/lab-modernization-journal/</guid><description>&lt;p&gt;This is the journal of taking a homelab that was held together with SSH sessions and good intentions and turning it into something that manages itself. It took months of evenings and weekends, a lot of broken things, and more hours than I want to admit. But the lab went from &amp;ldquo;I hope nobody touches that server&amp;rdquo; to &amp;ldquo;push to main and walk away.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>