From 90a703c4f5469adfcdcd96028915e0ce2af4b6b1 Mon Sep 17 00:00:00 2001 From: "Claude (via ashwin)" Date: Fri, 17 Jul 2026 02:10:58 +0530 Subject: [PATCH] fix(gitops): stop tracking ai-assistant via Flux ImagePolicy, pin explicit digest The ImagePolicy for this image uses alphabetical ordering, which always resolved to the literal tag "latest" (it sorts after any hex SHA) rather than tracking the newest build - Flux's ImageUpdateAutomation was reverting this file to :latest every 2 minutes, racing with and clobbering the specific-digest commits our own CI already writes correctly (the same pattern nxtgauge-backend-rust's 20 services already use, none of which rely on Flux's automatic image tracking either). Remove the $imagepolicy marker so CI's explicit write is the sole source of truth, and pin to the currently-running, verified-good digest. --- apps/nxtgauge-ai-assistant/overlays/prod/release-patch.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/apps/nxtgauge-ai-assistant/overlays/prod/release-patch.yaml b/apps/nxtgauge-ai-assistant/overlays/prod/release-patch.yaml index a94ffc9..d15aaa9 100644 --- a/apps/nxtgauge-ai-assistant/overlays/prod/release-patch.yaml +++ b/apps/nxtgauge-ai-assistant/overlays/prod/release-patch.yaml @@ -8,4 +8,4 @@ spec: spec: containers: - name: ai-assistant - image: ci.nxtgauge.com/ashwin/nxtgauge-ai-assistant:latest # {"$imagepolicy": "flux-system:nxtgauge-ai-assistant"} + image: ci.nxtgauge.com/ashwin/nxtgauge-ai-assistant@sha256:2b80024004c3ae78e04a11ec2448ad847991ed0cfb675962e7397b82fb4a9ed2