reduce headless EC install docs confusion #3409
Merged
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
✅ 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. |
replicated-ci
added
type::docs
paigecalvert
approved these changes
Jul 29, 2025
Contributor
|
Thank you this makes sense! |
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.
Removed the procedure partial which was causing confusion on this page with both the mention of existing cluster installs and the reference to the kots cli procedure which vendors then expected to work with EC installs.
I don't think it's really necessary to say how to scrape the UI for config on this page (only used to recreate an existing install). And I'd like to see that improved in EC so it's not UI-based for a headless install. If we find we do need to add that UI procedure back before then, we'll want to add just that relevant part back vs the whole partial previously there.
related internal slack thread about changing this page: https://replicated.slack.com/archives/C0499EGNPNY/p1753456745585659