-
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
Edit the Enterprise migration guide #41285
Edit the Enterprise migration guide #41285
Conversation
**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.
9740046
to
260cec4
Compare
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
🤖 Vercel preview here: https://docs-poozxvuau-goteleport.vercel.app/docs/ver/preview |
Migrating from a Teleport Enterprise (self-hosted) deployment to Teleport | ||
Enterprise (cloud-hosted) offers scalability, reliability, and ease of | ||
management. By following the steps outlined in this guide, you can transition | ||
your Teleport Enterprise (self-hosted) deployment to Teleport Enterprise | ||
(cloud-hosted) successfully while ensuring minimal disruption to your | ||
operations. |
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.
I'm probably yelling into the void and the decision has already been made above my pay grade, but I really don't like this whole "same product name with different qualifier in brackets" style. It's just clunky and awkward to read.
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.
I've opened a PR to clarify the style rule. From what I understand, it's less important that we use Teleport Enterprise (self/cloud-hosted)
than use "Teleport Enterprise" for the edition name and clarify the hosting type in some other way, outside the product name.
- 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
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
🤖 Vercel preview here: https://docs-4h7rmab37-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.
Looks good to me!
81b660c
into
oo-Migrate-from-self-hosted-to-Teleport-enterprise-cloud
* 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
* Migrate from self-hosted to Teleport-enterprise cloud * Update migrating.mdx * update guide * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Jeff Anderson <[email protected]> * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * update cloud migration doc * update cloud migration doc * Edit the Enterprise migration guide (#41285) * 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 * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * fix docs * fix docs * Apply suggestions from code review Co-authored-by: Gus Luxton <[email protected]> * Fix linter issues --------- Co-authored-by: Jeff Anderson <[email protected]> Co-authored-by: Gus Luxton <[email protected]> Co-authored-by: Paul Gottschling <[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
* 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
* 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
* 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
* Migrate from self-hosted to Teleport-enterprise cloud * Update migrating.mdx * update guide * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Jeff Anderson <[email protected]> * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * update cloud migration doc * update cloud migration doc * Edit the Enterprise migration guide (#41285) * 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 * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Fix linter issues --------- Co-authored-by: Jeff Anderson <[email protected]> Co-authored-by: Gus Luxton <[email protected]> Co-authored-by: Paul Gottschling <[email protected]>
* Migrate from self-hosted to Teleport-enterprise cloud * Update migrating.mdx * update guide * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Jeff Anderson <[email protected]> * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * update cloud migration doc * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/migrating.mdx Co-authored-by: Gus Luxton <[email protected]> * update cloud migration doc * update cloud migration doc * Edit the Enterprise migration guide (#41285) * 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 * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Update docs/pages/choose-an-edition/migrate-to-cloud.mdx Co-authored-by: Gus Luxton <[email protected]> * Fix linter issues --------- Co-authored-by: Jeff Anderson <[email protected]> Co-authored-by: Gus Luxton <[email protected]> Co-authored-by: Paul Gottschling <[email protected]>
Edit the guide for structure and style:
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: