Yassin Kortam f77c13edf4 feat(helm): add billingMetrics values to the classic chart ... The componentized chart just gained a first-class billingMetrics block; this mirrors it in litellm-helm so enabling enterprise billable-request metering no longer means hand-rolling the env vars and the cert volume through envVars and volumes. When enabled the proxy Deployment renders LITELLM_BILLING_METRICS_ENDPOINT plus the two cert paths, and mounts secretName read-only at /etc/litellm/billing-mtls. secretName defaults to litellm-billing-metrics-mtls, the conventional name, so enabling the block is enough once that Secret exists. caSecretName is optional and only needed for private collectors whose server certificate is not on the public web PKI; when set it mounts at /etc/litellm/billing-mtls-ca and adds the CA env var. exportIntervalMs is passed through only when set. The env entries render after envVars and extraEnvVars, so a user-supplied LITELLM_BILLING_METRICS_ENDPOINT cannot silently redirect the export under Kubernetes last-wins duplicate-env semantics; this is the same ordering the migrations Job relies on for DISABLE_SCHEMA_UPDATE. Enabling with an emptied secretName or endpoint fails the render with a named message rather than producing a proxy that silently never exports. The generic volumes, volumeMounts, envVars and extraEnvVars paths are untouched and still compose with this, so existing overlays keep working. The chart has no values.schema.json; README parameters and a setup section are updated. helm unittest -f 'tests/*.yaml' helm/litellm-helm # 68 passed (54 + 14 new) helm lint helm/litellm-helm # 0 failed		2026-07-09 19:54:55 +03:00
..
litellm	feat(helm): add first-class billingMetrics values to the componentized chart	2026-07-09 19:44:22 +03:00
litellm-helm	feat(helm): add billingMetrics values to the classic chart	2026-07-09 19:54:55 +03:00