selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

Argo CD logo

Self-host Argo CD

v3.6.1

GitOps continuous delivery controller for Kubernetes

ReleaseOpen SourceApache-2.0
Updatedlast week
LanguageGo
Setup difficultyModerate
Stars
24 622
Port
443 (argocd-server API server / web UI (HTTPS); the guide reaches it with kubectl port-forward mapping local 8080 to 443)
Docker
quay.io/argoproj/argocd
Install with Kubernetes
Applications page with the + New App button highlightedForm for app name, project and sync policy when creating an applicationRepository connection settings (URL, revision, path) in the new-app formDetail panel of the example guestbook application with the Sync actionResource tree view of a deployed application

What is Argo CD?

Argo CD is a continuous delivery tool that runs inside a Kubernetes cluster and treats Git repositories as the authoritative source for the desired state of applications. Its controller keeps comparing the live state against what is in Git, flags anything OutOfSync, and re-applies the desired state automatically or on demand, with automated drift detection, health assessment of resources, and rollback to any configuration committed in the repository. Manifests can be Kustomize applications, Helm charts, Jsonnet files, plain YAML directories, or any custom tool added through config management plugins, and one instance can manage and deploy to many clusters. Day-to-day operation happens through the real-time web UI or the argocd CLI; human login supports SSO via OIDC, OAuth2, LDAP and SAML 2.0, secured further by multi-tenancy and RBAC policies, plus audit trails, Prometheus metrics, webhooks from GitHub, GitLab and BitBucket, and a notification engine for services like Slack, email and Opsgenie. Self-hosting is done by applying the official install.yaml manifests with kubectl (namespace-scoped, high-availability and headless 'core' bundles also exist), through Kustomize, or via the community-maintained argo-helm chart; the default bundle ships Redis with password authentication. The non-HA installation is explicitly described as suited for evaluation rather than production use.

Should you self-host Argo CD?

Argo CD scores 81/100 on selfhost.directory (how scoring works) and ranks #2 of 28 in CI/CD. It has 24 622 GitHub stars, +238 in the last 30 days.

It shipped 35 stable releases in the past year. The latest, v3.6.1, came out on 4 November 2026. New versions land roughly every 1 days.

Setup is moderate: expect some configuration beyond a single command. An official Docker image is available. It is Apache-2.0-licensed and written mostly in Go.

Its closest alternative on selfhost.directory is jenkins (83/100, 26 779 stars). It scores higher overall, so compare the two before you pick. See Argo CD vs jenkins side by side.

Features

  • Audit Trails
  • Automated and manual sync
  • CLI for automation
  • Configuration Drift Detection
  • GitOps-based deployment from Git
  • Git webhooks
  • Multi-Cluster Management
  • Multi-format manifest support (Kustomize, Helm, Jsonnet, plain YAML)
  • Prometheus Metrics
  • RBAC and multi-tenancy
  • Real-time web UI
  • Resource health analysis
  • Rollback to any Git revision
  • SSO Integration
  • Sync lifecycle hooks

Argo CD README

Releases: Release Version Artifact HUB SLSA 3

Code: Integration tests codecov CII Best Practices OpenSSF Scorecard

Social: Twitter Follow Slack LinkedIn Bluesky

Argo CD - Declarative Continuous Delivery for Kubernetes

What is Argo CD?

Argo CD is a declarative GitOps continuous delivery tool for Kubernetes.

Argo CD UI

How to install Argo CD

Install Argo CD with Kubernetes

kubectl and a kubeconfig file (default location ~/.kube/config); CoreDNS
kubectl create namespace argocd
kubectl apply -n argocd --server-side --force-conflicts -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml

Alternative manifest sets: namespace-install.yaml (namespace-level privileges), ha/install.yaml for production high availability, core-install.yaml for headless use, Kustomize as a remote resource, or the community-maintained argo-helm chart.

