sshiv012 opened a new pull request, #9082: URL: https://github.com/apache/texera/pull/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) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
