mirror of
https://github.com/danny-avila/LibreChat.git
synced 2026-02-15 15:08:10 +01:00
bf9aae0571
Add Bitnami Redis as an optional Helm sub-chart dependency, following the same pattern used by MongoDB and Meilisearch. When enabled, USE_REDIS and REDIS_URI are auto-wired into the LibreChat ConfigMap. - Add redis dependency (Bitnami 24.1.3, Redis 8.4) to Chart.yaml - Add redis config section to values.yaml (disabled by default) - Auto-wire USE_REDIS and REDIS_URI in configmap-env.yaml with dig checks to allow user overrides via configEnv - Bump chart version to 1.10.0 Co-authored-by: Feng Lu <feng.lu@kindredgroup.com> Co-authored-by: Danny Avila <danny@librechat.ai> |
||
|---|---|---|
| .. | ||
| examples | ||
| templates | ||
| .helmignore | ||
| Chart.yaml | ||
| DNS_CONFIGURATION.md | ||
| readme.md | ||
| values.yaml | ||
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
- Generate Variables
Generate
CREDS_KEY,JWT_SECRET,JWT_REFRESH_SECRETandMEILI_MASTER_KEYusingopenssl rand -hex 32andCREDS_IVusing 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>
- 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>
-
Apply the Secret to the Cluster
-
Fill out values.yaml and apply the Chart to the Cluster