-
Notifications
You must be signed in to change notification settings - Fork 263
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ArgoCD fails to Sync image update for Helm, succeeds for Kustomize #833
Comments
I have a total of 3 test cases now, and debug logs. Why is beep-int-helm-staging failing to be upgraded by ArgoCD even after AIU has updated its gitops directory with the .argocd-* file?
The new test is a simple hello-go webapp deployment using Helm. ArgoCD server successfully syncs the image tag update that AIU uploads to its gitops directory. beep-int-kust-staging == SUCCESS
beep-int-helm-staging == FAIL
hello-go-helm-staging == SUCCESS
|
Have you tried using Also you may want to try v0.14.0, which contains some bug fixes compared to your version v0.13.1 |
@chengfang thanks for the suggestion. I will try to return to this work to try out your suggestion. I'll report back my result when I do. |
Describe the bug
My test case app is in 2 different layouts. One is Kustomize, one is Helm. Ultimately we want to go with Helm. They both deploy successfully by ArgoCD. ArgoCD Image Updater (AIU) detects updated image for both and it successfully adds the .argocd-source* file to gitops. After AIU updates gitops, ArgoCD polls gitops: The test app running as Kustomize is successfully updated, the Helm test app is not. It's as if ArgoCD doesn't see the update.
I figure I'm doing something wrong, rather than this being a bug. Help greatly appreciated!
Application beep-int-helm
Application beep-int-kust
Failing case:
Here's what happens for the failing case, my test app using Helm.
Succeeding case:
Here's what happens for the working case, my test app using Kustomize
Version
Logs
In-line above.
The text was updated successfully, but these errors were encountered: