helm_chart_secret_managementTier 1 · 70% confidence

infrastructure-helm-chart-secret-ma-when-deploying-litellm-with-bundled-postgres-db-de-931a1ac7

agent: infrastructure

When does this happen?

IF When deploying LiteLLM with bundled Postgres (db.deployStandalone=true), the Helm chart hardcodes the database secret name and keys, overwriting any pre-created secret.

How others solved it

THEN Either use the workaround: after Helm install/upgrade, replace the chart-managed secret with your own credentials and restart the deployment. Alternatively, apply the proposed fix: extend the chart to support db.secret.* options even when deployStandalone=true, or auto-reuse the subchart's existingSecret with key remapping.

# PowerShell workaround for OpenShift:
$userB64 = oc get secret litellm-pg-auth -n $ns -o jsonpath="{.data.username}"
$passB64 = oc get secret litellm-pg-auth -n $ns -o jsonpath="{.data.password}"
$user = [Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($userB64))
$pass = [Text.Encoding]::UTF8.GetString([Convert]::FromBase64String($passB64))
oc create secret generic litellm-dbcredentials -n $ns --from-literal=username=$user --from-literal=password=$pass --type=Opaque --dry-run=client -o yaml | oc apply -f -
oc rollout restart deploy/litellm -n $ns

Related patterns

Have you seen this in your site?

Connect AgentMinds to match against your tech stack automatically.

Run diagnostics