Skip to content
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

Argo CD Image Updater Not Retaining Full Registry Path in kustomization.yaml Updates #674

Open
assafsauer opened this issue Jan 30, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@assafsauer
Copy link

Describe the bug

Hello,

I'm encountering an issue with the Argo CD Image Updater where it's not updating my kustomization.yaml file as expected. Specifically, the updater seems to omit the full registry host from the image path, despite my annotations specifying it.

For example, my annotation is set as follows:
argocd-image-updater.argoproj.io/image-list: nodejs=index.docker.io/project/nodejs

However, the resulting update in kustomization.yaml consistently appears like this:

yaml
Copy code
images:

name: project/nodejs
newTag: 0.0.212
As you can see, the full registry path (index.docker.io/) is missing. This is causing issues as my kustomization.yaml requires the complete image path including the registry host.

Is there a way to configure the Image Updater to include the full registry path in the kustomization.yaml? Any guidance or suggestions on how to resolve this would be greatly appreciated.

To Reproduce
create annotations
argocd-image-updater.argoproj.io/image-list: nodejs=index.docker.io/proeject/nodejs

validate kustomization.yaml nam

Expected behavior
get full path of the registry host in the kustomization.yaml

Additional context
Add any other context about the problem here.

Version
0.9.3

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant