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

#29348 [Bug]: Helm chart default image tag main-<appVersion> does not exist on ghcr for stable releases → ImagePullBackOff

  • State: open
  • Author: @aSauerwein
  • Labels: bug

### Check for existing issues

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

### What happened?

Installing `oci://ghcr.io/berriai/litellm-helm` with no `image.tag` override fails with `ImagePullBackOff`. The chart's default renders an image tag that is **not published** to `ghcr.io/berriai/litellm-database`.

## Root cause

`templates/deployment.yaml` and `templates/migrations-job.yaml` both default the tag to `main-<AppVersion>`:

```yaml image: "{{ .Values.image.repository }}:{{ .Values.image.tag | default (printf "main-%s" .Chart.AppVersion) }}" ```

For chart 1.86.2 (`AppVersion: 1.86.2`) this renders `ghcr.io/berriai/litellm-database:main-1.86.2`, which returns **404**. The registry has the plain `1.86.2` tag (and `main-stable`), but not `main-1.86.2`.

## This is systemic across recent stable releases

Anonymous manifest checks on `ghcr.io/berriai/litellm-database`:

| Chart version | `main-<ver>` (default) | `<ver>` (plain) | |---|---|---| | 1.84.0 / 1.84.1 / 1.84.3 | 404 | 200 | | 1.85.0 / 1.85.1 / 1.85.2 | 404 | 200 | | 1.86.1 / 1.86.2 | 404 | 200 |

The published `1.86.2` tag and `main-stable` resolve to the **same digest** (`sh…

GitHub resolver

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

Refresh page
vote history (6 events)
#0 of 0 · 31d19h11m51s ago — entered · #import:https:::github.com:berriai:litellm post #1689
The right issue is harder because it likely requires tracing packaging, dependency inclusion, Prisma generation, and multiple installation/runtime paths, with broader compatibility and release risks. The left issue is comparatively localized to Helm image-tag defaults and chart validation.
The left item requires cross-provider response normalization, streaming-path handling, and compatibility regression testing, while the right is a localized Helm configuration correction.
29382 requires diagnosing and correcting the multi-architecture container build or publishing pipeline, validating native ARM artifacts, and potentially rebuilding and republishing affected releases. It carries broader release, CI, registry, and compatibility risks. 29348 is primarily a localized Helm default-value correction with focused template and installation tests.
The left issue is harder because it requires diagnosing request-scheme propagation across multiple proxy layers and safely correcting framework redirect behavior, with environment-dependent testing. The right issue is comparatively localized to Helm image-tag defaults and release validation.
The Helm chart issue is harder because it spans image-tag conventions, chart templating, release packaging, and deployment validation, whereas the dashboard issue is a localized provider-label/mapping correction.
#0 of 0 · 31d18h44m9s ago — current · #import:https:::github.com:berriai:litellm post #2147
The left issue is harder because it likely requires coordinated authorization, API, UI, and regression-test changes with security implications. The right issue is comparatively localized to Helm image-selection logic and release validation.
discussed in #import:https:::github.com:berriai:litellm

ranked child groups

no voted pairs yet in this scope

cli
src
spread
search