https://forcebyte.github.io/tags/kubernetes/Recent content in kubernetes on 'That' badly designed HomeLabHugo -- gohugo.ioen-usFirehavenTue, 20 Oct 2026 13:30:00 -0400https://forcebyte.github.io/posts/2026-20-10-shikata-flux-images/Tue, 20 Oct 2026 13:30:00 -0400https://forcebyte.github.io/posts/2026-20-10-shikata-flux-images/Most of my homelab runs images tagged :latest, which is less a versioning strategy than a hope. For a long time, “updating” 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.https://forcebyte.github.io/posts/2026-20-10-shikata-backups/Tue, 20 Oct 2026 09:00:00 -0400https://forcebyte.github.io/posts/2026-20-10-shikata-backups/For a long time, my homelab backup strategy was “nothing here is irreplaceable,” which is a fine strategy right up until the day it isn’t. In my case the day came during a routine rebuild: a PersistentVolumeClaim got recreated, the volume underneath it went away with it, and my web analytics database — years of history — was just gone. Kubernetes defaults did exactly what they’re documented to do. The PVC had a Delete reclaim policy, the storage class agreed, and the data left.