Skip to main content
This guide compares installation choices for Argo Workflows: minimal vs production installs, cluster-wide vs namespace-scoped deployments, and how to install the argo CLI to manage workflows from your terminal. It preserves examples using the v3.7.2 release; always verify the latest release at the Argo Workflows releases page before installing.

​
Minimal vs Production install

Minimal and production installs target different use cases. Use the minimal install to get started quickly or for local development; choose the production install for stable, long-running clusters with proper persistence, observability, and security. Example commands (v3.7.2)
  • Minimal (quick-start) install — creates the argo namespace and applies the minimal quick-start manifest:
  • Production install — full install manifest from the release (includes production-oriented defaults):
Choose the minimal install for fast experimentation. For production, use the full install manifest, configure a persistent artifact repository (S3/MinIO/etc.), and follow the official Argo Workflows documentation for securing RBAC and multi-tenant setups: https://argoproj.github.io/argo-workflows/security/

​
Scopes: cluster-wide vs namespace-scoped

Decide whether you want a centralized controller that manages all namespaces (cluster-wide) or isolated controllers per namespace (namespace-scoped).
  • Cluster-wide installation (default)
    • Single controller with visibility across all namespaces.
    • Simplifies administration and shared control plane for multiple teams.
    • Requires cluster-scoped RBAC.
  • Namespace-scoped installation
    • Controller is restricted to a single namespace and limited RBAC.
    • Useful for stricter isolation between environments (dev/test/prod) or for multi-tenant setups where teams manage their own controllers.
    • Implementation details and exact manifests for fully namespaced installs vary between releases.
Quick comparison: Note: The exact steps to achieve a fully namespaced installation (avoiding cluster-scoped RBAC) can change between releases. Always consult the release notes and official docs for the recommended namespaced manifest or flags for your target release.
When attempting a namespace-scoped installation, consult the Argo Workflows release notes (https://github.com/argoproj/argo-workflows/releases) and documentation (https://argoproj.github.io/argo-workflows/) for release-specific instructions to avoid unintentionally granting cluster-scoped privileges.

​
Install and use the argo CLI

The argo CLI lets you submit, manage, and inspect workflows from your terminal. Below is an example for Linux using the v3.7.2 release. Replace the version string with the release you intend to use, or fetch the latest from the releases page. Linux example:
Platform alternatives
  • macOS: download the darwin binary for your architecture or install via Homebrew if the formula matches the desired release.
  • Windows: download the Windows binary and add it to your PATH.
Basic argo CLI examples
  • Submit a workflow:
    • argo submit -n argo my-workflow.yaml
  • List workflows:
    • argo list -n argo
  • View workflow logs:
    • argo logs -n argo <workflow-name>
Use the official docs and release notes as your source of truth for manifests, version-specific flags, and recommended production configuration patterns.

Watch Video