Skip to content

Add LLM Auth Proxy without-public-ingress note to V15 release notes #4210

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

Draft
langsmith-fleet wants to merge 1 commit into
base: main
Choose a base branch
from
Draft

Add LLM Auth Proxy without-public-ingress note to V15 release notes #4210

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
1 change: 1 addition & 0 deletions src/langsmith/self-hosted-changelog.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,7 @@ Follow the [upgrade instructions](/langsmith/self-host-upgrades) to get access t
### Infrastructure changes

- **Section renames from the Fleet rename** — several sections were renamed as part of the Agent Builder to [Fleet](/langsmith/fleet) rename (see [Breaking changes](#breaking-changes)). You may need to update service accounts or shift values in your configuration.
- **LLM Auth Proxy without a public ingress** — if the LLM Auth Proxy is deployed without a public ingress and is only reachable through internal Kubernetes networking, you must add `SSRF_ALLOW_K8S_INTERNAL` to all services that make LLM calls and `SSRF_ALLOW_PRIVATE_IPS_PLAYGROUND` to the `playground` service. Without these settings, the built-in SSRF protection blocks requests to private IPs. See [Deploy without a public ingress](/langsmith/llm-auth-proxy-self-hosted#deploy-without-a-public-ingress) for full configuration details.

### New features

Expand Down
Loading