Skip to main content
In this lesson you’ll install Argo Workflows into a Kubernetes cluster, expose the Argo Server for local access, and install the matching argo CLI so you can interact with the server and run workflows. Start by opening the Argo Workflows documentation and navigating to the Getting Started page.
A browser screenshot of the Argo Workflows documentation homepage, showing the header/navigation and a main article titled "What is Argo Workflows?" with bullet points and a right-hand table of contents.

1. Choose a release and install the quick-start

Pick an Argo Workflows release (this guide uses v3.7.3). The quick-start minimal manifest creates the Workflow Controller, Argo Server, example services (httpbin), bundled MinIO artifact store, and the required CRDs. Commands to install:
Typical (condensed) output from applying the manifest:

2. What the quick-start deploys

MinIO provided in the quick-start is suitable for demos and testing. For production systems, configure Argo to use a durable artifact repository (S3/GCS) and supply appropriate credentials.

3. Expose the Argo Server (optional)

By default the argo-server Service is a ClusterIP. To access the UI from your workstation you can:
  • Change the Service to NodePort, or
  • Use kubectl port-forward, or
  • Add an Ingress/LoadBalancer in cloud environments.
Interactive example: edit the service to NodePort:
Verify services and pods:
Wait until the argo-server pod is Running and Ready before continuing.

4. Install the Argo CLI

Download the matching argo CLI binary for your OS. The example below auto-detects macOS vs Linux; adjust the ARGO_WORKFLOWS_VERSION if needed.
Expected (condensed) output:

5. Configure the CLI to talk to the Argo Server

If you exposed the Argo Server via NodePort (for example 2746 -> 30774), set environment variables so the CLI uses the Argo Server rather than the Kubernetes API. Adjust values for your environment:
Test the connection by listing workflows:

6. Access the web UI

  • Open your browser to https://localhost:<NODEPORT> (e.g., https://localhost:30774) if you used NodePort.
  • Accept any self-signed certificate warnings (the quick-start ships with demo certificates).
  • The UI shows an initial “Tell us what you want to use Argo for” dialog on fresh installs and an empty workflow dashboard.
A screenshot of the Argo Workflows web UI with a modal asking "Tell us what you want to use Argo for" and showing selectable tiles like Machine Learning, Data Processing, Stream Processing, CI/CD, Infrastructure Automation, and Other. The blurred dashboard and sidebar are visible in the background with a "No workflows" message.

7. Next steps and common commands

  • Submit example workflows from the Argo docs or local YAML files: argo submit -n argo <workflow.yaml>
  • Inspect and manage workflows: argo list, argo get <workflow>, argo logs -w <workflow>
  • Define reusable WorkflowTemplates and scheduled CronWorkflows.
  • Replace the bundled MinIO with a production artifact store (S3/GCS) by updating the Argo config map and providing credentials.
Common commands: That completes the installation and initial setup of Argo Workflows. You can now deploy and run example workflows via the CLI or the Web UI.

Watch Video