← All insightsConcepts

Argo Workflows: core concepts and configuration explained

CodeWizard Academy · 7 November 2025 · 3 min read · Beginner

Kubernetes-native workflow engine for CI, batch and ML pipelines defined as DAGs. This walkthrough covers the mental model and the configuration you will actually touch.

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.

The configuration that matters

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

Principles to hold onto

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

Everyday commands

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

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