Helm and Argo CD are a common pairing in a modern DevOps stack. Here is how they fit together and a practical way to wire them up.
Where Helm fits
Helm packages Kubernetes manifests into versioned, parameterized 'charts' so you can install, upgrade and roll back an entire application with a single command and a values file.
# templates/deployment.yaml
spec:
replicas: {{ .Values.replicaCount }}
template:
spec:
containers:
- name: {{ .Chart.Name }}
image: "{{ .Values.image.repo }}:{{ .Values.image.tag }}"
---
# values.yaml
replicaCount: 3
image:
repo: ghcr.io/acme/web
tag: "1.0"Where Argo CD fits
Argo CD is a Kubernetes controller that continuously compares the live cluster to manifests in Git and syncs any drift, giving you declarative, auditable, self-healing deployments.
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata: { name: web, namespace: argocd }
spec:
project: default
source:
repoURL: https://github.com/acme/deploy.git
targetRevision: main
path: apps/web
destination:
server: https://kubernetes.default.svc
namespace: web
syncPolicy:
automated: { prune: true, selfHeal: true }
syncOptions: [CreateNamespace=true]Making them work together
- Pin dependency versions in Chart.yaml and commit Chart.lock
- Use --atomic and --wait so failed upgrades roll back automatically
- Adopt app-of-apps to manage many Applications declaratively
- Enable selfHeal + prune so the cluster always matches Git
Want this pairing set up properly, with docs and handover? That is exactly the kind of work CodeWizard's embedded senior engineers do - and both Helm and Argo CD have active community groups you can join for free.