### Check for existing issues

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

### The Feature

When `db.deployStandalone: true`, the chart always creates its own *-dbcredentials Secret from plaintext postgresql.auth.* values and hardcodes the deployment and migration job to read it.

There's no way to source credentials from an existing secret (e.g. ExternalSecret/vault), so the proxy and Postgres can end up with mismatched credentials.

### Motivation, pitch

Deploying LiteLLM with the chart-managed standalone Postgres and want to keep database credentials in a vault (synced via ExternalSecret) rather than in plaintext values.

### What part of LiteLLM is this about?

Helm Chart

### LiteLLM is hiring a founding backend engineer, are you interested in joining us and shipping to all our users?

No

### Twitter / LinkedIn details

_No response_