fix(gitops): stop tracking ai-assistant via Flux ImagePolicy, pin explicit digest
Some checks failed
sync-to-forgejo / sync (push) Failing after 7m18s
Some checks failed
sync-to-forgejo / sync (push) Failing after 7m18s
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.
This commit is contained in:
parent
ce81802ad2
commit
90a703c4f5
1 changed files with 1 additions and 1 deletions
|
|
@ -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
|
||||
|
|
|
|||
Loading…
Add table
Reference in a new issue