You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@texera.apache.org by gi...@apache.org on 2026/10/22 07:59:39 UTC
(texera) 01/01: fix(k8s): pin the LiteLLM image to the version single-node uses (#9082)
This is an automated email from the ASF dual-hosted git repository.
github-merge-queue[bot] pushed a commit to branch gh-readonly-queue/main/pr-9082-9b9ffae6beb3e2bae3766f7470620885aefbc791
in repository https://gitbox.apache.org/repos/asf/texera.git
commit 497a3b61461865c1f82aa2064e660b698b8c8214
Author: Suryaa Charan <12...@users.noreply.github.com>
AuthorDate: Thu Oct 22 07:59:15 2026 +0000
fix(k8s): pin the LiteLLM image to the version single-node uses (#9082)
### What changes were proposed in this PR?
Pin the LiteLLM image in the Helm chart to the version single-node
already uses.
The chart used the moving tag `litellm/litellm:main-stable`, so any pod
restart could pull a new LiteLLM build without a Texera change. That is
how the compressed-reply bug in #9080 reached our k8s deployment.
| File | Before | After |
| --- | --- | --- |
| `bin/k8s/values.yaml` | `litellm/litellm:main-stable` |
`ghcr.io/berriai/litellm:v1.83.10-stable` |
| `bin/k8s/values-development.yaml` | `litellm/litellm:main-stable` |
`ghcr.io/berriai/litellm:v1.83.10-stable` |
`bin/single-node/docker-compose.yml` already uses
`ghcr.io/berriai/litellm:v1.83.10-stable`, so both deployments now run
the same LiteLLM. Future upgrades become a deliberate bump in both
places.
This does not replace the proxy fix for #9080; it only stops surprise
upgrades.
### Any related issues, documentation, discussions?
Closes #9081
Related: #9080
### How was this PR tested?
Chart (from a copy with `helm dependency build`):
```
helm lint . -f values.yaml # 1 chart(s) linted, 0 chart(s) failed
helm lint . -f values-development.yaml # 1 chart(s) linted, 0 chart(s) failed
helm template t . -f <each values file> # renders image: ghcr.io/berriai/litellm:v1.83.10-stable
```
Deployed on local minikube: the chart's LiteLLM deployment, service,
config and secret, plus the chart's Postgres and init script.
| Check | Result |
| --- | --- |
| Image pulls from GHCR | ok |
| Prisma migrations against `texera_litellm` | "Migration diff applied
successfully" |
| `GET /health/liveliness` | `"I'm alive!"` |
| `GET /models` with the chart's master key | 200, lists
`claude-haiku-4.5`, `gpt-5-mini` |
Not tested: a successful chat completion (no provider API key on the
test cluster), and a full Texera install on k8s. Minikube used the
`standard` storage class instead of `local-path` for the Postgres PVC
(test-only).
### Was this PR authored or co-authored using generative AI tooling?
Generated-by: Claude Code (Claude Opus 5.5)
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 5.5 <no...@anthropic.com>
---
bin/k8s/values-development.yaml | 2 +-
bin/k8s/values.yaml | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/bin/k8s/values-development.yaml b/bin/k8s/values-development.yaml
index 5cbda8ee0d..737da95db0 100644
--- a/bin/k8s/values-development.yaml
+++ b/bin/k8s/values-development.yaml
@@ -253,7 +253,7 @@ agentService:
litellm:
enabled: true
name: litellm
- image: litellm/litellm:main-stable
+ image: ghcr.io/berriai/litellm:v1.83.10-stable
numOfPods: 1
service:
type: ClusterIP
diff --git a/bin/k8s/values.yaml b/bin/k8s/values.yaml
index 2058b2a0f8..1a55a6d0dc 100644
--- a/bin/k8s/values.yaml
+++ b/bin/k8s/values.yaml
@@ -346,7 +346,7 @@ agentService:
litellm:
enabled: true
name: litellm
- image: litellm/litellm:main-stable
+ image: ghcr.io/berriai/litellm:v1.83.10-stable
numOfPods: 1
service:
type: ClusterIP