Repository navigation
docs: describe registry_blob and registry_tag backend options - #691
Open
Rohit-Singh-01 wants to merge 1 commit into
Open
Rohit-Singh-01 wants to merge 1 commit into
Rohit-Singh-01 wants to merge 1 commit into
Conversation
Add details about read-only registry backends and their options.
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
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.
Related to #268 (does not close it).
The "Read-Only Registry Backend" section of docs/CONFIGURATION.md only showed a local-testing example. This adds a short explanation of the two registry backends, written from lib/backend/registrybackend:
registry_blobandregistry_tag: which registry endpoints each one calls, and that both are read-only.address,timeout(default 60s),security.tls.client,security.basic,security.credsStore,security.enableHTTPFallback.Docs only, 16 added lines, nothing removed. I read the code to check each statement. I did not cover the multiple-registries question from #268 (the
gcr/.*namespace case), since I am not sure what behavior is intended there. Happy to adjust anything.