d503a32de7
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.
71 lines
2.1 KiB
YAML
71 lines
2.1 KiB
YAML
apiVersion: apps/v1
|
|
kind: Deployment
|
|
metadata:
|
|
name: litellm
|
|
namespace: nxtgauge-ai
|
|
labels:
|
|
app: litellm
|
|
spec:
|
|
replicas: 1
|
|
selector:
|
|
matchLabels:
|
|
app: litellm
|
|
template:
|
|
metadata:
|
|
labels:
|
|
app: litellm
|
|
spec:
|
|
containers:
|
|
- name: litellm
|
|
# This app was never included in Flux's root kustomization (see
|
|
# clusters/production/kustomization.yaml), so it was only ever
|
|
# deployed by a one-off manual `kubectl apply` and has since
|
|
# drifted from this file. Corrected to match what's actually
|
|
# running live (the real upstream image) rather than
|
|
# registry.nxtgauge.com/litellm:latest, which doesn't appear to
|
|
# exist/be maintained — using it would have broken a working
|
|
# deployment the moment this file was wired back into GitOps.
|
|
image: ghcr.io/berriai/litellm:latest
|
|
command:
|
|
- "/bin/bash"
|
|
args:
|
|
- "-c"
|
|
- "cat /app/config.yaml && exec litellm --config /app/config.yaml --port 4000 --host 0.0.0.0"
|
|
ports:
|
|
- containerPort: 4000
|
|
name: http
|
|
env:
|
|
- name: LITELLM_MASTER_KEY
|
|
valueFrom:
|
|
secretKeyRef:
|
|
name: litellm-secrets
|
|
key: LITELLM_MASTER_KEY
|
|
- name: LITELLM_LOG_LEVEL
|
|
value: "DEBUG"
|
|
volumeMounts:
|
|
- name: config
|
|
mountPath: /app/config.yaml
|
|
subPath: config.yaml
|
|
readOnly: true
|
|
resources:
|
|
requests:
|
|
cpu: 100m
|
|
memory: 256Mi
|
|
livenessProbe:
|
|
tcpSocket:
|
|
port: 4000
|
|
initialDelaySeconds: 60
|
|
periodSeconds: 10
|
|
timeoutSeconds: 5
|
|
failureThreshold: 3
|
|
readinessProbe:
|
|
tcpSocket:
|
|
port: 4000
|
|
initialDelaySeconds: 30
|
|
periodSeconds: 5
|
|
timeoutSeconds: 3
|
|
failureThreshold: 3
|
|
volumes:
|
|
- name: config
|
|
configMap:
|
|
name: litellm-config
|