Skip to content

fix(k8s): make LiteLLM emit https URLs behind the ingress #97

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jcschaff merged 1 commit into from
Aug 12, 2026
Merged

fix(k8s): make LiteLLM emit https URLs behind the ingress #97

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions kustomize/config/vcell-ai-rke-dev/litellm.env
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,3 +23,13 @@ LANGFUSE_HOST=https://cloud.langfuse.com
# rewrite-target and does NOT change route matching: the backend's in-cluster
# calls to http://litellm:4000/v1/... keep working unprefixed.
SERVER_ROOT_PATH=/kartik

# Trust the ingress controller's X-Forwarded-Proto so generated URLs use https.
# LiteLLM takes uvicorn's defaults, which install ProxyHeadersMiddleware but
# only trust 127.0.0.1 (uvicorn/config.py: FORWARDED_ALLOW_IPS default). nginx
# connects from a pod IP, so the header was ignored and /kartik/ui redirected to
# an http:// URL. Browsers recovered via a second hop, but it was a plaintext
# one. "*" is safe here because the Service is ClusterIP -- nothing outside the
# cluster can reach the pod directly to forge the header, and nginx overwrites
# it on every request.
FORWARDED_ALLOW_IPS=*
Loading