-
Notifications
You must be signed in to change notification settings - Fork 28
Replicated Registry: Clarify who gets access and what we recommend #3321
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
✅ 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. |
Related internal slack convo that led to this PR https://replicated.slack.com/archives/C036BTS7JCE/p1750093170197049?thread_ts=1750058750.221459&cid=C036BTS7JCE |
the old title "Use the Replicated Registry for KOTS Installations" sounded too much like we were telling you to use it, which conflicted with the advice note below
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@AmberAlston made a few edits to distribute that info that was in the note more in the Overview and Limitations sections instead:
- update overview to explain we mostly just recommend the registry for testing purposes, and you should use the proxy for all production releases
- added a limitation about how it's not available for helm installations
- also updated the topic sentence to add a "this page only applies to kots" sentence
No description provided.