Consolidate updating guides #41160
Merged
Consolidate updating guides #41160
Conversation
This file contains 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
|
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-fdplvmlbp-goteleport.vercel.app/docs/ver/preview |
hugoShaka
reviewed
May 2, 2024
hugoShaka
reviewed
May 2, 2024
Comment on lines
53
to
155
| Note that the `inventory ls` command will also list `teleport-auth` and | ||
| `teleport-proxy` services. These services are managed by the Teleport team, and | ||
| updates will be performed automatically. |
There was a problem hiding this comment.
The auth and proxy services are only managed by us for cloud customers, self-hosted AU users are also responsible for updating their control plane services.
There was a problem hiding this comment.
I had intended for this to be a guide for cloud-hosted clusters, but now realize that nothing in the introduction/prerequisites mentions this. I've added a prerequisite for a cloud-hosted cluster and a link to the reference for self-hosted users.
hugoShaka
reviewed
May 2, 2024
|
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-91cx3phl8-goteleport.vercel.app/docs/ver/preview |
ptgott
force-pushed
the
paul.gottschling/40636-refactor
branch
from
87a7cfe to
62ebdc7
Compare
ptgott
requested review from
klizhentas,
russjones,
fheinecke,
camscale and
tcsc
as code owners
|
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 |
ptgott
added
no-changelog
bernardjkim
approved these changes
May 6, 2024
|
I noticed that the static install script does not configure the |
|
🤖 Vercel preview here: https://docs-r8ms17amx-goteleport.vercel.app/docs/ver/preview |
r0mant
approved these changes
Jun 24, 2024
Include a how-to guide for the fast path we want most users to move to: using cloud-hosted Teleport Enterprise and enrolling agents in automatic updates. For other use cases and edge cases, include a general Updating Reference.
- Fix step numbering. - Add cloud prerequisite and mention cloud-hosted clusters in the introduciton.
- Remove unintentionally preserved text about release channels for Teleport v14. - Add instructions for determining the Teleport version to install.
Urge users to enroll their agents in automatic upgrades per feedback from bernardjkim.
- Include self-hosted instructions in the how-to guide - Include a journalctl command to check logs - Edit the upgrading menu page and intro of the how-to guide to provide stronger language re: using automatic agent upgrades in cloud accounts.
ptgott
force-pushed
the
paul.gottschling/40636-refactor
branch
from
338bb45 to
444a616
Compare
|
🤖 Vercel preview here: https://docs-q8taotl3c-goteleport.vercel.app/docs/ver/preview |
ptgott
added a commit
that referenced
this pull request
Jun 25, 2024
Backports #41160 * Consolidate updating guides Include a how-to guide for the fast path we want most users to move to: using cloud-hosted Teleport Enterprise and enrolling agents in automatic updates. For other use cases and edge cases, include a general Updating Reference. * Respond to hugoShaka feedback - Fix step numbering. - Add cloud prerequisite and mention cloud-hosted clusters in the introduciton. * Respond to bernardjkim feedback - Remove unintentionally preserved text about release channels for Teleport v14. - Add instructions for determining the Teleport version to install. * Add an intro paragraph with a recommendation Urge users to enroll their agents in automatic upgrades per feedback from bernardjkim. * Add check for the Enterprise teleport-kube-agent Incorporates #41132 * Respond to r0mant feedback - Include self-hosted instructions in the how-to guide - Include a journalctl command to check logs - Edit the upgrading menu page and intro of the how-to guide to provide stronger language re: using automatic agent upgrades in cloud accounts. * Add `helm repo update` step * Fix linter errors * Respond to r0mant feedback
ptgott
added a commit
that referenced
this pull request
Jun 25, 2024
Backports #41160 * Consolidate updating guides Include a how-to guide for the fast path we want most users to move to: using cloud-hosted Teleport Enterprise and enrolling agents in automatic updates. For other use cases and edge cases, include a general Updating Reference. * Respond to hugoShaka feedback - Fix step numbering. - Add cloud prerequisite and mention cloud-hosted clusters in the introduciton. * Respond to bernardjkim feedback - Remove unintentionally preserved text about release channels for Teleport v14. - Add instructions for determining the Teleport version to install. * Add an intro paragraph with a recommendation Urge users to enroll their agents in automatic upgrades per feedback from bernardjkim. * Add check for the Enterprise teleport-kube-agent Incorporates #41132 * Respond to r0mant feedback - Include self-hosted instructions in the how-to guide - Include a journalctl command to check logs - Edit the upgrading menu page and intro of the how-to guide to provide stronger language re: using automatic agent upgrades in cloud accounts. * Add `helm repo update` step * Fix linter errors * Respond to r0mant feedback
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jun 25, 2024
Backports #41160 * Consolidate updating guides Include a how-to guide for the fast path we want most users to move to: using cloud-hosted Teleport Enterprise and enrolling agents in automatic updates. For other use cases and edge cases, include a general Updating Reference. * Respond to hugoShaka feedback - Fix step numbering. - Add cloud prerequisite and mention cloud-hosted clusters in the introduciton. * Respond to bernardjkim feedback - Remove unintentionally preserved text about release channels for Teleport v14. - Add instructions for determining the Teleport version to install. * Add an intro paragraph with a recommendation Urge users to enroll their agents in automatic upgrades per feedback from bernardjkim. * Add check for the Enterprise teleport-kube-agent Incorporates #41132 * Respond to r0mant feedback - Include self-hosted instructions in the how-to guide - Include a journalctl command to check logs - Edit the upgrading menu page and intro of the how-to guide to provide stronger language re: using automatic agent upgrades in cloud accounts. * Add `helm repo update` step * Fix linter errors * Respond to r0mant feedback
github-merge-queue bot
pushed a commit
that referenced
this pull request
Jun 25, 2024
Backports #41160 * Consolidate updating guides Include a how-to guide for the fast path we want most users to move to: using cloud-hosted Teleport Enterprise and enrolling agents in automatic updates. For other use cases and edge cases, include a general Updating Reference. * Respond to hugoShaka feedback - Fix step numbering. - Add cloud prerequisite and mention cloud-hosted clusters in the introduciton. * Respond to bernardjkim feedback - Remove unintentionally preserved text about release channels for Teleport v14. - Add instructions for determining the Teleport version to install. * Add an intro paragraph with a recommendation Urge users to enroll their agents in automatic upgrades per feedback from bernardjkim. * Add check for the Enterprise teleport-kube-agent Incorporates #41132 * Respond to r0mant feedback - Include self-hosted instructions in the how-to guide - Include a journalctl command to check logs - Edit the upgrading menu page and intro of the how-to guide to provide stronger language re: using automatic agent upgrades in cloud accounts. * Add `helm repo update` step * Fix linter errors * Respond to r0mant feedback
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.
Include a how-to guide for the fast path we want most users to move to: using cloud-hosted Teleport Enterprise and enrolling agents in automatic updates. For other use cases and edge cases, include a general Updating Reference.