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
/ $ argocd-image-updater test gouthamappsmith/tests-argocd:release --update-strategy latest
DEBU[0000] Creating in-cluster Kubernetes client
INFO[0000] retrieving information about image image_alias= image_digest= image_name=gouthamappsmith/tests-argocd image_tag=release registry_url=
INFO[0000] Fetching available tags and metadata from registry application=test image_alias= image_digest= image_name=gouthamappsmith/tests-argocd image_tag=release registry_url=
FATA[0001] could not get tags: errors:
denied: requested access to the resource is denied
unauthorized: authentication required application=test image_alias= image_digest= image_name=gouthamappsmith/tests-argocd image_tag=release registry_url=
and it is working in the same cluster as imagePullSecrets. Also, occasionally i see Too many pull Requests despite providing my credentials and authenticating myself
Am i missing anything? anyhelp would be off great use Thankyou
Just wanted to add some traffic to this, we have a similar situation.
We use Azure Container Registry, and when I tried to configure a registry-wide pull secret, it wouldn't auth (but I could curl the same /tag/list endpoint with the same creds).
When I set each image in the image list to use the same pull secret individually, it works.
So I think there's a disconnect somewhere between the registry-wide config (which uses https://????.azurecr.io for it's api url), and the image list which omits the https when defining images.
I'm guessing when it goes to compare to decide if it needs to use that specific registry, it doesn't consider it a match? Just a stab in the dark.
Describe the bug
My registries configmap look as follows
Same creds work when i do a docker login
I created the secret as follows
kubectl create -n argocd secret docker-registry appsmith --docker-username=xxxx --docker-password=xxx
and it is working in the same cluster as imagePullSecrets. Also, occasionally i see Too many pull Requests despite providing my credentials and authenticating myself
Am i missing anything? anyhelp would be off great use Thankyou
Version
The text was updated successfully, but these errors were encountered: