Demystifying Argo Workflows: An Architectural Deep Dive
summary
Argo Workflows runs as two deployments plus eight CRDs and a controller that watches workflow CRs, creates pods for each step (typically one workflow step = one pod) and uses leader election for HA or per-namespace controllers to split load. The Argo Server provides API/UI, Dex SSO, archive offloading and CLI access. Each step pod has init, main and wait containers with the Argo exec main container calling user commands; examples use MinIO or cloud object storage and operators report successful orchestration.
AI-written summary · about
chapters (15)
- 0:00Intro
- 0:12Overview
- 5:27Workflow Controller
- 12:24Argo Server
- 12:39Kubernetes
- 13:19Why is it important
- 14:09Resource utilization
- 15:21What happens inside a pod
- 16:14Examples
- 16:56Templates
- 17:33Weight Container
- 17:48Summary
- 18:21Where to get started
- 19:32Jetstack Consult
- 20:06Outro
related talks
27mLeveraging Argo Workflows To Move, Migrate and Manage All of Your Workflows
25mOne Engine To Rule Them All: Unifying Cloud Workloads With Argo Workflows
05mArgo Workflows 4, What's New And What's Next
23mDemystifying Argo Events: An Architectural Deep Dive
27mBuilding a Data Science Platform with Argo Workflows
30mArgo’s Vibrant Ecosystem and Community
25mEvolving Argo Workflows for AI: New Features, Tuning, and Multi-Tenant Isolation
29mLarge Scale Batch Processing with Argo Work...