docs: update k8s instrs on auto upgrades #41132
Closed
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
stevenGravy
added
backport/branch/v14
no-changelog
|
🤖 Vercel preview here: https://docs-nkovycda7-goteleport.vercel.app/docs/ver/preview |
|
🤖 Vercel preview here: https://docs-m1ppe1ecp-goteleport.vercel.app/docs/ver/preview |
|
Hi @stevenGravy, Bernard and I are working on refactoring the upgrading docs (#40636). I've got a PR that I'm working on today. If that PR looks good, it might make sense to rebase this change over that one. I can also look into incorporating this fix into that PR! |
Yes please go ahead and apply these to the one you're working on. Feel free to close this one once you've done that. |
|
Being addressed in #41160 |
ptgott
added a commit
that referenced
this pull request
May 15, 2024
ptgott
added a commit
that referenced
this pull request
May 24, 2024
ptgott
added a commit
that referenced
this pull request
Jun 4, 2024
ptgott
added a commit
that referenced
this pull request
Jun 11, 2024
ptgott
added a commit
that referenced
this pull request
Jun 17, 2024
ptgott
added a commit
that referenced
this pull request
Jun 21, 2024
ptgott
added a commit
that referenced
this pull request
Jun 24, 2024
bikramtuladhar
pushed a commit
to cloudnepal/teleport
that referenced
this pull request
Jun 24, 2024
* 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 gravitational#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
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.
auto upgrade for k8s did not indicate to set enterprise value.