<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Debugging on Rusty Bower</title><link>https://www.rustybower.com/categories/debugging/</link><description>Recent content in Debugging on Rusty Bower</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© Rusty Bower</copyright><lastBuildDate>Tue, 08 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.rustybower.com/categories/debugging/index.xml" rel="self" type="application/rss+xml"/><item><title>How K3s Silently Grew a 40 GB SQLite Database and Took Down My Cluster</title><link>https://www.rustybower.com/posts/k3s-sqlite-kine-40gb-database-compaction/</link><pubDate>Tue, 08 Sep 2026 00:00:00 +0000</pubDate><guid>https://www.rustybower.com/posts/k3s-sqlite-kine-40gb-database-compaction/</guid><description>&lt;p&gt;My cluster — a single-node K3s instance running about 60 ArgoCD-managed applications — had been slowly dying for months. Pods crash-looped with &amp;ldquo;context deadline exceeded&amp;rdquo; errors. Leader elections failed. The metrics server stopped working entirely. I assumed it was resource pressure and tuned probe timeouts. The real problem was underneath all of it: K3s&amp;rsquo;s SQLite datastore had silently grown to 40 GB.&lt;/p&gt;</description></item><item><title>The LoadBalancer That Never Worked: Migrating MetalLB from L2 to BGP</title><link>https://www.rustybower.com/posts/metallb-l2-to-bgp-migration-udm-pro/</link><pubDate>Thu, 30 Jul 2026 00:00:00 +0000</pubDate><guid>https://www.rustybower.com/posts/metallb-l2-to-bgp-migration-udm-pro/</guid><description>&lt;p&gt;I started the day asking why one of my Frigate cameras was using more CPU than the others. I finished it having moved every LoadBalancer in my Kubernetes cluster onto BGP-routed addresses, because along the way I found a service that had been silently unreachable for two years.&lt;/p&gt;</description></item></channel></rss>