diff --git a/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx b/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx index 40d67a24a158b..8bde97e4c3ba4 100644 --- a/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx +++ b/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx @@ -12,6 +12,16 @@ description: How to enroll an agent into automatic updates > Automatic agent update is available starting from Teleport `13.0`. +
+ Automatic agent update is available starting from Teleport `13.0`. + Teleport Cloud does not run Teleport 13 yet. +
Teleport supports automatic agent updates for systemd-based Linux distributions using `apt` or `yum` package managers, diff --git a/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx b/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx index 89c070fd1d977..1c1e641442d60 100644 --- a/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx +++ b/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx @@ -23,6 +23,19 @@ This guide covers how to set up the automatic update infrastructure. If this is already done, or you are a Teleport Cloud user, you can directly [enroll agents into automatic updates](./enroll-agent-into-automatic-updates.mdx). + +Systemd agents enrolled into automatic updates can only install versions +present in their package repositories. As Teleport 14 won't be published to +`stable/v13`, those agents will require manual intervention to be updated to +the next major version (adding a new apt/yum repo for `stable/v14`). + +This limitation will be fixed before Teleport 14. We'll provide a rolling +update channel for agents to be able to automatically update from one major +to another. When this will happen, you will have to update the repos of the +existing agents to point to the new repo. + + + ## Requirements - Self-hosted Teleport cluster running.