Argo Workflows runs container-native, DAG or step-based workflows directly on Kubernetes - great for CI, data processing and ML pipelines where each step is a container.
Why teams use it
- Every step is a container, scheduled on Kubernetes
- DAG and step templates for complex pipelines
- Scales with the cluster; no separate CI fleet
Install it
kubectl create namespace argo
kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/latest/download/install.yamlA first working config
A DAG workflow with dependencies.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata: { generateName: build- }
spec:
entrypoint: main
templates:
- name: main
dag:
tasks:
- { name: build, template: run, arguments: { parameters: [{ name: cmd, value: make build }] } }
- { name: test, template: run, dependencies: [build], arguments: { parameters: [{ name: cmd, value: make test }] } }
- name: run
inputs: { parameters: [{ name: cmd }] }
container: { image: alpine, command: [sh, -c], args: ['{{inputs.parameters.cmd}}'] }Run and verify
argo submit -n argo build.yaml --watch
argo list -n argo
argo logs -n argo @latestMistakes to avoid early
- No resource limits on step containers
- Unbounded retries hammering the cluster
- Keeping completed workflows forever, bloating etcd
Want senior help putting Argo Workflows to work - or a team bootcamp on it? CodeWizard runs Israel's largest DevOps community and embeds named senior engineers with a transparent hours log. Book a free consult or explore the Academy.