Nxtgauge GitOps Configuration
Find a file
sync-test d52b911aba
All checks were successful
sync-to-forgejo / sync (push) Successful in 16s
chore(ai-guard): scale to 0 — Phase 0 stabilization per AI architecture doc
ai-guard has been in ImagePullBackOff for 14+ days: no Dockerfile exists
in its source repo so no image was ever successfully built by CI, it
has no Kubernetes Service (unreachable even if the pod were healthy),
and its own dependencies (llm-guard, presidio) were never deployed.
Nothing currently routes through it anyway — both AI consumers call
LiteLLM directly. Scaling to 0 stops the wasted pull-retry churn until
it's properly rebuilt (Phase 3 of the target architecture).
2026-07-21 06:20:44 +05:30
.github/workflows fix(ci): make sync-to-forgejo tolerate Forgejo-only commits 2026-07-13 22:01:41 +05:30
apps chore(ai-guard): scale to 0 — Phase 0 stabilization per AI architecture doc 2026-07-21 06:20:44 +05:30
clusters/production fix(flux): simplify ImageUpdateAutomation commit messages 2026-07-05 22:40:48 +00:00
docs feat(ai): add AI plans docs, LiteLLM manifests, and infrastructure updates 2026-06-15 06:15:41 +05:30
ops chore: remove forgejo and registry dependencies 2026-06-15 01:52:43 +05:30
scripts fix(ci): add ai-assistant to deployment scripts 2026-07-06 03:49:11 +05:30
.ci-trigger ci: trigger build 2026-07-07 21:52:58 +00:00
.sops.yaml Encrypt all secrets with SOPS, add Flux decryption support, rotate JWT_SECRET/AI_SERVICE_KEY 2026-07-02 17:56:28 +05:30
.test_push test push 2026-06-08 18:13:19 +05:30
OTP_ISSUE_FIX_PROMPT.md chore: remove argocd and standardize on flux 2026-06-11 17:17:42 +05:30
ROUTE_ISSUE_ANALYSIS.md chore: remove argocd and standardize on flux 2026-06-11 17:17:42 +05:30