Clarify proxy registry token endpoint behavior #3784
Merged
Conversation
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
Add note to custom domains documentation explaining that /v2/token authentication endpoints are expected behavior for the Docker Registry v2 API. This helps customers understand that anonymous tokens appearing in whitelabeled registry URLs are standard Docker registry behavior and not a security concern. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
| - **Proxy registry:** Images can be proxied from external private registries using the Replicated proxy registry. By default, the proxy registry uses the domain `proxy.replicated.com`. Replicated recommends using a CNAME such as `proxy.{your app name}.com`. | ||
|
|
||
| :::note | ||
| The default location for the image used by the Replicated SDK Helm chart is `proxy.replicated.com/library/replicated-sdk-image`. When you configure a custom domain for the Replicated proxy registry, the SDK is pulled from that custom domain. For more information about the Replicated SDK, see [About the Replicated SDK](/vendor/replicated-sdk-overview). |
Contributor
There was a problem hiding this comment.
I did a little reworking to make sure the info in this note was fully captured over under Use a Custom Domain for the Replicated SDK Image in Using Custom Domains. My goal was to avoid doubling up on notes. (After looking at it again, this SDK image note didn't really need to be over here anyway)
paigecalvert
approved these changes
Jan 22, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Adds clarifying note to the custom domains documentation explaining that
/v2/tokenauthentication endpoints are expected behavior for the Docker Registry v2 API.Context
A customer was confused and concerned when they saw JWT tokens in whitelabeled registry URLs like:
This is actually harmless anonymous token behavior that is standard for Docker registries to allow pulling public images.
Changes
docs/vendor/custom-domains.mdexplaining:/v2/tokenendpoints are part of standard Docker Registry v2 APITest plan
🤖 Generated with Claude Code