docs: document RUNPOD_ALLOW_IP IP allowlisting for Pods and Serverless - #837
Open
itsjdubois wants to merge 3 commits into
Open
docs: document RUNPOD_ALLOW_IP IP allowlisting for Pods and Serverless#837itsjdubois wants to merge 3 commits into
itsjdubois wants to merge 3 commits into
Conversation
Add customer-facing documentation for the RUNPOD_ALLOW_IP environment variable, which restricts inbound access by source IP for Pods (HTTP proxy) and Serverless endpoints. Behavior verified in production on 2026-09-09. - Pods > Expose ports: new "Restrict access by IP address" section, TCP bypass note, security and troubleshooting entries. - Pods > Environment variables: "Runpod-reserved variables" table. - Serverless > Endpoint settings: new "IP allowlist" section. - Serverless > Environment variables: "Runpod-reserved variables" table. - Serverless > Send API requests: 403 row in the error table. - Serverless > Load balancing overview: RUNPOD_ALLOW_IP env row. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Fold the RUNPOD_ALLOW_IP TCP caveat into prose and drop the duplicate note in the TCP section. Four callouts in thirty lines was too noisy. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Expand nothing, contract 'does not', drop passive voice and parentheticals, and say 'IP address ranges' instead of 'CIDR ranges' so the new paragraphs introduce zero Vale alerts relative to main. File-level readability scores were pre-existing and improve slightly. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Documents the
RUNPOD_ALLOW_IPenvironment variable, which restricts inbound access by source IP for Pods (HTTP proxy ports) and Serverless endpoints. The feature has existed in the proxy and ai-api for a long time but was undocumented apart from a one-line table row that has since been removed. Customers are asking support how to do IP allowlisting.What changed
RUNPOD_ALLOW_IProw in the environment variables table.Verified behavior (prod, 2026-09-09)
/runand/health, allowlist = non-matching IPip address not allowed/health, allowlist = caller IPIP,CIDREnforcement:
proxy/pkg/podproxy/proxy.go(pods, 400) andai-api/pkg/api/userAuth.go(serverless, 403), both keyed onCF-Connecting-IP.Notes for reviewer
RUNPOD_DISABLE_AUTHis parsed alongsideRUNPOD_ALLOW_IPin ai-api but is intentionally not documented here; that's a separate product decision.