<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Firewalld on Chris Wagner</title><link>/tags/firewalld/</link><description>Recent content in Firewalld on Chris Wagner</description><generator>Hugo -- gohugo.io</generator><language>en</language><managingEditor>cw@wagner.org.za (Chrisando Wagner)</managingEditor><webMaster>cw@wagner.org.za (Chrisando Wagner)</webMaster><copyright>© 2026 Chrisando Wagner</copyright><lastBuildDate>Tue, 28 Jul 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/firewalld/index.xml" rel="self" type="application/rss+xml"/><item><title>Building an HA k3s Control Plane on Ubuntu 24.04 LTS: Terraform, Ansible, kube-vip, and a Real Failover Drill</title><link>/posts/k3s-enterprise/</link><pubDate>Tue, 28 Jul 2026 00:00:00 +0000</pubDate><author>cw@wagner.org.za (Chrisando Wagner)</author><guid>/posts/k3s-enterprise/</guid><description>&lt;p&gt;This is the latest iteration of my homelab automation: Terraform provisions six Ubuntu 24.04 LTS VMs on Proxmox, Ansible turns three of them into an HA k3s control plane with embedded etcd and a kube-vip floating VIP, and ArgoCD takes over GitOps management of everything above the OS the moment the cluster is up. It&amp;rsquo;s IaC end to end — nothing in this post was clicked into existence, and the two commands that matter (&lt;code&gt;terraform apply&lt;/code&gt;, &lt;code&gt;ansible-playbook site.yml&lt;/code&gt;) are the only manual steps in the whole build.&lt;/p&gt;</description></item></channel></rss>