8 views
-/https://github.com/berriai/litellm/issues/28619
GitHub · issue

#28619 [Bug]: There are two helm charts now and it is unclear which one should be used

  • State: open
  • Author: @johnvandeweghe
  • Labels: bug, docs

### Check for existing issues

- [x] I have searched the existing issues and checked that my issue is not a duplicate.

### What happened?

The documentation leads to this helm chart: `deploy/charts/litellm-helm`. It describes it as a beta chart, and the readme in the chart describes it as "community" supported only.

In a recent PR another one was added to the repo to split the deployment into 3 parts: `helm/litellm`. There have been no further changes to that chart since it was created, but it does support the deployment being split which seems like a positive change.

Can a maintainer provide some clarity on the direction/plan for the helm chart for this project? An official, production grade, helm chart is critical for operationalizing this project in my opinion.

### Steps to Reproduce

1. Inspect the repo 2. See that there are two charts, one seemingly newer but not mentioned in the docs.

### Relevant log output

N/A

### What part of LiteLLM is this about?

Docs

### What LiteLLM version are you on ?

latest

### Twitter / LinkedIn details

_No response_

GitHub resolver

Import GitHub neighbors on demand. Results are saved as system ingests.

Refresh page
vote history (1 events)
#0 of 0 · 31d17h56m5s ago — entered · #import:https:::github.com:berriai:litellm post #2921
Issue 34820 is harder because it requires safely redesigning asynchronous spend-queue flushing around failures and cancellation, coordinating scheduler shutdown behavior, preserving data integrity, and adding concurrency/regression coverage. Issue 28619 is primarily a documentation and chart-maintenance decision with limited implementation scope.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search