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
Only second image in list is getting updated #675
Comments
Does anybody have a workaround for this? |
I have some more details on this. First, the Application resource is not getting updated. Also, I turned on trace for the logs. Slightly modified to remove private information. In this log, I updated two images in the registry. This is the first run after doing that.
This is what the manifest looks like. Even though I updated both, only one is showing up:
Also, here is the kustomization file:
|
After messing with this for hours and hours, I was finally found a workaround (unless I'm wrong about why it was not working). I believe the trick was using kustomization name to reference a tag in Deployment (not the registry) and using newName in kustomization.yaml to replace the image name in the Deployment. kustomization.yam
deployment1.yaml
deployment2.yaml
argocd-application.yaml
|
Describe the bug
When using argocd image updater with two images, only the second is updated. The first image remains at the initially defined tag version.
It looks like it has something to do with this info message:
To Reproduce
I've also tried several variations of this including:
Images in the registry:
sms: v1.0.1 through v1.0.2
email: v1.0.1 through v1.0.9
In this example, the version deployed with sms updates to the most recent image properly, but the email image remains at the originally deployed version (ie sms=1.0.2 and email=1.0.8). When I swap sms and email in the
image-list
, the results are reversed (sms=1.0.1 and email=1.0.9).Steps to reproduce the behavior:
Expected behavior
A clear and concise description of what you expected to happen.
Additional context
I did manually alter the logs and annotations to remove a customer name from the path and to not expose the name of our internal registry server.
Version
Using v0.12.2
Logs
Please paste any relevant logs here
The text was updated successfully, but these errors were encountered: