feat: add LiteLLM Dashboard helm chart for deployment #20
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Koufan-De-King
requested changes
Oct 21, 2025
Koufan-De-King
approved these changes
Oct 23, 2025
Comment on lines
+42
to
+73
| **To create and inject your secrets:** | ||
|
|
||
| 1. **Create a `secret.yaml` file:** Copy the content of `charts/litellm-dashboard/templates/secret.example.yaml` to a new file named `secret.yaml` (or any other desired name) outside of the Helm chart directory. | ||
| ```bash | ||
| cp charts/litellm-dashboard/templates/secret.example.yaml secret.yaml | ||
| ``` | ||
|
|
||
| 2. **Populate with your sensitive data:** Edit the `secret.yaml` file and replace the placeholder values with your actual sensitive information. | ||
| ```yaml | ||
| apiVersion: v1 | ||
| kind: Secret | ||
| metadata: | ||
| name: litellm-credentials-secret | ||
| type: Opaque | ||
| stringData: | ||
| LITELLM_PROXY_URL: "your-litellm-proxy-url" | ||
| LITELLM_API_KEY: "your-litellm-api-key" | ||
| NEXT_AUTH_SECRET: "your-next-auth-secret" | ||
| ADMIN_EMAIL: "your-admin-email" | ||
| ADMIN_PASSWORD: "your-admin-password" | ||
| NODE_ENV: "production" | ||
| ``` | ||
|
|
||
| 3. **Apply the secret to your Kubernetes cluster:** | ||
| ```bash | ||
| kubectl apply -f secret.yaml -n <your-namespace> | ||
| ``` | ||
| Replace `<your-namespace>` with the namespace where you intend to deploy the LiteLLM Dashboard. | ||
|
|
||
| 4. **Helm Chart Integration:** The `values.yaml` file within this Helm chart is already configured to reference the `litellm-credentials-secret`. This ensures that the environment variables are automatically injected into the LiteLLM Dashboard pod when the chart is deployed, without hardcoding sensitive data directly into the chart. | ||
|
|
||
| --- |
There was a problem hiding this comment.
Perfect!
Is it possible to do better with these secrets? Like to have them injected from an environment variable instead? I am skeptical about having to manually apply the secret.
There was a problem hiding this comment.
You should add secret.yaml to .gitignore for safety.
marcjazz
requested changes
Oct 24, 2025
Comment on lines
+70
to
+73
| command: | ||
| - /bin/sh | ||
| - -c | ||
| - SKIP_ENV_VALIDATION=1 yarn start |
There was a problem hiding this comment.
This will not be needed if the image if built correctly.
Comment on lines
+46
to
+68
| probes: | ||
| liveness: | ||
| enabled: true | ||
| custom: false | ||
| spec: | ||
| httpGet: | ||
| path: /health | ||
| port: http | ||
| initialDelaySeconds: 10 | ||
| periodSeconds: 10 | ||
| timeoutSeconds: 3 | ||
| failureThreshold: 3 | ||
| readiness: | ||
| enabled: true | ||
| custom: false | ||
| spec: | ||
| httpGet: | ||
| path: /health | ||
| port: http | ||
| initialDelaySeconds: 5 | ||
| periodSeconds: 5 | ||
| timeoutSeconds: 3 | ||
| failureThreshold: 3 |
There was a problem hiding this comment.
Is the /health endpoint expose by the lite-llm-customer server?
Comment on lines
+42
to
+73
| **To create and inject your secrets:** | ||
|
|
||
| 1. **Create a `secret.yaml` file:** Copy the content of `charts/litellm-dashboard/templates/secret.example.yaml` to a new file named `secret.yaml` (or any other desired name) outside of the Helm chart directory. | ||
| ```bash | ||
| cp charts/litellm-dashboard/templates/secret.example.yaml secret.yaml | ||
| ``` | ||
|
|
||
| 2. **Populate with your sensitive data:** Edit the `secret.yaml` file and replace the placeholder values with your actual sensitive information. | ||
| ```yaml | ||
| apiVersion: v1 | ||
| kind: Secret | ||
| metadata: | ||
| name: litellm-credentials-secret | ||
| type: Opaque | ||
| stringData: | ||
| LITELLM_PROXY_URL: "your-litellm-proxy-url" | ||
| LITELLM_API_KEY: "your-litellm-api-key" | ||
| NEXT_AUTH_SECRET: "your-next-auth-secret" | ||
| ADMIN_EMAIL: "your-admin-email" | ||
| ADMIN_PASSWORD: "your-admin-password" | ||
| NODE_ENV: "production" | ||
| ``` | ||
|
|
||
| 3. **Apply the secret to your Kubernetes cluster:** | ||
| ```bash | ||
| kubectl apply -f secret.yaml -n <your-namespace> | ||
| ``` | ||
| Replace `<your-namespace>` with the namespace where you intend to deploy the LiteLLM Dashboard. | ||
|
|
||
| 4. **Helm Chart Integration:** The `values.yaml` file within this Helm chart is already configured to reference the `litellm-credentials-secret`. This ensures that the environment variables are automatically injected into the LiteLLM Dashboard pod when the chart is deployed, without hardcoding sensitive data directly into the chart. | ||
|
|
||
| --- |
There was a problem hiding this comment.
You should add secret.yaml to .gitignore for safety.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.