d52b911aba
All checks were successful
sync-to-forgejo / sync (push) Successful in 16s
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). |
||
|---|---|---|
| .. | ||
| ai-guard | ||
| forgejo | ||
| github-actions-runners/base | ||
| litellm | ||
| nxtgauge-admin-solid | ||
| nxtgauge-ai-assistant | ||
| nxtgauge-backend-rust | ||
| nxtgauge-frontend-solid | ||
| ollama/base | ||
| postgresql | ||
| registry | ||
| traceworks2026 | ||