mirror of
https://github.com/BerriAI/litellm.git
synced 2026-08-28 05:25:59 +00:00
ae3e19a83f
Both charts run schema migrations from a Job that is a pre-install and pre-upgrade hook, and neither set activeDeadlineSeconds. A migration that blocks on the database therefore never fails: backoffLimit is not reached because the pod never terminates, so the Job stays active indefinitely and the release waits on the hook forever. `helm upgrade` and any GitOps controller driving it stop reconciling the whole chart until someone deletes the Job by hand, which means unrelated changes to the gateway, the backend and the UI silently stop shipping. Give the field a 1800s default, guarded by `with` so setting it to null restores the old unbounded behaviour. A migration that has exhausted its retries is not going to succeed on the next one, so failing is strictly better than hanging: a failed sync is visible and retryable, a hung one is neither. Chart.yaml is deliberately untouched. Recent template-only changes to litellm-helm did not bump it either. |
||
|---|---|---|
| .. | ||
| tests | ||
| _helpers.tpl | ||
| configmap-litellm.yaml | ||
| deployment.yaml | ||
| extra-resources.yaml | ||
| hpa.yaml | ||
| ingress.yaml | ||
| keda.yaml | ||
| migrations-job.yaml | ||
| NOTES.txt | ||
| poddisruptionbudget.yaml | ||
| secret-dbcredentials.yaml | ||
| secret-masterkey.yaml | ||
| service.yaml | ||
| serviceaccount.yaml | ||
| servicemonitor.yaml | ||