Replies: 1 comment
-
|
You are mixing Git tags for Helm charts stored in Git with Helm charts themselves. There is no need for such complexity. Either
OR
Basically choose if you are going to store your Helm charts in Git and treat them as Git files, or store them in a Helm repository and treat them as Helm artifacts. Now you are trying to do both at the same time. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello.
I'm using ArgoCD ApplicationSet to generate multiple applications that are using single helm chart and the only thing that is changing between each app are the values.
The helm chart is being versioned in parallel to the entire application, so I'm using the following configuration to stick to specific helm version, with the ability to overwrite it for specific app:
The problem I'm facing now is the order of actions that are happening in ArgoCD when I'm releasing a new app version. If the upgrade doesn't require helm chart update, everything works great, but when I need to update the helm chart version the same time I'm updating the application, ArgoCD tend to synchronize the applications before ApplicationSet will apply the changes on
targetRevision.I'm not using the AutoSync to synchronize my applications, but I'm doing the sync using ArgoCD CLI in Github Actions, so I thought about adding some step that would verify if ApplicationSet controller has already refreshed all the applications. The problem is that I can't find any indicator that would tell me that ApplicationSet controller has updated all the Applications.
Did anyone face the same issue and found some solutions for this?
Beta Was this translation helpful? Give feedback.
All reactions