LibreChat/helm/librechat
Vijay Chegu 9e9a1d6a42
fix(helm): default MongoDB image tag to "latest" (fixes #11568)
Add image tag for MongoDB configuration in values.yaml

Problem
Fresh Helm installs fail with ImagePullBackOff because the Bitnami MongoDB sub-chart references a versioned image tag (e.g. 8.0.13-debian-12-r0) that no longer exists on Docker Hub. Bitnami removed all versioned tags from their bitnami/mongodb repository.

Fix
Set mongodb.image.tag: "latest" in the chart's default values.yaml so installs work out of the box.

Risk
latest is unpinned — a future Bitnami push could introduce breaking changes. For production, users should pin to a SHA256 digest. A longer-term fix could switch to the official mongo image or pin a stable digest.

Related Issues
Fixes #11568
Related: #11516, #10587, #10247, #10242
2026-03-13 19:27:40 -07:00
..
examples ☸️ feat: Helm hostAliases Support For Custom DNS Mappings (#9857) 2025-09-27 10:49:36 -04:00
templates 💎 feat: Add Redis as Optional Sub-chart Dependency in Helm Chart (#11664) 2026-02-14 13:57:01 -05:00
.helmignore 📊 feat: Improve Helm Chart (#3638) 2025-05-17 15:52:16 -04:00
Chart.yaml v0.8.3 (#12161) 2026-03-09 15:19:57 -04:00
DNS_CONFIGURATION.md 🌐 feat: Helm DNS Configuration Support for Traffic Redirection (#9785) 2025-09-23 10:41:58 -04:00
readme.md 📊 feat: Improve Helm Chart (#3638) 2025-05-17 15:52:16 -04:00
values.yaml fix(helm): default MongoDB image tag to "latest" (fixes #11568) 2026-03-13 19:27:40 -07:00

LibreChat Helm Chart

This Librechat Helm Chart provides an easy, light weight template to deploy LibreChat on Kubernetes

Variables

In this Chart, LibreChat will only work with environment Variables. You can Specify Vars and Secret using an existing Secret (This can be generated by creating an Env File and converting it to a Kubernetes Secret --from-env-file)

Setup

  1. Generate Variables Generate CREDS_KEY, JWT_SECRET, JWT_REFRESH_SECRET and MEILI_MASTER_KEY using openssl rand -hex 32 and CREDS_IV using openssl rand -hex 16. place them in a secret like this (If you want to change the secret name, remember to change it in your helm values):
apiVersion: v1
kind: Secret
metadata:
  name: librechat-credentials-env
  namespace: <librechat-chart-namespace>
type: Opaque
stringData:
  CREDS_KEY: <generated value>
  JWT_SECRET: <generated value>
  JWT_REFRESH_SECRET: <generated value>
  MEILI_MASTER_KEY: <generated value>
  1. Add Credentials to the Secret Dependant of the Model you want to use, create Credentials in your provider and add them to the Secret:
apiVersion: v1
kind: Secret
. . . .

  OPENAI_API_KEY: <your secret value>
  1. Apply the Secret to the Cluster

  2. Fill out values.yaml and apply the Chart to the Cluster