Commit graph

10 commits

Author SHA1 Message Date
sync-test
d503a32de7 feat(ai): fix Ollama resource limits and bring LiteLLM under GitOps management
All checks were successful
sync-to-forgejo / sync (push) Successful in 10s
Phase 1 of the AI architecture doc ("Improve Generation Quality") —
qwen3:4b and qwen3:8b were already pulled onto the Ollama PVC, and
apps/litellm/base/configmap.yaml already had the correct model_list
mapping every feature alias to them instead of gemma3:270m. Neither
was actually in effect:

1. apps/litellm was never included in
   clusters/production/kustomization.yaml, so it was only ever
   deployed by a one-off manual `kubectl apply` and has been
   completely outside GitOps ever since (same root cause as the
   ai-guard registry drift found earlier). Added it to the root
   kustomization. Corrected its image reference from
   registry.nxtgauge.com/litellm:latest (doesn't appear to exist) to
   ghcr.io/berriai/litellm:latest, matching what's actually running
   live — adopting this file without that fix would have broken a
   working deployment the moment Flux started managing it.

2. apps/ollama/base/deployment.yaml's memory limit (1500Mi) was too
   small to ever load qwen3:4b (~2.5GB) or qwen3:8b (~5.2GB) — every
   model alias in the (also-never-applied) LiteLLM config was
   therefore unusable regardless of what it was named. Raised to
   4 CPU / 8Gi limit (node has 16GB total, was at ~26% memory use) and
   added OLLAMA_KEEP_ALIVE=30m so a loaded model survives the gaps
   between bursty feature requests instead of reloading from disk on
   every first call after 5+ minutes idle.
2026-07-21 06:30:13 +05:30
sync-test
f0906d2c67 Add Traceworks Flux image automation
All checks were successful
sync-to-forgejo / sync (push) Successful in 18s
2026-07-05 23:04:54 +05:30
Ashwin Kumar Sivakumar
b4f371d415 Encrypt all secrets with SOPS, add Flux decryption support, rotate JWT_SECRET/AI_SERVICE_KEY
- Add .sops.yaml (age) and encrypt every plaintext Secret manifest in apps/
- Commit the Flux GitRepository/Kustomization (previously only applied manually)
  with a decryption stanza referencing the sops-age key (created out-of-band,
  not committed)
- Rotate JWT_SECRET (previously exposed in plaintext) and set a real
  AI_SERVICE_KEY (was an empty placeholder), shared between
  nxtgauge-backend-rust and nxtgauge-ai-assistant
- Wire JWT_SECRET into the ai-assistant deployment (was missing entirely,
  causing every authenticated request to fail)
- Redact the leaked LiteLLM production master key from README/OPENCODE_CONNECT
  docs; move the litellm prod overlay off a plaintext secretGenerator onto an
  encrypted patch
2026-07-02 17:56:28 +05:30
Ashwin Kumar Sivakumar
c0abc5e152 feat(ci): add github self-hosted runners 2026-06-16 00:47:15 +05:30
Ashwin Kumar Sivakumar
fce1da5b3f chore: remove forgejo and registry dependencies 2026-06-15 01:52:43 +05:30
Ashwin Kumar Sivakumar
f5d1041f14 fix: add openobserve-alerts to cluster kustomization and disable Telegram alerts 2026-06-12 04:26:32 +05:30
Ashwin Kumar Sivakumar
c4a7e1e330 chore: remove argocd and standardize on flux 2026-06-11 17:17:42 +05:30
Ashwin Kumar Sivakumar
bd389ac480 fix(flux): correct relative paths to apps/ in cluster kustomization 2026-06-08 20:57:15 +05:30
Ashwin Kumar Sivakumar
216a363c66 fix(flux): point cluster kustomization at each app's overlays/prod 2026-06-08 20:56:36 +05:30
Ashwin Kumar Sivakumar
6674264bad chore(flux): add cluster/production kustomization pointing at apps 2026-06-08 20:13:43 +05:30