Code In, Cluster Out: Building Reproducible Edge Kubernetes with NixOS, K3s, and Forgejo

What if your entire Kubernetes edge cluster, from the kernel to the workload, was a single reproducible function? No drift. No snowflakes. No, "this node got fixed manually six months ago, and nobody remembers how." Just code in, cluster out. That question led me into a project that combines: infrastructure-nixos for the Raspberry Pi-hosted Forgejo control path edge-cluster-infra for Oracle networking, compute, and block storage infrastructure-secrets for the shared SOPS-managed secret layer nix