Documentation: using custom connectors #9833
Merged
Conversation
This file contains 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
alafanechere
added
area/documentation
marcosmarxm
reviewed
Jan 27, 2022
Co-authored-by: Marcos Marx <marcosmarxm@users.noreply.github.com>
marcosmarxm
approved these changes
Jan 28, 2022
Comment on lines
+27
to
+28
| ## 2. Authenticate to your private Docker registry | ||
| To push and pull images to your private Docker registry, you need to authenticate to it: |
There was a problem hiding this comment.
Maybe use Private Container Registry?
There was a problem hiding this comment.
I think the common naming is Docker registry, and in our case we want it to be private 😄 . Container registry is a cloud service name.
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.
What
Add documentation about how to use custom connectors and a private docker registry in the Operator Guides section.
This is a question often received by the USE team on slack.
How
Explain how to: