← All insightsCheat Sheet

Argo Workflows cheat sheet: the complete command reference

CodeWizard Engineering · 30 October 2025 · 3 min read · Beginner

This is a complete, hands-on Argo Workflows cheat sheet: install, configure, operate, automate and secure it - with copy-paste commands grouped by task. Bookmark it for day-to-day work, incidents and interviews alike.

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 you reach for it

  • Every step is a container, scheduled on Kubernetes
  • DAG and step templates for complex pipelines
  • Scales with the cluster; no separate CI fleet

Installation

bash
kubectl create namespace argo
kubectl apply -n argo -f https://github.com/argoproj/argo-workflows/releases/latest/download/install.yaml

Configuration reference

A DAG workflow with dependencies.

yaml
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}}'] }

Core commands you use daily

bash
argo submit -n argo build.yaml --watch
argo list -n argo
argo logs -n argo @latest

Submit & inspect

bash
argo submit -n argo build.yaml --watch
argo list -n argo
argo get -n argo @latest
argo logs -n argo @latest -f
argo retry -n argo @latest
argo delete -n argo --completed

Templates & cron

bash
argo submit --from workflowtemplate/ci -p revision=$SHA -n argo
argo cron list -n argo
argo template list -n argo

Use it in CI/CD

Trigger workflows from events with Argo Events.

bash
argo submit --from workflowtemplate/ci -p revision=$GIT_SHA -n argo

Best-practice checklist

  • Set limits and activeDeadlineSeconds on templates
  • Use workflow GC (TTL) to clean up finished runs
  • Store artifacts in object storage, not the cluster

Common pitfalls to avoid

  • No resource limits on step containers
  • Unbounded retries hammering the cluster
  • Keeping completed workflows forever, bloating etcd

Security quick wins

  • Scope the workflow ServiceAccount with least-privilege RBAC
  • Use separate namespaces per team/tenant

Works well with

  • Jenkins - The extensible automation server for CI/CD, with pipelines defined as code in a Jenkinsfile.
  • Kubernetes - Declarative orchestration for containers at scale - self-healing, rolling updates and service discovery.
  • Argo CD - GitOps continuous delivery for Kubernetes - Git is the source of truth, the cluster is reconciled to match.
A cheat sheet is muscle memory on paper - keep it close until the commands live in your fingers.

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.

Like where this is going?

Get hands-on help from the engineers who write these posts.

Book a free consult