Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 37 ยท Getting Started

Installing Argo CD: kubectl, Helm and Local Clusters

Install Argo CD on a local kind cluster or a real cluster with the official manifests or the Helm chart, log in the first time, and choose between standard, HA and core installs.

You can try Argo CD on a laptop in about ten minutes. All you need is a Kubernetes cluster, kubectl, and network access to GitHub. This lesson shows the supported installation routes, how to reach the UI and how to get the first admin password. Production hardening comes later in the course.

The commands below are read-only here because the site has no cluster. Run them in your own terminal. The runnable blocks are stand-ins: a chooser and a readiness checker that work on sample text, not on a real cluster.

Prerequisites

  • A cluster: Docker Desktop's Kubernetes, kind, minikube or k3d are fine for learning. For example: kind create cluster --name gitops.
  • kubectl configured to talk to it (kubectl get nodes should answer).
  • Optionally the argocd CLI and helm.

Install with the official manifest

Create a namespace and apply the install manifest published with each release:

Terminal
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts \
  -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

--server-side is recommended because some of Argo CD's custom resource definitions are larger than the client-side apply annotation limit. In real use, replace stable with a release tag such as v3.0.0 (check the project's releases page for the current one) so installs are repeatable.

Wait until the pods are ready:

Terminal
kubectl get pods -n argocd

You should see pods for the application controller, server, repo server, Redis, Dex, ApplicationSet controller and notifications controller, all Running.

Choose a flavor

Flavor Manifest Use it for
Standard (cluster-wide) manifests/install.yaml Normal use: UI, API, SSO, can manage the cluster it runs in and others.
Namespace-scoped manifests/namespace-install.yaml Multi-tenant clusters where you cannot grant cluster-wide roles.
HA manifests/ha/install.yaml Production: several replicas, Redis HA. Needs at least three nodes.
Core manifests/core-install.yaml Headless: only the controllers, no UI, API or Dex.

The stand-in below turns a few questions into a recommendation. Change the inputs and re-run it.

JS Stand-in: pick an install flavor

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Install with Helm

The community-maintained chart lives in the argo-helm repository and gives you a values.yaml for configuration, which is handy for GitOps-managed installs later:

Terminal
helm repo add argo https://argoproj.github.io/argo-helm
helm repo update
helm install argocd argo/argo-cd --namespace argocd --create-namespace

Customize with --values my-values.yaml; helm show values argo/argo-cd lists every option.

Reach the UI

A fresh install does not expose the server outside the cluster. For learning, use a port forward:

Terminal
kubectl port-forward svc/argocd-server -n argocd 8080:443

Open https://localhost:8080. The certificate is self-signed, so your browser will warn you; that is expected locally. For real use you will add an Ingress or a LoadBalancer with a proper certificate (see Operations and Patterns later in the course).

First login

The built-in admin user gets a random password, stored in a Secret that you read once:

Terminal
argocd admin initial-password -n argocd
# or, without the CLI:
kubectl -n argocd get secret argocd-initial-admin-secret \
  -o jsonpath="{.data.password}" | base64 -d

Log in on the command line with argocd login localhost:8080 --username admin --insecure (the --insecure flag skips TLS verification for the local self-signed certificate; never use it in production). Then change the password with argocd account update-password and delete the initial secret, since it is no longer needed:

Terminal
kubectl -n argocd delete secret argocd-initial-admin-secret

In production you would disable admin and use SSO instead (Security and RBAC is covered later).

Checking readiness

Before you start, make sure every pod is ready. The stand-in checks sample kubectl get pods output (pasted below, not live) for pods that are not Running with all containers ready.

JS Stand-in: readiness checker

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Install the CLI

The argocd CLI is a single binary from the project's releases page (or brew install argocd on macOS and Homebrew-enabled Linux). Check it with argocd version; the next lesson tours the CLI and UI.

Removing it again

Delete Applications first (so the resources they manage are cleaned up as you intend), then remove the namespace with kubectl delete namespace argocd. The custom resource definitions are cluster-wide and stay behind until you delete them separately.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why does the install command use --server-side?

    Large CRDs exceed the last-applied annotation size limit of client-side apply, so server-side apply is recommended.
  2. 2. Which install flavor has no UI or API server?

    core-install.yaml installs only the controllers for headless use.
  3. 3. Where is the initial admin password stored?

    A random password is generated on install and saved in that Secret. Change it and delete the Secret afterwards.
  4. 4. What does kubectl port-forward svc/argocd-server -n argocd 8080:443 do?

    A port forward is a private tunnel from your machine, good for learning and quick checks.

Summary

  • Install with the official manifest (kubectl apply --server-side) or the argo/argo-cd Helm chart.
  • Pick standard, namespace-scoped, HA or core to match your environment; pin a release tag.
  • Use a port forward for the first visit; add an Ingress with TLS for real use.
  • Read the initial admin password once, change it, then delete the Secret.
  • Wait until every pod in the argocd namespace is ready.

Next: The Argo CD UI and CLI