Skip to content

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

Merged
merged 5 commits into from
Jun 18, 2025

Conversation

AmberAlston
Copy link
Member

No description provided.

Copy link

netlify bot commented Jun 17, 2025

Deploy Preview for replicated-docs ready!

Name Link
🔨 Latest commit 6a669e2
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs/deploys/6851f725efa87700089708e7
😎 Deploy Preview https://deploy-preview-3321--replicated-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Copy link

netlify bot commented Jun 17, 2025

Deploy Preview for replicated-docs-upgrade ready!

Name Link
🔨 Latest commit 6a669e2
🔍 Latest deploy log https://app.netlify.com/projects/replicated-docs-upgrade/deploys/6851f725b5a65e00082d46ef
😎 Deploy Preview https://deploy-preview-3321--replicated-docs-upgrade.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

@replicated-ci replicated-ci added type::docs Improvements or additions to documentation type::feature labels Jun 17, 2025
@AmberAlston
Copy link
Member Author

@AmberAlston AmberAlston changed the title Clarify who gets access and what we recommend Replicated Registry: Clarify who gets access and what we recommend Jun 17, 2025
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
@AmberAlston AmberAlston marked this pull request as ready for review June 17, 2025 22:52
@AmberAlston AmberAlston requested a review from a team as a code owner June 17, 2025 22:52
Copy link
Contributor

@paigecalvert paigecalvert left a 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

@AmberAlston AmberAlston merged commit 33a95c8 into main Jun 18, 2025
5 checks passed
@AmberAlston AmberAlston deleted the AmberAlston-patch-1 branch June 18, 2025 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type::docs Improvements or additions to documentation type::feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants