argocd-image-updater icon indicating copy to clipboard operation
argocd-image-updater copied to clipboard

How to reduce interval of checking for new image from the registry

Open st3fus opened this issue 1 year ago • 7 comments

Hey there, so I got everything working for several weeks now, and accidentally I noticed this on my docker hub for both repos I'm using:

image

How do I reduce the interval it checks/pulls latest image? I did set limit: 5 in repo config but I think it's still checking it too many times. I do have a paid dockerhub license so I can pull 5000times per day without hitting a limit, but still.

st3fus avatar Aug 08 '23 11:08 st3fus

This can be set in the extra args in the helm chart values: CleanShot 2023-08-08 at 13 46 06

What I think you've configured is the rate at which it tries to fetch the actual data from source registry.

jwhy89 avatar Aug 09 '23 14:08 jwhy89

@st3fus see above

jwhy89 avatar Aug 09 '23 14:08 jwhy89

This can be set in the extra args in the helm chart values: CleanShot 2023-08-08 at 13 46 06

What I think you've configured is the rate at which it tries to fetch the actual data from source registry.

Which helm chart exactly? The ones from the backend and front or the main chart?

st3fus avatar Aug 09 '23 14:08 st3fus

This can be set in the extra args in the helm chart values: CleanShot 2023-08-08 at 13 46 06 What I think you've configured is the rate at which it tries to fetch the actual data from source registry.

Which helm chart exactly? The ones from the backend and front or the main chart?

The main chart in the values.yaml file.

jwhy89 avatar Aug 09 '23 17:08 jwhy89

Seems like I installed it with default helm values, can I download the default values.yaml and have only the extraArgs in it? I'm guessing when I do kubectl -f apply on that it will only modify the extraArgs since I only have that inside values.yaml?

st3fus avatar Aug 16 '23 14:08 st3fus

Seems like I installed it with default helm values, can I download the default values.yaml and have only the extraArgs in it? I'm guessing when I do kubectl -f apply on that it will only modify the extraArgs since I only have that inside values.yaml?

Yep, that or pass in flags like https://github.com/helm/charts/issues/2112#issuecomment-370650234. It just depends on how you're managing the helm chart, e.g. helm cli, kubectl, or argocd... etc

helm install \
  --name cluster-autoscaler \
  --set autoscalingGroups[0].name=worker.${K8S_NAME} \
  --set autoscalingGroups[0].maxSize=6 \
  --set autoscalingGroups[0].minSize=1 \
  --set awsRegion=us-east-1 \
  --set extraArgs.v=4 \
  --set extraArgs.stderrthreshold=info \
  --set extraArgs.expander=least-waste \
  --set image.tag=v1.1.1 \
  stable/cluster-autoscaler

jwhy89 avatar Aug 17 '23 18:08 jwhy89

@jwhy89 I just got back to this issue, was busy with other projects... I've set it up all on my previous PC, now that I switched to a new one I can't recall how I installed it... I think I used helm, but helm list doesn't output anything on this PC. I got kubectl and argoCD, I just want to modify that extraArgs so I can increase the interval of checks.

I'm not exactly sure how should I apply that setting without messing up my current deployment.

st3fus avatar Oct 16 '23 16:10 st3fus