Using Helm Values Files with Argo CD

In this video, we explain how to supply custom values files to a Helm chart sourced from a Helm chart repository in an Argo CD application.
- 0:00 Intro
- 2:03 The Problem
- 2:50 Solution 1 - Helm Umbrella Chart
- 7:53 Solution 2 - Helm Values in the Application
- 12:13 Solution 3 - Multiple Sources for Applications
- 16:34 Closing thoughts

[@hcompres1]

Can you do that same scenario with aplicatioset?

[@facundoruetaloyanes7320]

Nice video, it worked for me, thanks. The only problem that I'm having is that I don't know how to call a secret value (secret externally created with external-secrets in the same namespace) in my new values.yaml from my subchart, do I need to create a template folder and a configmap file or something like that?

[@samanabdollahpour1429]

thanks a lot man worked like a charm

[@manikantaseetha-my5yf]

Thanks for the video it’s cut and clear I have one small doubt we are implementing umbrella chart way and we have a problem with whenever we use snapshot versions we usually push it with same name and argocd is not able to pull changes even with hard refresh it’s sometimes too hard Do you think multiple sources should work in this case ?

[@jemag]

You can also follow a specific git tag with applications using the umbrella chart, to prevent affecting all environments at once

[@scottamolinari]

Sure, but wouldn't that be an obscure piece of information to know what revision is being used?

[@spiraldynamics6008]

☂️

[@scottamolinari]

Has the UI gotten the update yet? I'd like to try that last solution. I guess I could just try it out.

[@100yasser100]

I have 2 dependencies in chart umbrella and I provided 2 different values both has different top level key one of the first dependency and second key for the second dependency. Yet, it seems values are being passed correctly to the sub charts and still not sure why

[@nikolayandcards]

good stuff

[@soumitasardar2616]

Hi... Can you please also show like how the private helm chart repo will get connected with argocd by keeping the helm repo creds in aws ssm manager

[@100yasser100]

Use @repo_name , make sure to use name same as what's configured in argoCD. If repo doesn't have a name, you need to name it to use the credentials correctly without having it in umbrella chart

[@suhanimatki]

I am trying the first option and i get unauthroized error when i add dependencies on a repo in artifactory that i have added as a Repo in argocd already. what am i doing wrong ? how can i resolve 401 unauthoized here.

[@rafayhussain3485]

You need to login to the artifactory repo before you pull from it. That will resolve 4011 error

[@itskagiso]

Great tutorial however did not work for me. The 3rd method gives an error: error validating and normalizing app: error getting application's project: application 'app-x' in namespace 'default' is not allowed to use project 'default'

[@morey-tech-akuity]

The error you are getting points to an issue with the `default` AppProject configuration not permitting the Application. Check to make sure you AppProject isn't restricting the Application by name or namespace. I confirmed that it works on a fresh install of Argo CD v2.8