How to configure Argo CD

  • ARGOCD_SERVERthe address of the Argo CD server without https:// prefix (instead of specifying --server for every command) eg. ARGOCD_SERVER=argocd.example.com if served through an ingress with DNS
  • ARGOCD_AUTH_TOKENthe Argo CD apiKey for your Argo CD user to be able to authenticate
  • ARGOCD_OPTScommand-line options to pass to argocd CLI eg. ARGOCD_OPTS="--grpc-web"
  • ARGOCD_CONFIG_DIRsets the directory hosting argocd CLI config, e.g., ~/.config/argocd/config. (if ENV var not provided, defaults to $XDG_CONFIG_HOME/argocd, or ~/.config/argocd, or if exists legacy ~/.argocd)
  • ARGOCD_SERVER_NAMEthe Argo CD API Server name (default "argocd-server")

Argo CD releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

FAQ

How Do I Fix invalid cookie, longer than max length 4093?

The auth token is a JWT cookie listing your groups, and belonging to many groups exceeds the 4KB cookie limit; decode the callback token from the browser's network tab and leave some groups.

Why is my ArgoCD application Out Of Sync when there are no actual changes to the resource limits (or other fields with unit values)?

Kubernetes normalizes unit values (e.g. 1000m becomes 1, 3072Mi becomes 3Gi), so the rendered Git manifests no longer match the live objects; diff customizations address this.

How often does Argo CD check for changes to my Git or Helm repository ?

By default it polls roughly every three minutes (120s plus up to 60s jitter); timeout.reconciliation in argocd-cm adjusts the interval, and 0 disables polling so only webhooks or manual refreshes trigger checks.

Why Is My App Out Of Sync Even After Syncing?

Tools that add the app.kubernetes.io/instance label themselves (e.g. Kustomize common labels) collide with the label Argo CD injects to track resources; change the key via application.instanceLabelKey in argocd-cm.

How Can I Terminate A Sync?

In the UI, open the synchronization control and then choose terminate.

Argo CD is unable to connect to my cluster, how do I troubleshoot it?

Exec into an Argo CD pod, generate the cluster's kubeconfig with argocd admin cluster kubeconfig and test the connection manually with kubectl from inside the pod.

I've configured cluster secret but it does not show up in CLI/UI, how do I fix it?

Verify the secret carries the argocd.argoproj.io/secret-type: cluster label; if it does but the cluster is still invisible, it is likely a permission issue, so list clusters with the admin user.

After deploying my Helm application with Argo CD I cannot see it with helm ls and other Helm commands

Argo CD uses Helm only to render templates and then applies the resulting manifests itself, so the release does not exist in Helm; Argo CD natively covers history and rollback instead.

Argo CD cannot deploy Helm Chart based applications without internet access, how can I solve it?

Charts with dependencies in external repositories can fail offline; keep requirements.yaml on internal repos and, as a workaround, override the stable repo URL in the argocd-cm ConfigMap.

How to view orphaned resources?

Orphaned monitoring is enabled per AppProject from the Projects settings in the UI (with a warning about performance on broadly scoped namespaces); once on, orphaned resources surface in the application's sync panel via Show Orphaned.

How to disable admin user?

Set admin.enabled to "false" in the argocd-cm ConfigMap.

I forgot the admin password, how do I reset it?

On v1.9+ the initial password lives in the argocd-initial-admin-secret secret; you can patch a new bcrypt hash into argocd-secret, or delete the password keys and restart argocd-server to regenerate one.

Why is my application stuck in Progressing state?

Known health-check quirks with Ingress, StatefulSet and SealedSecret (e.g. controllers not populating status fields) can keep resources in Progressing; custom health checks let you override the default behavior.

Why is my application still OutOfSync immediately after a successful Sync?

The FAQ points to the diffing documentation, which explains the reasons resources can remain OutOfSync and how to make Argo CD ignore expected field differences.

I've deleted/corrupted my repo and can't delete my app.

Argo CD cannot delete an application whose manifests it can no longer generate, so either restore the repository or delete the app with --cascade=false and remove the resources manually.

More in CI/CD

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…