mirror of
https://github.com/BerriAI/litellm.git
synced 2026-08-28 05:25:59 +00:00
cd9c410ae2
Bitnami retired the versioned tags under docker.io/bitnami and republished the archived builds under docker.io/bitnamilegacy, so every install and upgrade of the chart with the bundled database fails to pull docker.io/bitnami/postgresql:16.2.0-debian-12-r6. Repoint the subchart images at the bitnamilegacy copies of the exact builds those subchart versions shipped with, so the on-disk data directory layout is unchanged for existing installs. Pin the subchart dependency ranges to the versions already in Chart.lock. The current bitnami postgresql chart defaults to `tag: latest`, which is PostgreSQL 18 today, so an open-ended range turns a dependency refresh into a major-version jump on an existing volume. Refuse to render when postgresql.image.tag is empty or `latest` while the bundled database is deployed. Starting a different PostgreSQL major against an existing data directory leaves the server unable to boot with no in-place way back, which is how the reported install lost its data. Resolves LIT-4708
13 lines
No EOL
530 B
YAML
13 lines
No EOL
530 B
YAML
{{- if .Values.db.deployStandalone -}}
|
|
{{- include "litellm.validateBundledPostgresImageTag" . -}}
|
|
apiVersion: v1
|
|
kind: Secret
|
|
metadata:
|
|
name: {{ include "litellm.fullname" . }}-dbcredentials
|
|
data:
|
|
# Password for the "postgres" user
|
|
postgres-password: {{ ( index .Values.postgresql.auth "postgres-password") | default "litellm" | b64enc }}
|
|
username: {{ .Values.postgresql.auth.username | default "litellm" | b64enc }}
|
|
password: {{ .Values.postgresql.auth.password | default "litellm" | b64enc }}
|
|
type: Opaque
|
|
{{- end -}} |