Submit
All skills
Skillintermediate

Helm Chart for LiteLLM

> [!IMPORTANT] > This is community maintained, Please make an issue if you run into a bug > We recommend using [Docker or Kubernetes for production deployments](https://docs.litellm.ai/docs/proxy/prod)

Claude Code Knowledge Pack7/10/2026

Overview

Helm Chart for LiteLLM

[!IMPORTANT] This is community maintained, Please make an issue if you run into a bug We recommend using Docker or Kubernetes for production deployments

Prerequisites

  • Kubernetes 1.21+
  • Helm 3.8.0+

If db.deployStandalone is used:

  • PV provisioner support in the underlying infrastructure

If db.useStackgresOperator is used (not yet implemented):

  • The Stackgres Operator must already be installed in the Kubernetes Cluster. This chart will not install the operator if it is missing.

Parameters

LiteLLM Proxy Deployment Settings

NameDescriptionValue
replicaCountThe number of LiteLLM Proxy pods to be deployed1
masterkeySecretNameThe name of the Kubernetes Secret that contains the Master API Key for LiteLLM. If not specified, use the generated secret name.N/A
masterkeySecretKeyThe key within the Kubernetes Secret that contains the Master API Key for LiteLLM. If not specified, use masterkey as the key.N/A
masterkeyThe Master API Key for LiteLLM. If not specified, a random key in the sk-... format is generated.N/A
environmentSecretsAn optional array of Secret object names. The keys and values in these secrets will be presented to the LiteLLM proxy pod as environment variables. See below for an example Secret object.[]
environmentConfigMapsAn optional array of ConfigMap object names. The keys and values in these configmaps will be presented to the LiteLLM proxy pod as environment variables. See below for an example Secret object.[]
image.repositoryLiteLLM Proxy image repositorydocker.litellm.ai/berriai/litellm
image.pullPolicyLiteLLM Proxy image pull policyIfNotPresent
image.tagOverrides the image tag whose default the latest version of LiteLLM at the time this chart was published.""
imagePullSecretsRegistry credentials for the LiteLLM and initContainer images.[]
serviceAccount.createWhether or not to create a Kubernetes Service Account for this deployment. The default is false because LiteLLM has no need to access the Kubernetes API.false
service.typeKubernetes Service type (e.g. LoadBalancer, ClusterIP, etc.)ClusterIP
service.portTCP port that the Kubernetes Service will listen on. Also the TCP port within the Pod that the proxy will listen on.4000
livenessProbe.*Liveness probe settings for the LiteLLM container (path, periodSeconds, timeoutSeconds, thresholds, and initial delay).See values.yaml
readinessProbe.*Readiness probe settings for the LiteLLM container (path, periodSeconds, timeoutSeconds, thresholds, and initial delay).See values.yaml
startupProbe.*Startup probe settings for the LiteLLM container (path, periodSeconds, timeoutSeconds, thresholds, and initial delay).See values.yaml
resources.*CPU/memory requests and limits for the LiteLLM container.{}
service.loadBalancerClassOptional LoadBalancer implementation class (only used when service.type is LoadBalancer)""
ingress.labelsAdditional labels for the Ingress resource{}
ingress.*See values.yaml for example settingsN/A
proxyConfigMap.createWhen true, render a ConfigMap from .Values.proxy_config and mount it.true
proxyConfigMap.nameWhen create=false, name of the existing ConfigMap to mount.""
proxyConfigMap.keyKey in the ConfigMap that contains the proxy config file."config.yaml"
proxy_config.*See values.yaml for default settings. Rendered into the ConfigMap’s config.yaml only when proxyConfigMap.create=true. See example_config_yaml for configuration examples.N/A
extraContainers[]An array of additional containers to be deployed as sidecars alongside the LiteLLM Proxy.
pdb.enabledEnable a PodDisruptionBudget for the LiteLLM proxy Deploymentfalse
pdb.minAvailableMinimum number/percentage of pods that must be available during voluntary disruptions (choose one of minAvailable/maxUnavailable)null
pdb.maxUnavailableMaximum number/percentage of pods that can be unavailable during voluntary disruptions (choose one of minAvailable/maxUnavailable)null
pdb.annotationsExtra metadata annotations to add to the PDB{}
pdb.labelsExtra metadata labels to add to the PDB{}

Example proxy_config ConfigMap from values (default):

proxyConfigMap:
  create: true
  key: "config.yaml"

proxy_config:
  general_settings:
    master_key: os.environ/PROXY_MASTER_KEY
  model_list:
    - model_name: gpt-3.5-turbo
      litellm_params:
        model: gpt-3.5-turbo
        api_key: eXaMpLeOnLy

Example using existing proxyConfigMap instead of creating it:

proxyConfigMap:
  create: false
  name: my-litellm-config
  key: config.yaml

# proxy_config is ignored in this mode

Example environmentSecrets Secret

apiVersion: v1
kind: Secret
metadata:
  name: litellm-envsecrets
data:
  AZURE_OPENAI_API_KEY: TXlTZWN1cmVLM3k=
type: Opaque

Database Settings

NameDescriptionValue
db.useExistingUse an existing Postgres database. A Kubernetes Secret object must exist that contains credentials for connecting to the database. An example secret object definition is provided below.false
db.endpointIf db.useExisting is true, this is the IP, Hostname or Service Name of the Postgres server to connect to.localhost
db.databaseIf db.useExisting is true, the name of the existing database to connect to.litellm
db.urlIf db.useExisting is true, the connection url of the existing database to connect to can be overwritten with this value.postgresql://$(DATABASE_USERNAME):$(DATABASE_PASSWORD)@$(DATABASE_HOST)/$(DATABASE_NAME)
db.secret.nameIf db.useExisting is true, the name of the Kubernetes Secret that contains credentials.postgres
db.secret.usernameKeyIf db.useExisting is true, the name of the key within the Kubernetes Secret that holds the username for authenticating with the Postgres instance.username
db.secret.passwordKeyIf db.useExisting is true, the name of the key within the Kubernetes Secret that holds the password associates with the above user.password
db.useStackgresOperatorNot yet implemented.false