[{"data":1,"prerenderedAt":76},["ShallowReactive",2],{"work-en-kubernetes-platform":3},{"id":4,"title":5,"body":6,"client":52,"description":46,"extension":53,"locale":54,"meta":55,"metric":56,"navigation":57,"order":47,"path":58,"role":59,"seo":60,"slug":61,"stack":62,"stem":69,"summary":70,"tags":71,"year":74,"__hash__":75},"work\u002Fwork\u002Fkubernetes-platform.md","GitOps Kubernetes Platform",{"type":7,"value":8,"toc":45},"minimark",[9,14,18,22,25,38,42],[10,11,13],"h2",{"id":12},"the-problem","The problem",[15,16,17],"p",{},"Product teams were blocked on a hand-managed cluster: slow deploys, scary rollbacks, and infra knowledge locked in one head.",[10,19,21],{"id":20},"what-i-built","What I built",[15,23,24],{},"A GitOps platform where the repo is the source of truth. Merges reconcile the cluster automatically; rollbacks are a git revert.",[26,27,28,32,35],"ul",{},[29,30,31],"li",{},"Declarative infra in Terraform; app delivery via ArgoCD",[29,33,34],{},"S3 + lifecycle policies for durable, cheap object storage",[29,36,37],{},"Golden-path templates so teams ship services without learning Kubernetes",[10,39,41],{"id":40},"outcome","Outcome",[15,43,44],{},"Deploys went from a careful weekly event to many-a-day, rollbacks became boring, and the platform kept running whether or not I was online.",{"title":46,"searchDepth":47,"depth":47,"links":48},"",2,[49,50,51],{"id":12,"depth":47,"text":13},{"id":20,"depth":47,"text":21},{"id":40,"depth":47,"text":41},"Series-A SaaS","md","en",{},"Deploy frequency up 6×, rollback in seconds",true,"\u002Fwork\u002Fkubernetes-platform","Platform · Cloud",{"title":5,"description":46},"kubernetes-platform",[63,64,65,66,67,68],"Kubernetes","AWS","S3","ArgoCD","Terraform","GitHub Actions","work\u002Fkubernetes-platform","Designed and ran a GitOps Kubernetes platform on AWS — S3-backed storage, self-healing deploys, and a golden-path for product teams to ship without touching infra.",[72,63,73],"Platform","GitOps","2026","nXHgFEubHy6Pkh7ZZHwS1XxOiTO6v1Vci_YgkpkjRlQ",1784975504009]