fix(litellm): restore DATABASE_URL env var lost when adopting the drifted live deployment
All checks were successful
sync-to-forgejo / sync (push) Successful in 14s
All checks were successful
sync-to-forgejo / sync (push) Successful in 14s
kubectl apply replaced the live pod's env list wholesale with what was in this file (which never had DATABASE_URL, despite the litellm-db-credentials secret already existing) — litellm's proxy requires DB connectivity to fully start regardless of config.yaml content, so this caused an immediate crash loop. Restored it.
This commit is contained in:
parent
4ea0e2ae43
commit
2c34d78534
1 changed files with 13 additions and 0 deletions
|
|
@ -42,6 +42,19 @@ spec:
|
||||||
key: LITELLM_MASTER_KEY
|
key: LITELLM_MASTER_KEY
|
||||||
- name: LITELLM_LOG_LEVEL
|
- name: LITELLM_LOG_LEVEL
|
||||||
value: "DEBUG"
|
value: "DEBUG"
|
||||||
|
# Present on the live (drifted) deployment but missing from this
|
||||||
|
# file — LiteLLM's proxy tries to reach Postgres for spend
|
||||||
|
# tracking/virtual-key storage regardless of whether
|
||||||
|
# general_settings.database_url is set in config.yaml, and
|
||||||
|
# fails startup entirely if DATABASE_URL is unset (discovered
|
||||||
|
# when adopting this file caused a crash loop: the litellm-db-
|
||||||
|
# credentials secret already existed, this file just never
|
||||||
|
# referenced it).
|
||||||
|
- name: DATABASE_URL
|
||||||
|
valueFrom:
|
||||||
|
secretKeyRef:
|
||||||
|
name: litellm-db-credentials
|
||||||
|
key: DATABASE_URL
|
||||||
volumeMounts:
|
volumeMounts:
|
||||||
- name: config
|
- name: config
|
||||||
mountPath: /app/config.yaml
|
mountPath: /app/config.yaml
|
||||||
|
|
|
||||||
Loading…
Add table
Reference in a new issue