<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>flux on 'That' badly designed HomeLab</title><link>https://forcebyte.github.io/tags/flux/</link><description>Recent content in flux on 'That' badly designed HomeLab</description><generator>Hugo -- gohugo.io</generator><language>en-us</language><copyright>Firehaven</copyright><lastBuildDate>Tue, 20 Oct 2026 13:30:00 -0400</lastBuildDate><atom:link href="https://forcebyte.github.io/tags/flux/index.xml" rel="self" type="application/rss+xml"/><item><title>ShikataLab - Updating Containers Without Restarting Everything: Flux Image Automation</title><link>https://forcebyte.github.io/posts/2026-20-10-shikata-flux-images/</link><pubDate>Tue, 20 Oct 2026 13:30:00 -0400</pubDate><guid>https://forcebyte.github.io/posts/2026-20-10-shikata-flux-images/</guid><description>Most of my homelab runs images tagged :latest, which is less a versioning strategy than a hope. For a long time, &amp;ldquo;updating&amp;rdquo; those containers meant a CronJob whose entire job was to restart things. It worked, in the sense that a hammer works. This is the story of replacing it with Flux Image Automation — where the cluster watches the registries itself, and every image update arrives as a small, boring, revertible git commit.</description></item></channel></rss>