V for Vincent

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation Proving the entire platform with one blog Handing PostgreSQL over to Amp Modernizing an application, not merely moving it Replacing a surveillance media chain, not just a recorder Proving Frigate before the cutover Upgrading observability beyond the old cluster Building a platform agents can keep improving (this post) The point was not only to rebuild the homelab. It was to leave a platform that agents can keep improving safely. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation Proving the entire platform with one blog Handing PostgreSQL over to Amp Modernizing an application, not merely moving it Replacing a surveillance media chain, not just a recorder Proving Frigate before the cutover Upgrading observability beyond the old cluster (this post) The new stack explains what is happening inside Kubernetes. A separate host checks whether the platform can still be reached from outside it. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation Proving the entire platform with one blog Handing PostgreSQL over to Amp Modernizing an application, not merely moving it Replacing a surveillance media chain, not just a recorder Proving Frigate before the cutover (this post) The four-camera design and access checks passed. The broken 24-hour run kept the production gate closed. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation Proving the entire platform with one blog Handing PostgreSQL over to Amp Modernizing an application, not merely moving it Replacing a surveillance media chain, not just a recorder (this post) Frigate made the design much simpler, but it still had to meet the real needs of the old system. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation Proving the entire platform with one blog Handing PostgreSQL over to Amp Modernizing an application, not merely moving it (this post) Rewriting the application also meant finding a safe place to test it and putting authentication in front of it. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation Proving the entire platform with one blog Handing PostgreSQL over to Amp (this post) More than five years of history moved from the old cluster to the new one and was checked at both ends. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation Proving the entire platform with one blog (this post) One stateless blog acted as a test signal through the platform’s complete delivery path. After building the K3s control plane, I needed to find out whether the rest of the platform actually worked. I could have moved several applications at once and spent days wondering which layer was broken. Instead, I chose the simplest workload I had: this blog. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly Building the new K3s foundation (this post) The hardware stayed where it was. I reinstalled Raspberry Pi OS from scratch and rebuilt the cluster around a new control plane. ...

In this series Why I modernized my homelab instead of upgrading it Making a homelab repository agent-friendly (this post) Before an agent could work safely on the homelab, the repository needed to make the paved path—and its stopping points—visible. In Part I, I decided to rebuild the homelab with Amp. However, before I trusted it with Kubernetes, I wanted a much safer place to start: this blog. ...

In this series Why I modernized my homelab instead of upgrading it (this post) This is the start of a new series about rebuilding my homelab from the ground up. Later posts will cover the platform, applications, data and lessons from the journey. This first part is about the decision that shaped everything afterwards: I was not looking for a like-for-like upgrade. I wanted a full-scale modernization. Amp let me coordinate different parts of the rebuild across devices and environments. ...