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
Whenever argocd-image-updater tries to update the version, it reports the following error:
time="2024-03-04T19:14:14Z" level=error msg="Could not update application spec: could not get creds for repo '': credentials for '' are not configured in Argo CD settings" application=ledswitcher
Additional context
Similar setups exist in my cluster for deployments. Those work without any problem. The only difference that I found is that in this case, it's trying to update a daemonset, rather than a deployment.
Version
quay.io/argoprojlabs/argocd-image-updater:v0.12.2
Logs
time="2024-03-04T19:14:14Z" level=info msg="Setting new image to ghcr.io/clambin/ledswitcher:sha-092c297-2024030415280045" alias=ledswitcher application=ledswitcher image_name=clambin/ledswitcher image_tag=sha-ad4c2e3-2024030411003510 registry=ghcr.io
time="2024-03-04T19:14:14Z" level=info msg="Successfully updated image 'ghcr.io/clambin/ledswitcher:sha-ad4c2e3-2024030411003510' to 'ghcr.io/clambin/ledswitcher:sha-092c297-2024030415280045', but pending spec update (dry run=false)" alias=ledswitcher application=ledswitcher image_name=clambin/ledswitcher image_tag=sha-ad4c2e3-2024030411003510 registry=ghcr.io
time="2024-03-04T19:14:14Z" level=info msg="Committing 1 parameter update(s) for application ledswitcher" application=ledswitcher
time="2024-03-04T19:14:14Z" level=info msg="Starting configmap/secret informers"
time="2024-03-04T19:14:14Z" level=info msg="Configmap/secret informer synced"
time="2024-03-04T19:14:14Z" level=error msg="Could not update application spec: could not get creds for repo '': credentials for '' are not configured in Argo CD settings" application=ledswitcher
time="2024-03-04T19:14:14Z" level=info msg="secrets informer cancelled"
time="2024-03-04T19:14:14Z" level=info msg="configmap informer cancelled"
The text was updated successfully, but these errors were encountered:
I accidentally found that this can also happen for a Deployment. The root cause seems to be related to using multiple sources in your application:
Does not work (even if there's only one source):
sources:
- path: argocd/conf/infra/ledswitcher/resources
repoURL: https://github.com/clambin/gitops
targetRevision: HEAD
Works:
source:
path: argocd/conf/infra/ledswitcher/resources
repoURL: https://github.com/clambin/gitops
targetRevision: HEAD
In the first confirmation, image updates are broken with the error in the first comment. If we change it to the 2nd version (one source, rather than multiple), then image upgrades works fine.
clambin
changed the title
Could not update application spec: could not get creds for repo '': credentials for '' are not configured in Argo CD settings (daemonset?)
Could not update application spec: could not get creds for repo '': credentials for '' are not configured in Argo CD settings
Mar 6, 2024
Describe the bug
I have an Application in ArgoCD with the following configuration:
This leads to a DaemonSet in argocd/conf/infra/ledswitcher/resources:
and the image tag is set in a kustomization.yaml:
Whenever argocd-image-updater tries to update the version, it reports the following error:
Additional context
Similar setups exist in my cluster for deployments. Those work without any problem. The only difference that I found is that in this case, it's trying to update a daemonset, rather than a deployment.
Version
quay.io/argoprojlabs/argocd-image-updater:v0.12.2
Logs
The text was updated successfully, but these errors were encountered: