Dog Food Delight: How Argo Workflows Eats Its Own CI
summary
A migration from GitHub Actions to Argo Workflows replaces external binaries with in-cluster test runners, uses buildkit + vcluster to create 10 virtual clusters in one host cluster, and exercises real Kubernetes RBAC (including added Windows nodes). Tests run comparable or slightly faster than upstream and cost about ~$2.50 per run. Implementation uses an NFS share for step data, Spiegel for image caching, kube-janitor and Argo exit handlers for cleanup, and found/fixed an Argo 3.6 bug.
AI-written summary · about
chapters (7)
- 0:00Argo Workflows CI intro
- 3:52Why dog food CI
- 7:44vcluster for test envs
- 12:40CI implementation challenges
- 19:22Lessons from Argo tests
- 20:26Future CI open source plans
- 21:52Q&A
related talks
27mThe Life of an Argo Workflows Salesperson
33mScaling to Thousands of Data & CI/CD Pipelines Using Argo and Virtual...
25mHow to Multiply the Power of Argo Projects By Using Them Together
25mMigrating CI/CD from Jenkins to Argo
12mLightning Talk: Migrating 1,300 Jenkins Jobs To Argo Workflows: Lessons From a…
26mGitOps Me Some of That! Managing Hundreds of Clusters with Argo CD
39mBuild and Deploy Your Application with Argo on Kubernetes
25mArgo Workflows in Action: Rabobank's Journey to Cloud Native Banking