6 views
-/https://github.com/berriai/litellm/issues/30311
GitHub · issue

#30311 [Bug]: Migration job in helm chart does not support envFrom secrets or configmaps

  • State: open
  • Author: @calebhansard
  • Labels: bug

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

The migration job in the LiteLLM helm chart does not support environmentSecrets or environmentConfigMaps. If env vars are added there that are required for LiteLLM to run, the job will quit with no changes.

### Steps to Reproduce

1. Add environment variables to a secret or configmap 2. Use `environmentSecrets` or `environmentConfigMaps` in the values file to read the env vars 3. The migration job does not run as it cannot connect to the db

### Suggested fix

Add the following to mirgation-job.yaml

```yaml envFrom: {{- range .Values.environmentSecrets }} - secretRef: name: {{ . }} {{- end }} {{- range .Values.environmentConfigMaps }} - configMapRef: name: {{ . }} {{- end }} ```

### What part of LiteLLM is this about?

Other

### What LiteLLM version are you on ?

1.88.1

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d17h59m38s ago — entered · #import:https:::github.com:berriai:litellm post #3081
The right issue is harder because it likely requires tracing provider-specific tool-call translation, conversation-state handling, and compatibility with an external client/API contract. The left issue is a localized Helm template change with a relatively contained validation surface.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search