Argo CD & GitOps — Trivia & Interesting Facts¶
Surprising, historical, and little-known facts about Argo CD and GitOps.
GitOps was coined by Weaveworks CEO in 2017¶
Alexis Richardson, CEO of Weaveworks, coined the term "GitOps" in an August 2017 blog post titled "GitOps - Operations by Pull Request." The concept formalized what some teams were already doing — using Git as the single source of truth for declarative infrastructure — and gave it a catchy name.
Weaveworks, the company that coined GitOps, went bankrupt¶
In a twist of irony, Weaveworks — the company that coined "GitOps" and built Flux — shut down in February 2024 after failing to secure additional funding. The GitOps movement they started continued to thrive through Argo CD and the CNCF-hosted Flux project.
Argo CD was created because Flux v1 didn't have a UI¶
One of the original motivations for creating Argo CD at Intuit was that Flux (the existing GitOps tool) lacked a graphical interface. Intuit engineers wanted a visual representation of application state and sync status. The Argo CD UI, showing a real-time resource tree, became one of its most distinguishing features.
Argo CD syncs by polling Git every 3 minutes by default¶
Argo CD's default reconciliation interval is 3 minutes, meaning it polls Git repositories for changes rather than receiving push notifications. This surprised many users who expected real-time sync. Webhooks can be configured for near-instant reconciliation, but the polling default was chosen for simplicity and reliability.
The "app of apps" pattern was discovered, not designed¶
The "app of apps" pattern — where one Argo CD Application manages other Application resources — emerged organically from the community rather than being an intentional design feature. Users discovered they could bootstrap entire clusters by pointing Argo CD at a single "root" application that referenced others.
ApplicationSets solved a problem that affected 90% of large deployments¶
Before ApplicationSets (added in Argo CD 2.3), organizations managing more than 10 clusters had to manually create and maintain individual Application resources for each cluster-app combination. The ApplicationSet controller, originally a separate project, automated this and was cited by the Argo team as addressing complaints from 90% of large-scale users.
Argo CD has over 17,000 GitHub stars¶
By 2024, Argo CD had accumulated over 17,000 GitHub stars, making it one of the most popular Kubernetes ecosystem projects. It consistently ranks in the top 5 CNCF projects by contributor count and was one of the fastest projects to move from CNCF Incubating to Graduated status.
The drift detection algorithm compares normalized manifests¶
Argo CD's drift detection doesn't simply diff YAML files — it applies Kubernetes-style normalization, removing server-set fields like creationTimestamp and resourceVersion. Getting this normalization right was one of the hardest engineering challenges, and edge cases in drift detection remain the most common source of bug reports.
Config Management Plugins were deprecated because they were a security nightmare¶
Argo CD's Config Management Plugin (CMP) v1 allowed arbitrary sidecar containers to run during manifest generation, creating a significant attack surface. The team deprecated CMP v1 in favor of CMP v2 (sidecar-based), which provided better isolation. The original design was described internally as "giving users a footgun."
GitOps doesn't require Git¶
Despite the name, "GitOps" principles can work with any version control system. Argo CD supports Git and Helm repositories, and some organizations have experimented with OCI registries as the source of truth. The "Git" in GitOps refers more to the workflow pattern (declarative, versioned, auditable) than the specific VCS tool.