Setting Up ArgoCD for GitOps: What Actually Works in Production

I pushed a broken Helm chart on a Friday afternoon last October. Not my finest moment. The cluster had three microservices that needed coordinated config updates, I was in a hurry, and I did what I always did: SSH into the jump box, run a bunch of kubectl apply -f commands, and hope for the best. The deploy partially succeeded, partially failed, and I spent the next two hours reverse-engineering what state the cluster was actually in versus what I thought I'd applied. That was the last time I managed Kubernetes deployments that way. Our team is small — four engineers, two clusters (staging and prod), maybe 15 microservices across them. Not massive scale, but enough complexity that "just apply the YAML manually" stopped being a viable strategy months before I finally admitted it. ArgoCD was something I'd been circling for a while, read a dozen tutorials about, and kept putting off because it looked complicated. Setting it up properly took me about two weeks of on-and-off work. This post