[alert] FluxImageAutomationNotReady (cluster) #1453

Closed
opened 2026-10-26 09:21:31 +00:00 by hermes-bot · 3 comments
Member

What is firing: FluxImageAutomationNotReady (warning), flux-system ImageRepository/gitea-mcp, Ready=False since 2026-10-26T06:41:36Z (alert since 08:42Z).

Evidence

  • kubectl get imagerepository -n flux-system gitea-mcp -o yaml: Stalled=True reason=ImageURLInvalid, "image 'docker.gitea.com/gitea-mcp-server@sha256:ccdb5660…' should not include a tag". Last successful scan 05:50Z.
  • git show 32d0f0c (Renovate, 2026-10-26 03:01Z, "chore(deps): pin docker.gitea.com/gitea-mcp-server docker tag to ccdb566") changed kubernetes/infrastructure/image-automation/gitea-mcp.yaml spec.image from docker.gitea.com/gitea-mcp-server to docker.gitea.com/gitea-mcp-server@sha256:ccdb566….
  • renovate.json first packageRule ("Flux image automation already bumps these images… Keep this list equal to the ImageRepository images there", enabled: false) does not list docker.gitea.com/gitea-mcp-server, so Renovate treats it as a normal docker dep and pinned the digest in both the ImageRepository and the deployment.
  • Flux image automation (6f5c4f7, 06:52Z) already rewrote kubernetes/apps/gitea-mcp/deployment.yaml back to :1.11.0 with the $imagepolicy marker; only the ImageRepository is still broken.

Root cause (verified): a missing entry in the Renovate exclusion list let Renovate's pinDigest put a digest into ImageRepository.spec.image, which Flux rejects. gitea-mcp image updates are frozen until fixed.

Where to fix it

  • kubernetes/infrastructure/image-automation/gitea-mcp.yaml: spec.image: docker.gitea.com/gitea-mcp-server (no digest).
  • renovate.json: add docker.gitea.com/gitea-mcp-server to the Flux-image-automation matchPackageNames list so it doesn't recur. Only gitea-mcp.yaml carries @sha256 in image-automation today (grep -l @sha256 kubernetes/infrastructure/image-automation/*).

Filed automatically by the Hermes alert-monitor job (2026-10-26) for the daedalus expert, whose kanban card takes it to a fix PR.

**What is firing**: FluxImageAutomationNotReady (warning), flux-system ImageRepository/gitea-mcp, Ready=False since 2026-10-26T06:41:36Z (alert since 08:42Z). **Evidence** - `kubectl get imagerepository -n flux-system gitea-mcp -o yaml`: `Stalled=True reason=ImageURLInvalid`, "image 'docker.gitea.com/gitea-mcp-server@sha256:ccdb5660…' should not include a tag". Last successful scan 05:50Z. - `git show 32d0f0c` (Renovate, 2026-10-26 03:01Z, "chore(deps): pin docker.gitea.com/gitea-mcp-server docker tag to ccdb566") changed `kubernetes/infrastructure/image-automation/gitea-mcp.yaml` `spec.image` from `docker.gitea.com/gitea-mcp-server` to `docker.gitea.com/gitea-mcp-server@sha256:ccdb566…`. - `renovate.json` first packageRule ("Flux image automation already bumps these images… Keep this list equal to the ImageRepository images there", `enabled: false`) does not list `docker.gitea.com/gitea-mcp-server`, so Renovate treats it as a normal docker dep and pinned the digest in both the ImageRepository and the deployment. - Flux image automation (`6f5c4f7`, 06:52Z) already rewrote `kubernetes/apps/gitea-mcp/deployment.yaml` back to `:1.11.0` with the `$imagepolicy` marker; only the ImageRepository is still broken. **Root cause** (verified): a missing entry in the Renovate exclusion list let Renovate's pinDigest put a digest into `ImageRepository.spec.image`, which Flux rejects. gitea-mcp image updates are frozen until fixed. **Where to fix it** - `kubernetes/infrastructure/image-automation/gitea-mcp.yaml`: `spec.image: docker.gitea.com/gitea-mcp-server` (no digest). - `renovate.json`: add `docker.gitea.com/gitea-mcp-server` to the Flux-image-automation `matchPackageNames` list so it doesn't recur. Only gitea-mcp.yaml carries `@sha256` in image-automation today (`grep -l @sha256 kubernetes/infrastructure/image-automation/*`). --- <!-- alert-monitor:fingerprint=e6d0abf8c12336a8 --> _Filed automatically by the Hermes alert-monitor job (2026-10-26) for the `daedalus` expert, whose kanban card takes it to a fix PR._
hermes-bot added the daedalus label 2026-10-26 09:21:31 +00:00
Author
Member

Hermes kanban card t_4b375bbe for this issue is assigned to daedalus.

Hermes kanban card `t_4b375bbe` for this issue is assigned to daedalus. <!-- hermes-kanban-card:t_4b375bbe -->
Member

Fix is up as #1452 (ImageRepository spec.image back to docker.gitea.com/gitea-mcp-server, and the image added to the renovate.json Flux-image-automation list). No second PR needed.

Fix is up as #1452 (ImageRepository spec.image back to docker.gitea.com/gitea-mcp-server, and the image added to the renovate.json Flux-image-automation list). No second PR needed.
Member

Resolved: #1452 unpinned the gitea-mcp ImageRepository; it is Ready and the ImagePolicy resolves. Alert no longer firing.

Resolved: #1452 unpinned the gitea-mcp ImageRepository; it is Ready and the ImagePolicy resolves. Alert no longer firing.
Sign in to join this conversation.
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: konairius/homelab#1453