When Argo Workflows misbehaves, the cause is usually one of a handful of familiar issues. Here is how to spot and fix them fast.
The usual suspects
- No resource limits on step containers
- Unbounded retries hammering the cluster
- Keeping completed workflows forever, bloating etcd
Commands for diagnosis
argo submit -n argo build.yaml --watch
argo list -n argo
argo logs -n argo @latestPrevent the repeat
- Set limits and activeDeadlineSeconds on templates
- Use workflow GC (TTL) to clean up finished runs
- Store artifacts in object storage, not the cluster
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.