fix(argocd): restore fleet image rollouts — image-updater v1 needs an ImageUpdater CR
The un-pinned HelmChart pulled argocd-image-updater v1.2.2, whose CRD-based
controller no longer reads Application annotations by itself ("No ImageUpdater
CRs to process") — image rollouts silently froze for every annotated app
(kadans stuck on its 07-18 digest, same for webapp/cms/dance-lessons-coach/
prospection/telegram-gateway). One useAnnotations CR selecting "*" restores
the annotation-driven behaviour; values.yaml stays the single source of truth.
Co-Authored-By: Claude Fable 5 <[email protected]>
Claude-Session: https://claude.ai/code/session_013ws8L74dVZmp97Wu36fm8j
This commit is contained in:
@@ -0,0 +1,22 @@
|
||||
{{- /*
|
||||
argocd-image-updater v1+ ships a CRD-based controller: it no longer scans
|
||||
Application annotations on its own and idles with "No ImageUpdater CRs to
|
||||
process" — which silently froze image rollouts for the WHOLE fleet (kadans,
|
||||
webapp, cms, dance-lessons-coach, prospection, telegram-gateway) after the
|
||||
un-pinned HelmChart pulled the new major.
|
||||
|
||||
This single CR restores the previous behaviour: select every Application in
|
||||
the argocd namespace and read the existing
|
||||
`argocd-image-updater.argoproj.io/*` annotations (useAnnotations mode). Apps
|
||||
without annotations are simply ignored — no per-app CR to maintain, the
|
||||
annotations in values.yaml stay the one source of truth.
|
||||
*/ -}}
|
||||
apiVersion: argocd-image-updater.argoproj.io/v1alpha1
|
||||
kind: ImageUpdater
|
||||
metadata:
|
||||
name: annotated-applications
|
||||
namespace: argocd
|
||||
spec:
|
||||
applicationRefs:
|
||||
- namePattern: "*"
|
||||
useAnnotations: true
|
||||
Reference in New Issue
Block a user