I Wanted Kubernetes Without an Always On EKS Bill

<p>My Kubernetes application moved from my home server to Amazon EKS without an application code change.</p> <p>The platform around it did not.</p> <p>The EKS control plane took

<p>Most homelab content stops at "I installed Proxmox on a NUC." This post goes further — how I built a multi-node cluster running a full Kubernetes platform with GPU inference,

<p><a class="article-body-image-wrapper"

<p>In <a href="https://peculiarengineer.com/blog/kubernetes-first-app-k3s-single-node/" rel="noopener noreferrer">Part One</a> I deployed nginx on a single k3s node and killed a

<p><a class="article-body-image-wrapper"

<p>Over two weeks I moved six self-hosted services from Docker Compose onto Kubernetes — ArgoCD, supply-chain policy, the whole GitOps loop. Then, in a single day, I moved all six

<p>ArgoCD deploys what's in Git. That's the whole point. It watches a repository, diffs the desired state against the cluster, and reconciles.</p> <p>The question nobody answers

<p>When using managed platforms like Google Kubernetes Engine (GKE), there are many things that you don’t have to worry about that it takes care of for you! But have you ever