### Check for existing issues

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

### What happened?

A bug happened!

**Problem** We are looking to upgrade our LiteLLM version to `1.86.x` and we noticed that the componentized chart at `helm/litellm` (v1.86+) expects four GHCR images:

- ghcr.io/berriai/litellm-gateway - ghcr.io/berriai/litellm-backend - ghcr.io/berriai/litellm-ui - ghcr.io/berriai/litellm-migrations

`docker manifest inspect` returns manifest unknown for these at release tags we tried, including latest stable v1.88.0 and v1.86.4.

Published images that do exist at those tags:

- ghcr.io/berriai/litellm-database:v1.88.0 (amd64 + arm64) - ghcr.io/berriai/litellm:v1.88.0 (amd64 + arm64)

We run arm64-only EKS and want to adopt `helm/litellm` instead of the legacy `litellm-helm` monolith.

**Questions**

- What are the correct repository + tag values for gateway, backend, ui, and migrations for v1.88.0 (or the recommended patch)? - Are component images published on a different schedule than litellm / litellm-database? If so, which release first includes them? - Will all four ship linux/arm64? We need arm64 for every component. - U…