You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Image updater successfully push new image tag with digest to image_updater_branch .argocd-source-staging-my-app.yaml file, but ArgoCD doesn't update deployment with the new tag from .argocd-source-staging-my-app.yaml file.
Without argocd-image-updater.argoproj.io/git-branch: :image_updater_branch annotation all works correctly, but I want to keep main branch protected and use image_updater_branch for image changes.
Expected behavior
Image updater push new tag to image_updater_branch .argocd-source-staging-my-app.yaml file, argo update deployment's image after sync.
Version
Image updater 0.15.1, ArgoCD 2.13.0 Logs
No any errors in logs.
The text was updated successfully, but these errors were encountered:
Since the app sources from targetRevision: main, it will not sync up with other branches like the custom write-back-target branch. If you want to keep parameter updates in a separate place, you may want to consider multi-source app, with the 2nd source as a repo keeping helm values file.
Describe the bug
When I try to specify a target branch to commit for image updater argoCD doesn't catch image from the branch.
I have:
Image updater successfully push new image tag with digest to image_updater_branch .argocd-source-staging-my-app.yaml file, but ArgoCD doesn't update deployment with the new tag from .argocd-source-staging-my-app.yaml file.
Without argocd-image-updater.argoproj.io/git-branch: :image_updater_branch annotation all works correctly, but I want to keep main branch protected and use image_updater_branch for image changes.
Expected behavior
Image updater push new tag to image_updater_branch .argocd-source-staging-my-app.yaml file, argo update deployment's image after sync.
Version
Image updater 0.15.1, ArgoCD 2.13.0
Logs
No any errors in logs.
The text was updated successfully, but these errors were encountered: