Using a Private OCI Helm Chart Repo with Argo CD

This video illustrates using a private OCI Helm Chart repository with Argo CD.
Free course on CD and GitOps using Argo CD: academy.akuity.io/courses/git...
Start a free trial of the Akuity Platform, a hosted Argo CD offering with innovation beyond the open-source offering: akuity.io/signup/
For more knowledge about Argo and GitOps, check out the Akuity Blog: akuity.io/blog/ and the Awesome Argo list on GitHub github.com/akuity/awesome-argo
0:00 Intro
0:18 Overview of Setup
0:56 Adding using the UI
1:34 Adding using the CLI
2:03 Adding using Kubernetes Secret
2:40 Demonstration
4:08 Outro

[@RuslanGonzalez]

Was the secret file populated with values that were not encrypted using base64?

[@maiwaly7061]

When we tried that approach it didnt work with dependency chart, please advise, it only works if the main app point to the helm repo but in our case the app point to chart in a git repo that uses a private oci dependency chart, we see 401 err

[@user-ws5ky1md4w]

is it possible to have as a cred template ?

[@krystianh4732]

Thank you for the intro. How to handle chart from private helm repo with custom values.yaml file? Can Argo CD be synced with private repo for new chart version?

[@morey-tech-akuity]

This is a great question and certainly something I need to make video on. Becuase the custom values.yaml files don't get packaged with the chart in Helm repos, there are two options for using a Helm chart from a private repo and a custom values.yaml file with Argo CD. 1. Create an Umbrella chart in the Git repo with the values.yaml files, where the chart from the private Helm repo is a dependency of the Umbrella chart and the values reference that dependency [1]. 2. Use the beta multiple sources feature to reference the private helm chart and the Git repo with the values.yaml file. [2] In either case, make sure to add repo credentials for that private repo to Argo CD. Regards to syncing, in scenario 1, the Application will sync when the chart dependency version is updated in the Umbrella chart. In scenario 2, it should sync when either the Helm chart changes in the Helm repo or the values change. [1] - github.com/argoproj/argo-cd/issues/2789#issuecomment-892406021 [2] - argo-cd.readthedocs.io/en/stable/user-guide/multiple_sources/#helm-value-files-from-external-git-repository

[@krystianh4732]

@@morey-tech-akuity Just awesome! Thanks for quick reply.

[@krystianh4732]

I've also found about another approach - helm values in argo application yaml, as parameters or block of yaml values. That doesn't seem clean to me though. I even tried to add helm parameters for values of type array and map, but looks like those are not supported in argo app yaml.

[@morey-tech-akuity]

​@@krystianh4732 Oh yes! I forgot to mention that you can add the values directly in the Application manifest. Yeah, I've run into issues with arrays and maps with the Helm parameters too. It seems like you have to reference each index when using parameters. For example: # Array - name: key[0] value: foo - name: key[1] value: bar # Map - name: key.foo value: bar - name: key.bar value: foo

[@AlexisNDelgado]

The best approach for this it would be create your own plugin that is able to connect to that chart repository

[@jamallmahmoudi9481]

Hi, cool & perfect 🙏👌👌👌