-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Migrate from self-hosted to Teleport-enterprise cloud #40172
Migrate from self-hosted to Teleport-enterprise cloud #40172
Conversation
🤖 Vercel preview here: https://docs-pbczgg62a-goteleport.vercel.app/docs/ver/preview |
🤖 Vercel preview here: https://docs-mhvlm5inf-goteleport.vercel.app/docs/ver/preview |
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.
Great work! There's lots of little nits here and it seems like a lot, but I promise I'm saving you time when this goes to docs review!
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
* Edit the Enterprise migration guide **Edit the guide for structure and style:** - Use title case in the title. - Wrap lines at 80 chars. - Begin H2s with "Step n/d" - Move the Conclusion text to the intro. How-to guides do not include conclusions in our docs, and this information is valuable at the start of the guide. - Use numbered steps for instructions. - Use relative file paths for links. - Minor style edits. **Remove the "Verify connectivity" step:** This repeats instructions from the step to deploy a cloud-hosted cluster. **Add a note on migrating plugins and Machine ID Bots:** the guide only includes instructions for migrating agents in the section on migrating services. This change suggests linking to docs on migrating plugins and Bots. **Edit the navigation:** - Add a link to the navigation sidebar. - Edit the "Choose a Teleport Edition" intro page to (a) imply that cloud-hosted is the recommended solution and (b) link to the migration guide. * Respond to webvictim feedback - Reduce the overuse of `Teleport Enterprise (cloud|self-hosted)`. - Move the note re: trusted clusters to the Prerequisites. - Mention the `--auth` flag in `tsh login` commands. - Fix typo. - Add a note about the `proxy_server` field
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
Co-authored-by: Gus Luxton <[email protected]>
76090fd
to
d899a18
Compare
🤖 Vercel preview here: https://docs-2mvfx4a8m-goteleport.vercel.app/docs/ver/preview |
Documentation guide for Migrating from a self-hosted Teleport deployment to the Teleport Cloud