Yassin Kortam 37c6bad289 fix(helm): meter the backend too, it serves the MCP transport ... Scoping billingMetrics to the gateway was wrong. Applying each component's own route allowlist to the proxy app shows the split is 75 billable routes on the gateway and one on the backend: /{mcp_server_name}/mcp, the named-server MCP transport, which writes a SpendLogs row on success. Metering only the gateway would have silently dropped every MCP transport call from the counter, an undercount proportional to a customer's MCP traffic. The backend deployment now renders the same env and mounts the same read-only cert secret. The migrations job still gets neither; it runs prisma and serves no traffic, and a test pins that. helm unittest -f 'tests/*.yaml' helm/litellm # 25 passed helm unittest -f 'tests/*.yaml' helm/litellm-helm # 69 passed This also aligns the chart with the terraform templates, which inject the credentials into both components.		2026-07-09 20:08:00 +03:00
..
litellm	fix(helm): meter the backend too, it serves the MCP transport	2026-07-09 20:08:00 +03:00
litellm-helm	test(helm): pin that the migrations job never mounts the billing cert	2026-07-09 19:57:39 +03:00