Clarify supported install types for using local image registries #2905
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
replicated-ci
added
type::docs
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
paigecalvert
changed the title
paigecalvert
commented
Jan 24, 2025
| The domain of the image registry must support a Docker V2 protocol. KOTS has been tested for compatibility with the following registries: | ||
|
|
||
| ## Configure Private Registries in Online Clusters | ||
| <DockerCompatibility/> |
Contributor
Author
There was a problem hiding this comment.
^ pulled in the partial instead of linking
paigecalvert
commented
Jan 24, 2025
| Using a private registry lets you create a custom image pipeline. Any proprietary configurations that you make to the application are shared only with the groups that you allow access, such as your team or organization. You also have control over the storage location, logging messages, load balancing requests, and other configuration options. | ||
| ## Overview | ||
|
|
||
| Private registries can be used with online or air gap clusters. For kURL clusters, if the Replicated kURL installer spec includes the kURL Registry add-on, then the built-in kURL registry is used to host the application images. For more information, see [Working with the kURL Image Registry](image-registry-kurl). |
Contributor
Author
There was a problem hiding this comment.
^ removed this kurl info because it makes it sound like the registry add-on is what you always have to use for kurl, whereas you can actually configure a different registry for kurl too
paigecalvert
commented
Jan 24, 2025
| 1. Click **Save changes**. | ||
|
|
||
| 1. (Optional) Click **Stop using registry** if you want to remove the registry settings from KOTS. | ||
|
|
Contributor
Author
There was a problem hiding this comment.
^ moved this step to its own procedure since no one would want to immediately remove a registry after adding it
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.
https://deploy-preview-2905--replicated-docs-upgrade.netlify.app/enterprise/image-registry-settings