Project not found.
ArgoCD Image Updater
What It Does
Polls Harbor for new image tags matching a regex pattern. When a new image is found, writes a
.argocd-source-{app-name}.yaml file back to the Forgejo repo via git commit.Configuration
- Strategy:
newest-build— picks the most recently built image - Regex: SHA-based tags (
^[0-9a-f]{7,40}$) - Auth: Forgejo token stored as k8s secret
argocd/git-credsfor git write-back - Write-back method: git commit to the branch specified by
target_revision(defaults tomain, but follows whatever branch each service is configured to track)
Troubleshooting
- Check Image Updater logs:
kubectl logs -n argocd -l app.kubernetes.io/name=argocd-image-updater - Ensure Forgejo auth token in
git-credssecret is valid and has write access - Verify image tag format matches the configured regex
- The
.argocd-source-*file should be excluded from CI triggers to prevent infinite loops
Procedures
sop-deploy-recovery— recovery procedure when ArgoCD image updater or deployment pipeline breaks