Demos and production are different sports. This checklist covers what changes when Argo Workflows has to be reliable, secure and observable under real load.
Security and reliability defaults
- Scope the workflow ServiceAccount with least-privilege RBAC
- Use separate namespaces per team/tenant
A production-minded 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}}'] }Operational best practices
- Set limits and activeDeadlineSeconds on templates
- Use workflow GC (TTL) to clean up finished runs
- Store artifacts in object storage, not the cluster
In production, boring and reproducible beats clever every time.
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.