Course contentsShow
← Cloud and Infrastructure
Lesson 1879 of 2,98940. ArgoCDFree lesson

Installing ArgoCD on Kubernetes

Install ArgoCD in a Kubernetes cluster using manifests or Helm charts.

Installing ArgoCD on Kubernetes

You'll learn: How to deploy ArgoCD in your Kubernetes cluster using two standard installation methods.

The Installation Challenge

Now that you understand ArgoCD's architecture, it's time to actually deploy it. ArgoCD runs inside your Kubernetes cluster as a set of services and controllers. Think of it like installing a control tower inside an airport—it becomes part of the infrastructure it manages. You have two main installation paths: direct manifest application or Helm charts.

Installation Method 1: Using Manifests

The quickest way is applying ArgoCD's official manifest:

# Create argocd namespace
kubectl create namespace argocd

# Install ArgoCD
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

This deploys all ArgoCD components—API server, repo server, application controller, and Redis—in one command. It's like unpacking a pre-configured appliance.

Installation Method 2: Using Helm

For more customization, use the official Helm chart:

# Add ArgoCD Helm repository
helm repo add argo https://argoproj.github.io/argo-helm
helm repo update

# Install with Helm
helm install argocd argo/argo-cd --namespace argocd --create-namespace

Helm gives you easy access to configuration values for resource limits, replicas, and ingress settings.

Post-Installation Access

Access the ArgoCD UI by retrieving the initial admin password:

# Get initial password
kubectl -n argocd get secret argocd-initial-admin-secret -o jsonpath="{.data.password}" | base64 -d

# Port-forward to access UI
kubectl port-forward svc/argocd-server -n argocd 8080:443

Visit https://localhost:8080 and log in with username admin and the retrieved password.

Key Takeaway: ArgoCD installs as a Kubernetes application itself, deployable via manifests for simplicity or Helm for customization, and runs continuously in your cluster to manage other applications.