Day 5: Helm Sources
Goal: A third-party Helm chart runs through Argo CD, first with values in the Application, then with values from the fleet repo via multiple sources. · Duration: approx. 45 min · Prerequisite: Day 3
Briefing
- Instead of a Git path, a source can be a Helm chart
from a chart repo:
repoURLis the chart repo,chartthe name,targetRevisionthe chart version. - Argo CD does not run
helm install. The repo-server renders the chart withhelm template, and Argo CD applies the result like any other manifest. That is why there is no Helm release in the cluster. - Values live either in the Application (
valuesObject) or in a file. If the file is in a different repo than the chart, you need multiple sources: one source for the chart, a second one withref, which the first refers to with$name. - Today’s example is podinfo, a small demo program with a web UI and a public chart.
Application podinfo
sources[0]: Chart podinfo 6.16.0 ── valueFiles: $fleet/values/podinfo.yaml
sources[1]: argocd-fleet (main) ── ref: fleet ──────────────┘
Drill 1: Look at the Chart
You only need Helm on the VM to look at the chart beforehand:
helm repo add podinfo https://stefanprodan.github.io/podinfo
helm search repo podinfo --versions | head -4Expected:
"podinfo" has been added to your repositories
NAME CHART VERSION APP VERSION DESCRIPTION
podinfo/podinfo 6.17.0 6.17.0 Podinfo Helm chart for Kubernetes
podinfo/podinfo 6.16.0 6.16.0 Podinfo Helm chart for Kubernetes
podinfo/podinfo 6.15.0 6.15.0 Podinfo Helm chart for Kubernetes
helm show values shows which values the chart knows. You
put them in a file and look for the places you are about to set:
mkdir -p ~/argo-lab/tag05
cd ~/argo-lab/tag05
helm show values podinfo/podinfo --version 6.16.0 > podinfo-werte.yaml
wc -l podinfo-werte.yaml
grep -n "replicaCount:" podinfo-werte.yaml
grep -n "message:" podinfo-werte.yaml
grep -n "nodePort:" podinfo-werte.yamlExpected:
322 podinfo-werte.yaml
3:replicaCount: 1
19: message: ""
42: nodePort: 31198
You deliberately use 6.16.0 and not the newest version. The update comes in the challenge.
Save your progress? Sign up for free
Drill 2: Chart with Values in the Application
cat > podinfo-app.yaml <<'EOF'
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: podinfo
namespace: argocd
spec:
project: default
source:
repoURL: https://stefanprodan.github.io/podinfo
chart: podinfo
targetRevision: 6.16.0
helm:
valuesObject:
ui:
message: Hallo aus Argo CD
service:
type: NodePort
nodePort: 30090
destination:
server: https://kubernetes.default.svc
namespace: podinfo
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true
EOF
kubectl apply -f podinfo-app.yaml
argocd app wait podinfo --healthExpected (abridged):
application.argoproj.io/podinfo created
…
Sync Status: Synced to 6.16.0
…
GROUP KIND NAMESPACE NAME STATUS HEALTH HOOK MESSAGE
Namespace podinfo Running Synced namespace/podinfo created
Service podinfo podinfo Synced Healthy service/podinfo created
apps Deployment podinfo podinfo Synced Healthy deployment.apps/podinfo created
A public chart repo does not need to be registered.
Synced to 6.16.0 names the chart version instead of a
commit.
curl -s localhost:30090 | grep -E '"version|"message'Expected:
"version": "6.16.0",
"message": "Hallo aus Argo CD",
In the browser, http://172.16.0.182:30090 shows the
podinfo web UI with your message.
Save your progress? Sign up for free
Drill 3: No Helm Release
helm list -AExpected:
NAME NAMESPACE REVISION UPDATED STATUS CHART APP VERSION
gateway-api-crd kube-system 1 2026-11-14 08:10:31.54139108 +0000 UTC deployed gateway-api-crd-1.6.301 v1.6.3
podinfo is missing. The only release was created by k3s itself during installation. For Helm, podinfo does not exist; for Argo CD it is an ordinary Application with two objects:
argocd app manifests podinfo | grep "^kind:"Expected:
kind: Service
kind: Deployment
It follows that helm upgrade and
helm rollback have no business here. Argo CD translates
Helm hooks in the chart into its own hooks, for example
pre-install into PreSync.
Save your progress? Sign up for free
Drill 4: Values from Git
Values in the Application are convenient, but the Application is not in Git yet. It is better to put the values into the fleet repo as a file:
cd ~/argo-lab/argocd-fleet
mkdir -p values
cat > values/podinfo.yaml <<'EOF'
replicaCount: 2
ui:
message: Werte aus Git
color: "#2e7d32"
service:
type: NodePort
nodePort: 30090
EOF
git add .
git commit -m "podinfo-Werte"
git pushThe chart lives in the chart repo, the values in the fleet repo. The
Application therefore gets two sources. Instead of source,
the field is now called sources:
cd ~/argo-lab/tag05
cat > podinfo-app.yaml <<'EOF'
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: podinfo
namespace: argocd
spec:
project: default
sources:
- repoURL: https://stefanprodan.github.io/podinfo
chart: podinfo
targetRevision: 6.16.0
helm:
valueFiles:
- $fleet/values/podinfo.yaml
- repoURL: [email protected]:<du>/argocd-fleet.git
targetRevision: main
ref: fleet
destination:
server: https://kubernetes.default.svc
namespace: podinfo
syncPolicy:
automated:
prune: true
selfHeal: true
syncOptions:
- CreateNamespace=true
EOF
kubectl apply -f podinfo-app.yaml
argocd app wait podinfo --health --sync
argocd app get podinfo | sed -n "/^Sources/,/^SyncWindow/p"Expected (abridged):
application.argoproj.io/podinfo configured
…
Sources:
- Repo: https://stefanprodan.github.io/podinfo
Target: 6.16.0
Helm Values: $fleet/values/podinfo.yaml
- Repo: [email protected]:<du>/argocd-fleet.git
Target: main
Ref: fleet
SyncWindow: Sync Allowed
ref: fleetgives the second source a name. It does not deliver any manifests itself.$fleet/values/podinfo.yamlis the path within this source.
kubectl -n podinfo get deploy podinfo
curl -s localhost:30090 | grep -E '"message|"color'Expected:
NAME READY UP-TO-DATE AVAILABLE AGE
podinfo 2/2 2 2 45s
"color": "#2e7d32",
"message": "Werte aus Git",
From now on, a commit to values/podinfo.yaml changes the
cluster.
Save your progress? Sign up for free
Drill 5: Parameters on the Command Line
The CLI can set individual values directly in the Application:
argocd app set podinfo -p replicaCount=3Expected:
{"level":"fatal","msg":"Source position should be specified and must be greater than 0 for applications with multiple sources","time":"…"}
With multiple sources, you have to say which one you mean. Counting
starts at 1:
argocd app set podinfo --source-position 1 -p replicaCount=3
sleep 15
kubectl -n podinfo get deploy podinfo
kubectl -n argocd get app podinfo -o jsonpath='{.spec.sources[0].helm}'Expected:
NAME READY UP-TO-DATE AVAILABLE AGE
podinfo 2/3 3 2 78s
{"parameters":[{"name":"replicaCount","value":"3"}],"valueFiles":["$fleet/values/podinfo.yaml"]}
The value now lives in the Application in the cluster, not in Git and
not in your file podinfo-app.yaml. The next
kubectl apply of the file would silently remove it. For
experiments, -p is handy; for production, it is a trap. You
take it out again:
argocd app unset podinfo --source-position 1 -p replicaCount
sleep 15
kubectl -n podinfo get deploy podinfoExpected:
NAME READY UP-TO-DATE AVAILABLE AGE
podinfo 2/2 2 2 94s
Save your progress? Sign up for free
Checkpoint
argocd app get podinfo | grep -E "Sync Status|Health Status"Expected: Synced to 6.16.0 and Healthy.
curl -s localhost:30090 | grep '"message'Expected: "message": "Werte aus Git",.
argocd app history podinfoExpected: two blocks, one per source. The block for the fleet repo
names main with a commit.
Challenge
Upgrade podinfo to chart version 6.17.0.
Hint: The chart version is in the Application, not in the values.
Solution
cd ~/argo-lab/tag05
sed -i "s/targetRevision: 6.16.0/targetRevision: 6.17.0/" podinfo-app.yaml
kubectl apply -f podinfo-app.yaml
argocd app wait podinfo --health --sync
curl -s localhost:30090 | grep '"version'Expected (abridged):
application.argoproj.io/podinfo configured
…
"version": "6.17.0",
Because the Application is still a file on your VM, the update is not in any commit. From Day 7 on, the Applications live in the fleet repo too.
Save your progress? Sign up for free
Enterprise Note
- Always pin chart versions, never
*or a range. Otherwise a new chart changes the cluster without a commit. - Charts from OCI registries work the same way. The repo is then
registered with
--enable-oci. - A company usually mirrors third-party charts into its own registry, so that a deleted chart repo does not block deployments.