Docker registry customisation #12590
Draft
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
0e5586f to
a484b00
Compare
a484b00 to
069cfcf
Compare
Test Results - Alternative Providers597 tests 420 ✅ 14m 54s ⏱️ Results for commit 069cfcf. |
Test Results (amd64) - Integration, Bootstrap 5 files 5 suites 2h 22m 3s ⏱️ Results for commit 069cfcf. |
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.
Motivation
Some customers work in airgapped environments, and require customisation of the Docker image registries used. This PR enables a flexible method for adding customisation to the Docker image pulling strategy.
Changes
RegistryResolverStrategyprotocol to support custom image resolvingHardCodedResolverwhich is a no-op