LinkedIn Replaces Argo CD with a Custom GitOps Engine for Kubernetes Deployments

7.1 relevance

LinkedIn replacing Argo CD with custom GitOps engine is a significant platform engineering case study.

Cloud infoq.com

Answer the board on AI readiness

Arrive with evidence, not opinion. See how your foundation benchmarks against your peers, get a clear read, and leave with a ranked place to start.

Why It Matters

For a platform engineer managing large-scale Kubernetes, this case study reveals the architectural limits of Argo CD's shared controller state and PATCH-based updates at hyperscale, and offers a concrete alternative pattern using ephemeral pods and full object replacement.

Key Takeaways

Evaluate replacing shared-controller GitOps engines with per-deployment ephemeral pods and PUT-based updates when scaling beyond 80,000 pods per cluster to eliminate cross-application sync interference and managedFields truncation issues.

LinkedIn Replaces Argo CD with a Custom GitOps Engine for Kubernetes Deployments

Summary

LinkedIn replaced Argo CD with a custom GitOps engine to manage over 250 Kubernetes clusters, 4,000 services, and 100,000 weekly deployments. The new engine runs each deployment in an ephemeral pod with no shared controller state, uses PUT for full replacements instead of PATCH, and performs a 3-way diff to detect drift. Deployment infrastructure failures dropped from 925 to 63 despite a 3.7x increase in deployment volume, and median time to detect failed deployments fell from 16.1 to 2.45 minutes.

Author

Claudio Masolo