<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>GitOps on Packets &amp; Regrets</title><link>https://matijazezelj.github.io/packets-and-regrets/tags/gitops/</link><description>Recent content in GitOps on Packets &amp; Regrets</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Sun, 19 Jul 2026 20:10:00 +0200</lastBuildDate><atom:link href="https://matijazezelj.github.io/packets-and-regrets/tags/gitops/index.xml" rel="self" type="application/rss+xml"/><item><title>Why the Lab Is Boring on Purpose</title><link>https://matijazezelj.github.io/packets-and-regrets/posts/why-the-lab-is-boring-on-purpose/</link><pubDate>Sun, 19 Jul 2026 20:10:00 +0200</pubDate><guid>https://matijazezelj.github.io/packets-and-regrets/posts/why-the-lab-is-boring-on-purpose/</guid><description>&lt;p&gt;The current lab is mostly Docker Compose, HAProxy, PostgreSQL, ZFS, and shell scripts.&lt;/p&gt;
&lt;p&gt;That sentence would have embarrassed an earlier version of me. The previous version ran Talos Kubernetes with Flux because Kubernetes was interesting, GitOps was fashionable, and apparently a family photo library needed a control plane.&lt;/p&gt;
&lt;p&gt;The cluster worked. It also turned every small operational question into a distributed-systems question. Eventually the useful lesson became obvious: a home lab should optimize for the operator&amp;rsquo;s time, not for the number of CNCF logos in its diagram.&lt;/p&gt;</description></item></channel></rss>