Uploaded November 2026 | Updated November 2026, 9 hours ago
Connect with the cloud native community and explore CNCF events: kubecon.io
We Have GitOps at Home: How Meta Went from Terraform on Cron to GitOps for AI Infra - Phong Nguyen, Meta Platforms & Shaun Hopper, Meta (ASL)
At Meta, ~15 engineers run ~100 Kubernetes clusters for AI research & inference. Terraform exceeds expectations at its job: setting up infra for those clusters. The problem is its side gig: deploying the k8s apps. Even a one-line Helm values change can take a working day in our monolithic Terraform pipeline, where one stuck app can block dozens of others.
In the new model, Terraform didn't get fired, just reorged. Kargo and Argo CD take over the apps, so each app ships on its own and a routine update is live and healthy in minutes.
Terraform's side gig now comes down to installing ArgoCD. That's the easy part. The hard part is making GitOps work with Meta's internal systems: one-way config syncs from our in-house VCS to Git, an app "order form" instead of hand-written YAMLs, and multi-tenant ArgoCD(s) instead of one per cluster.
If your company also runs on many homegrown systems, our lessons can save you a few headaches.
Connect with the cloud native community and explore CNCF events: kubecon.io
We Have GitOps at Home: How Meta Went from Terraform on Cron to GitOps for AI Infra - Phong Nguyen, Meta Platforms & Shaun Hopper, Meta (ASL)
At Meta, ~15 engineers run ~100 Kubernetes clusters for AI research & inference. Terraform exceeds expectations at its job: setting up infra for those clusters. The problem is its side gig: deploying the k8s apps. Even a one-line Helm values change can take a working day in our monolithic Terraform pipeline, where one stuck app can block dozens of others.
In the new model, Terraform didn't get fired, just reorged. Kargo and Argo CD take over the apps, so each app ships on its own and a routine update is live and healthy in minutes.
Terraform's side gig now comes down to installing ArgoCD. That's the easy part. The hard part is making GitOps work with Meta's internal systems: one-way config syncs from our in-house VCS to Git, an app "order form" instead of hand-written YAMLs, and multi-tenant ArgoCD(s) instead of one per cluster.
If your company also runs on many homegrown systems, our lessons can save you a few headaches.










