• Sources: primary, discussion
  • Summary: Meta engineers say their research and inference clusters were built from about 12 Terraform layers that also deployed most Helm charts, so a stuck DaemonSet or a cloud SDK error could block an unrelated values change. They now keep Terraform for cloud resources, Kargo for promotion and a managed internal Argo CD service for deployment, with a tool called Catch that exports internal monorepo configs and merges layered Helm values into Git. A pipeline.yaml abstraction asks developers only what to deploy, where, and how to roll out.
  • Why it matters: It is a first-hand argument for keeping Terraform out of in-cluster app delivery, relevant to anyone running Argo CD alongside infrastructure as code.
  • Background: Argo CD continuously reconciles Kubernetes clusters to manifests stored in Git, while Kargo promotes versions of those manifests through stages such as dev and production. Both expect Git as the source of truth, which is why Meta needed a bridge from its internal monorepo.