All 29 Applications questions
More in Applications
How does ArgoCD track which resources belong to an Application? What is a Project (AppProject) in ArgoCD? How do you handle resources that ArgoCD should create but not manage/delete? How do you set an Application to auto-create its target namespace? How do you temporarily pause management of an Application? How do you view an Application's sync history and roll back to a prior revision? What are ApplicationSets and what problem do they solve? What ApplicationSet generators exist and when do you use each? How do you create ephemeral preview environments with ArgoCD? How do you manage many environments (dev/staging/prod) for one app?
Advertisement
Back to results for “GitOps Principles”
ArgoCD › Applications

How do Application parameters differ between Helm and Kustomize sources?

Intermediate

Answer

For Helm you override via helm.parameters, helm.values, or helm.valueFiles. For Kustomize you use kustomize.images, namePrefix/nameSuffix, and commonLabels/commonAnnotations. Each maps to that tool's native override mechanism, applied when ArgoCD renders the manifests.
kustomize:
  images: [ myapp=repo/myapp:v3 ]
helm:
  parameters: [ { name: image.tag, value: v3 } ]
Real-world example The Helm app overrides image.tag while the Kustomize app overrides the image via kustomize.images.

Common follow-ups: Which section overrides Helm values? | How does Kustomize override images?

GitOps Principles Sync & Health Applications
All 29 Applications questions