# Scaled to 0 (Phase 0 of the AI architecture doc — "Stabilize the Existing # Environment"): ai-guard has no Dockerfile in its source repo, so no image # has ever been successfully built by its CI. The pod has been in # ImagePullBackOff for 14+ days (90,000+ failed pulls) pulling an image that # doesn't exist. It also has no Service (unreachable even if healthy) and # depends on llm-guard/presidio, neither of which are deployed. Nothing # currently routes through it — both AI consumers (nxtgauge-ai-assistant, # nxtgauge-backend-rust) call LiteLLM directly. Scaling to 0 stops the # wasted kubelet pull-retry churn until Phase 3 (Rebuild ai-guard) is done # properly, per the architecture doc. apiVersion: apps/v1 kind: Deployment metadata: name: ai-guard namespace: nxtgauge-ai labels: app: ai-guard spec: replicas: 0 selector: matchLabels: app: ai-guard template: metadata: labels: app: ai-guard spec: containers: - name: ai-guard image: registry.nxtgauge.com/ai-guard:latest imagePullPolicy: Always ports: - containerPort: 8080 name: http env: - name: RUST_LOG value: "info" - name: PORT value: "8080" - name: OLLAMA_BASE_URL value: "http://ollama.nxtgauge-ai.svc.cluster.local:11434" - name: OLLAMA_CHAT_MODEL value: "gemma3:270m" - name: LLM_GUARD_URL value: "http://llm-guard.nxtgauge-ai.svc.cluster.local:8000" - name: PRESIDIO_URL value: "http://presidio.nxtgauge-ai.svc.cluster.local:3000" - name: AI_SERVICE_KEY valueFrom: secretKeyRef: name: ai-guard-secrets key: ai-service-key resources: requests: cpu: 100m memory: 128Mi limits: cpu: 1000m memory: 512Mi livenessProbe: httpGet: path: /health port: 8080 initialDelaySeconds: 10 periodSeconds: 20 readinessProbe: httpGet: path: /health port: 8080 initialDelaySeconds: 5 periodSeconds: 10