Argo Workflow Configuration Checker

Check Argo Workflows YAML against production best practices: service accounts, deadlines, TTL, podGC, resources, pinned images, secrets and v4 deprecations. Free, no sign-up, and everything runs privately in your browser.

How to use the configuration checker

  1. Paste a Workflow, WorkflowTemplate or CronWorkflow, or load the sample with deliberate problems.
  2. Click Check configuration to score it against production best practices.
  3. Fix items marked Error first (security), then Warnings (reliability), then Info (polish).
  4. Re-run until the score is green, and download the report for your review.

Manifest

Best-practice report

    How the score is calculated

    Each rule has a weight that reflects its impact. Security issues such as privileged containers, secrets in plain environment variables or secret-looking parameters carry the most weight and appear as errors. Reliability issues — missing deadlines, cleanup settings, resource requests or pinned images — appear as warnings. Polish items such as labels, exit handlers and runAsNonRoot appear as information. The score is the share of weighted rules your manifest passes, so a few serious problems lower it much more than several minor ones.

    Rules at a glance

    • Dedicated serviceAccountName
    • activeDeadlineSeconds, ttlStrategy and podGC
    • Resource requests and memory limits on every container or script
    • No :latest or untagged images
    • No privileged containers and no plain-text secrets
    • parallelism when loops fan out
    • CronWorkflow policies: concurrency, starting deadline and timezone
    • Fields removed in version 4.0

    When a workflow uses workflowTemplateRef, workflow-level checks are treated as satisfied because those settings normally live in the referenced template — check the template itself as well.

    Frequently asked questions

    Is a score of 100 required?

    No. Treat errors as must-fix and use judgement on the rest; some information items may not apply to your environment.

    How is this different from the validator?

    The validator answers “will this run?”. The checker answers “should this run in production?”.

    Can I run these checks in CI?

    The tool runs in the browser. For CI, combine argo lint with a policy engine such as Kyverno or OPA Gatekeeper using similar rules.

    More free tools