Skip to main content
In this lesson you’ll learn how to deploy Helm charts with Argo CD and how Argo CD integrates with Helm to implement GitOps-style, declarative application delivery. Helm is the Kubernetes package manager that packages applications as charts and defines them declaratively — a core principle of GitOps. Argo CD can deploy and continuously monitor Helm charts from several sources, including:
  • a Git repository where the chart lives under a specific repo path, or
  • a Helm chart repository (public or private), such as Bitnami or Artifactory.
For full reference:

​
Typical Helm chart layout

A simple Helm chart directory looks like this:
What these files do:

​
How Argo CD consumes Helm charts

Argo CD treats Helm as a manifest generator: it renders chart templates (using provided values) and applies the generated Kubernetes manifests to the target cluster. You can reference Helm charts from:
  • Git repository (chart files inside a repo path)
  • Helm chart repository (using chart name and optional revision)
Below are step-by-step examples for both approaches.

​
Create an Argo CD application from a Git repository

Steps:
  1. Point Argo CD at the Git repository URL.
  2. Set the repo path that contains the chart.
  3. Optionally override chart values using --helm-set or a values file.
Example: create an application named random-shapes from the repo path helm-chart, overriding a few values:
Expected CLI response:

​
Create an Argo CD application from a Helm chart repository

Steps:
  1. Add the Helm chart repository to Argo CD (use --type helm for Helm repos).
  2. Create an application referencing the chart name in that repo; optionally specify a chart revision and a values file.
Example: add the Bitnami chart repository to Argo CD, then create an application from the nginx chart at a specific revision:

​
Manage deployments via the Argo CD UI

  • The Argo CD web UI provides forms to create and manage applications, including Helm chart options and value overrides.
  • UI supports repository connections using SSH, HTTPS, and GitHub App authentication.
  • Whether created via CLI or UI, Argo CD continuously monitors the desired state in Git (or the chart repo) and reconciles changes to the cluster.
Once Argo CD deploys and manages a Helm chart, Argo CD becomes the source of truth for that application’s lifecycle. Use the Argo CD CLI or the UI to inspect, sync, and manage the application state rather than local Helm client commands.

​
Important: Helm CLI vs Argo CD-managed apps

When Argo CD deploys Helm charts, Argo CD renders the manifests and applies them to the cluster using its reconciliation engine. Argo CD does not create Helm release records in cluster storage the way a local Helm CLI install does. As a result:
  • helm list typically will not show applications managed by Argo CD.
  • Use Argo CD commands and the Argo CD UI for authoritative application metadata and status.
To inspect an Argo CD-managed application:
Example: helm ls output may be empty for Argo CD-managed apps:
Do not rely on helm list to determine the state of applications managed by Argo CD. Always use argocd app get or the Argo CD UI for authoritative application status and metadata.

​
Quick reference — Argo CD + Helm

Watch Video