From 59cc813a877b23bf459ef4c8c81f5cb751c7c410 Mon Sep 17 00:00:00 2001 From: Claude Bot Date: Sat, 7 Nov 2026 22:07:33 +0100 Subject: [PATCH] fix(image-automation): scan the Immich repositories every 6h immich-machine-learning has ~222k tags and immich-server ~33k, nearly all PR builds. Each anonymous scan pages the full list (about 220 requests of 1000 tags for ML) and hourly scans hit ghcr.io's TOOMANYREQUESTS. Immich releases a few times a week at most, so 6h costs nothing. S28-40 Co-Authored-By: Claude Opus 5.5 --- kubernetes/infrastructure/image-automation/immich.yaml | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/kubernetes/infrastructure/image-automation/immich.yaml b/kubernetes/infrastructure/image-automation/immich.yaml index 901824be..79ea99c4 100644 --- a/kubernetes/infrastructure/image-automation/immich.yaml +++ b/kubernetes/infrastructure/image-automation/immich.yaml @@ -1,11 +1,14 @@ apiVersion: image.toolkit.fluxcd.io/v1 kind: ImageRepository +# 6h, not 1h: both repositories carry tens to hundreds of thousands of PR +# build tags, and every scan pages the full list anonymously, which runs +# into ghcr.io's rate limit. metadata: name: immich-server namespace: flux-system spec: image: ghcr.io/immich-app/immich-server - interval: 1h + interval: 6h --- # v-prefix tags only, semver 3.x. The 4.x cutover would need manual # review — Immich major bumps historically require migration. @@ -31,7 +34,7 @@ metadata: namespace: flux-system spec: image: ghcr.io/immich-app/immich-machine-learning - interval: 1h + interval: 6h --- # Same policy as immich-server; machine-learning image must stay in # version-sync with the server image (Immich docs require it). -- 2.54.0