Open bcbrockway opened 11 months ago
Setting --max-concurrency
to 1 works for me, although I don't know exactly how this fixes the problem 😅
https://argocd-image-updater.readthedocs.io/en/stable/install/reference/#flags
extraArgs:
- --max-concurrency
- "1"
Setting
--max-concurrency
to 1 works for me, although I don't know exactly how this fixes the problem 😅 https://argocd-image-updater.readthedocs.io/en/stable/install/reference/#flagsextraArgs: - --max-concurrency - "1"
Some of our ArgoCD instances have a lot of apps so this would slow us down quite a bit :(
This still seems to happen even with --max-concurrency
set to 1. Is this still happening to anyone else? Where is the 10s timeout being set and can it be extended?
It's not related to caching invalid token data or something for the lifetime of credsexpire
if one call fails or something, is it?
Same here; it connects at the start, then fails when it requires a refresh. Any solution?
We just made a new image updater for ECR by ourselves from scratch...
Describe the bug
We have the Image Updater running on EKS clusters using IRSA to link them to an IAM role that grants it permissions to our ECR registry. In addition, we have an auth script configured to run an awscli command to grab a new token every 11 hours:
This usually works on startup, and sometimes after
credsexpire
, but it also often fails with:Sometimes this can take hours of retries to rectify and sometimes nothing short of killing the pod and starting a new one will fix it.
It's also weird that it seems to run this script once for each app in its update cycle (see logs below) rather than just running it once seeing as we've configured at the registry level.
To Reproduce Set up as above. Unfortunately, this is intermittent.
Expected behavior The script runs correctly (once) and stores the new token for all apps to use.
Additional context N/A
Version 0.12.0
Logs