diff --git a/docs/pages/ai-assist.mdx b/docs/pages/ai-assist.mdx index 989e4590e54e8..4c9805f7145e4 100644 --- a/docs/pages/ai-assist.mdx +++ b/docs/pages/ai-assist.mdx @@ -11,17 +11,6 @@ This guide will help you understand how to set up and use Teleport Assist, an AI-powered assistant that helps you run commands, debug issues and navigate your infrastructure. -
- -Teleport Assist is available starting from Teleport `v12.4` for Teleport -Community Edition. - -
- ### Architecture diagram ![Teleport Assist Architecture](../img/assist/architecture-diagram.png) @@ -34,8 +23,8 @@ Community Edition. Before you get started with Teleport Assist, make sure you have the following: -- A running Teleport Community Edition cluster. For details on how to set this - up, see our [Getting Started](./index.mdx) guide. +- A running Teleport Community Edition cluster, v12.4 or higher. For details on + how to set this up, see our [Getting Started](./index.mdx) guide. - **OpenAI Account**: You will need an active OpenAI account with GPT-4 API access as Teleport Assist relies on OpenAI services. diff --git a/docs/pages/architecture/tls-routing.mdx b/docs/pages/architecture/tls-routing.mdx index b8a8708bb7b42..334c884b282c7 100644 --- a/docs/pages/architecture/tls-routing.mdx +++ b/docs/pages/architecture/tls-routing.mdx @@ -3,17 +3,6 @@ title: TLS Routing description: How Teleport implements a single-port setup with TLS routing --- -
- Support for TLS Routing behind layer 7 (HTTP/HTTPS) load balancers and reverse - proxies is available starting from Teleport `13.0`. -
- In TLS routing mode [Teleport proxy](./proxy.mdx) multiplexes all client connections on a single TLS port. @@ -26,6 +15,9 @@ To implement TLS routing, Teleport uses SNI ([Server Name Indication](https://en and ALPN ([Application-Level Protocol Negotiation](https://en.wikipedia.org/wiki/Application-Layer_Protocol_Negotiation)) TLS extensions. +Support for TLS Routing behind layer 7 (HTTP/HTTPS) load balancers and reverse +proxies is available starting from Teleport `13.0`. + ## How it works The Teleport Proxy Service listens for all client connections on its `web_listen_addr` by default: diff --git a/docs/pages/choose-an-edition/teleport-enterprise/gcp-kms.mdx b/docs/pages/choose-an-edition/teleport-enterprise/gcp-kms.mdx index eebcc410cfcda..5179fccb974fd 100644 --- a/docs/pages/choose-an-edition/teleport-enterprise/gcp-kms.mdx +++ b/docs/pages/choose-an-edition/teleport-enterprise/gcp-kms.mdx @@ -8,18 +8,6 @@ This guide will show you how to set up your Teleport Cluster to use the Google Cloud Key Management Service (KMS) to store and handle the CA private key material used to sign all certificates issued by your Teleport cluster. -
- -The features documented on this page are available in Teleport `11.1.0` and higher. - -
- Teleport generates private key material for its internal Certificate Authorities (CAs) during the first Auth Server's initial startup. These CAs are used to sign all certificates issued to clients and hosts in the @@ -42,6 +30,9 @@ learn more. ## Prerequisites +The features documented on this page are available in Teleport `11.1.0` and +higher. + (!docs/pages/includes/commercial-prereqs-tabs.mdx!) - (!docs/pages/includes/tctl.mdx!) diff --git a/docs/pages/database-access/auto-user-provisioning/aws-redshift.mdx b/docs/pages/database-access/auto-user-provisioning/aws-redshift.mdx index 89dfc2a9f917f..47819b3aa45d7 100644 --- a/docs/pages/database-access/auto-user-provisioning/aws-redshift.mdx +++ b/docs/pages/database-access/auto-user-provisioning/aws-redshift.mdx @@ -3,22 +3,12 @@ title: AWS Redshift Automatic User Provisioning description: Configure automatic user provisioning for AWS Redshift. --- -
- Automatic user provisioning for AWS Redshift is available starting from - Teleport 14.2. -
- (!docs/pages/includes/database-access/auto-user-provisioning/intro.mdx!) ## Prerequisites -- Teleport cluster with a configured [AWS Redshift](../guides/postgres-redshift.mdx) database. +- Teleport cluster v14.2 or higher with a configured [AWS + Redshift](../guides/postgres-redshift.mdx) database. - Ability to connect to and create user accounts in the target database. diff --git a/docs/pages/database-access/auto-user-provisioning/mariadb.mdx b/docs/pages/database-access/auto-user-provisioning/mariadb.mdx index 64a7ef99bfafe..74c6bd5e881fe 100644 --- a/docs/pages/database-access/auto-user-provisioning/mariadb.mdx +++ b/docs/pages/database-access/auto-user-provisioning/mariadb.mdx @@ -3,23 +3,13 @@ title: MariaDB Automatic User Provisioning description: Configure automatic user provisioning for MariaDB. --- -
- Automatic user provisioning for MariaDB is available starting from Teleport - 14.2. -
- (!docs/pages/includes/database-access/auto-user-provisioning/intro.mdx!) ## Prerequisites -- Teleport cluster with a configured [self-hosted MariaDB](../guides/mysql-self-hosted.mdx) - or [RDS MariaDB](../guides/rds.mdx) database. +- Teleport cluster v14.2 or higher with a configured [self-hosted + MariaDB](../guides/mysql-self-hosted.mdx) or [RDS MariaDB](../guides/rds.mdx) + database. - Ability to connect to and create user accounts in the target database. diff --git a/docs/pages/database-access/auto-user-provisioning/mysql.mdx b/docs/pages/database-access/auto-user-provisioning/mysql.mdx index 8b82aa08fdba1..f0a7291879ec2 100644 --- a/docs/pages/database-access/auto-user-provisioning/mysql.mdx +++ b/docs/pages/database-access/auto-user-provisioning/mysql.mdx @@ -3,21 +3,11 @@ title: MySQL Automatic User Provisioning description: Configure automatic user provisioning for MySQL. --- -
- Automatic user provisioning for MySQL is available starting from Teleport - 14.1. -
- ## Prerequisites -- Teleport cluster with a configured [self-hosted MySQL](../guides/mysql-self-hosted.mdx) - or [RDS MySQL](../guides/rds.mdx) database. +- Teleport cluster v14.1 or higher with a configured [self-hosted + MySQL](../guides/mysql-self-hosted.mdx) or [RDS MySQL](../guides/rds.mdx) + database. - Ability to connect to and create user accounts in the target database. diff --git a/docs/pages/database-access/auto-user-provisioning/postgres.mdx b/docs/pages/database-access/auto-user-provisioning/postgres.mdx index ab04c144f815e..103ca0659df0d 100644 --- a/docs/pages/database-access/auto-user-provisioning/postgres.mdx +++ b/docs/pages/database-access/auto-user-provisioning/postgres.mdx @@ -3,23 +3,13 @@ title: PostgreSQL Automatic User Provisioning description: Configure automatic user provisioning for PostgreSQL. --- -
- Automatic user provisioning for PostgreSQL is available starting from - Teleport 13.1. -
- (!docs/pages/includes/database-access/auto-user-provisioning/intro.mdx!) ## Prerequisites -- Teleport cluster with a configured [self-hosted PostgreSQL](../guides/postgres-self-hosted.mdx) - or [RDS PostgreSQL](../guides/rds.mdx) database. +- Teleport cluster v13.1 or above with a configured [self-hosted + PostgreSQL](../guides/postgres-self-hosted.mdx) or [RDS + PostgreSQL](../guides/rds.mdx) database. - Ability to connect to and create user accounts in the target database. ## Step 1/3. Configure database admin diff --git a/docs/pages/database-access/guides/aws-cassandra-keyspaces.mdx b/docs/pages/database-access/guides/aws-cassandra-keyspaces.mdx index 3bf225230eb27..a74abd6f72024 100644 --- a/docs/pages/database-access/guides/aws-cassandra-keyspaces.mdx +++ b/docs/pages/database-access/guides/aws-cassandra-keyspaces.mdx @@ -3,16 +3,6 @@ title: Database Access with AWS Keyspaces (Apache Cassandra) description: How to configure Teleport database access with AWS Keyspaces (Apache Cassandra) --- -
- Database access for AWS Keyspaces (Apache Cassandra) is available starting from Teleport `v11.0`. -
- (!docs/pages/includes/database-access/db-introduction.mdx dbType="AWS Keyspaces (Apache Cassandra)" dbConfigure="AWS Keyspaces database with IAM authentication" dbName="AWS Keyspaces" !) @@ -27,6 +17,9 @@ description: How to configure Teleport database access with AWS Keyspaces (Apach ## Prerequisites +Database access for AWS Keyspaces (Apache Cassandra) is available starting from +Teleport `v11.0`. + (!docs/pages/includes/edition-prereqs-tabs.mdx!) - AWS Account with AWS Keyspaces database and permissions to create and attach IAM policies diff --git a/docs/pages/database-access/guides/aws-cross-account.mdx b/docs/pages/database-access/guides/aws-cross-account.mdx index b9c9045f28bbb..fd8d766c9fc0e 100644 --- a/docs/pages/database-access/guides/aws-cross-account.mdx +++ b/docs/pages/database-access/guides/aws-cross-account.mdx @@ -3,20 +3,12 @@ title: AWS Cross-Account Database Access description: How to connect AWS databases in external AWS accounts to Teleport. --- -
- AWS cross-account database access is available starting from Teleport `13.0`. -
- You can deploy the Teleport Database Service with AWS IAM credentials in one AWS account and use an AWS IAM role to grant Teleport access to databases in another AWS account. +AWS cross-account database access is available starting from Teleport `13.0`. + When the Teleport Database Service needs to discover, configure, or retrieve short-lived authentication tokens for AWS databases, it uses credentials for an AWS IAM identity to make requests to the AWS API. diff --git a/docs/pages/database-access/guides/azure-sql-server-ad.mdx b/docs/pages/database-access/guides/azure-sql-server-ad.mdx index 10fe4bb799831..619b1a0053114 100644 --- a/docs/pages/database-access/guides/azure-sql-server-ad.mdx +++ b/docs/pages/database-access/guides/azure-sql-server-ad.mdx @@ -3,17 +3,6 @@ title: Database Access with SQL Server on Azure description: How to configure Teleport database access with Azure SQL Server using Azure Active Directory authentication. --- -
- Database access for Azure SQL Server with Azure Active Directory authentication - is available starting from Teleport `11.0`. -
- (!docs/pages/includes/database-access/db-introduction.mdx dbType="Azure SQL Server" dbConfigure="Azure SQL Server using Azure Active Directory authentication" dbName="Azure SQL Server" !) @@ -28,6 +17,9 @@ description: How to configure Teleport database access with Azure SQL Server usi ## Prerequisites +Database access for Azure SQL Server with Azure Active Directory authentication +is available starting from Teleport `11.0`. + (!docs/pages/includes/edition-prereqs-tabs.mdx!) - SQL Server running on Azure. diff --git a/docs/pages/database-access/guides/cassandra-self-hosted.mdx b/docs/pages/database-access/guides/cassandra-self-hosted.mdx index 3fe4436688475..598380a9a12f7 100644 --- a/docs/pages/database-access/guides/cassandra-self-hosted.mdx +++ b/docs/pages/database-access/guides/cassandra-self-hosted.mdx @@ -3,16 +3,6 @@ title: Database Access with Cassandra and ScyllaDB description: How to configure Teleport database access with Cassandra and ScyllaDB. --- -
- Database access for Cassandra & ScyllaDB is available starting from Teleport `v11.0`. -
- (!docs/pages/includes/database-access/db-introduction.mdx dbType="Cassandra or ScyllaDB" dbConfigure="Cassandra or ScyllaDB with mutual TLS authentication" dbName="Cassandra or ScyllaDB" !) @@ -27,6 +17,9 @@ description: How to configure Teleport database access with Cassandra and Scylla ## Prerequisites +Database access for Cassandra & ScyllaDB is available starting from Teleport +`v11.0`. + (!docs/pages/includes/edition-prereqs-tabs.mdx!) - Self-hosted Cassandra or ScyllaDB instance. diff --git a/docs/pages/includes/machine-id/v2-config-warning.mdx b/docs/pages/includes/machine-id/v2-config-warning.mdx index fb9a3645b9c1a..31e6aa3596957 100644 --- a/docs/pages/includes/machine-id/v2-config-warning.mdx +++ b/docs/pages/includes/machine-id/v2-config-warning.mdx @@ -1,9 +1,3 @@ -
- This version of the guide uses the v2 `tbot` configuration. This version is only - supported by Teleport 14 and beyond. Change the selected version of the - documentation to view the guide for previous Teleport versions. -
\ No newline at end of file +This version of the guide uses the v2 `tbot` configuration. This version is only +supported by Teleport 14 and beyond. Change the selected version of the +documentation to view the guide for previous Teleport versions. diff --git a/docs/pages/machine-id/deployment/gitlab.mdx b/docs/pages/machine-id/deployment/gitlab.mdx index 605af52cfba81..3bf28d1ae78b8 100644 --- a/docs/pages/machine-id/deployment/gitlab.mdx +++ b/docs/pages/machine-id/deployment/gitlab.mdx @@ -3,16 +3,6 @@ title: Deploying Machine ID on GitLab CI description: How to install and configure Machine ID on GitLab CI --- -
- Machine ID for GitLab is available starting from Teleport `v12.2`. -
- In this guide, you will use Teleport Machine ID to allow a GitLab pipeline to securely connect to a Teleport SSH node without the need for long-lived secrets. @@ -27,6 +17,8 @@ control. ## Prerequisites +Machine ID for GitLab is available starting from Teleport `v12.2`. + (!docs/pages/includes/edition-prereqs-tabs.mdx!) - (!docs/pages/includes/tctl.mdx!) 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 1dc745de18625..ee01f6ac22733 100644 --- a/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx +++ b/docs/pages/management/operations/enroll-agent-into-automatic-updates.mdx @@ -3,14 +3,6 @@ title: Enroll an agent into automatic updates description: How to enroll an agent into automatic updates --- -
- Automatic agent update is available starting from Teleport `13.0`. -
- Teleport supports automatic agent updates for systemd-based Linux distributions using `apt`, `yum`, or `zypper` package managers, and Kubernetes clusters. The [automatic updates architecture @@ -22,6 +14,8 @@ updates. ## Requirements +Automatic agent update is available starting from Teleport `13.0`. + - A Teleport Enterprise agent, either: 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 5a5c8198d1a4e..3f431cfaaef43 100644 --- a/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx +++ b/docs/pages/management/operations/self-hosted-automatic-agent-updates.mdx @@ -3,16 +3,6 @@ title: Setting up self-hosted automatic agent updates description: How to setup automatic agent update for self-hosted Teleport --- -
- Automatic agent update is available starting from Teleport `13.0`. -
- Teleport supports automatic agent updates for systemd-based Linux distributions using `apt`, `yum`, and `zypper` package managers, and Kubernetes clusters. The [automatic updates architecture @@ -35,7 +25,7 @@ Teleport v13.3.2 forward, including future major releases. ## Requirements -- Self-hosted Teleport cluster running. +- Self-hosted Teleport cluster v13.0 or higher. - `tctl` execution on the auth machine or a role allowing verbs `create`, `read`, `update`, `delete` on the resource `cluster_maintenance_config`. - Either: diff --git a/docs/pages/management/operations/tls-routing.mdx b/docs/pages/management/operations/tls-routing.mdx index 92044655b0db0..3fa9eb5af8aed 100644 --- a/docs/pages/management/operations/tls-routing.mdx +++ b/docs/pages/management/operations/tls-routing.mdx @@ -3,17 +3,6 @@ title: TLS Routing Migration description: How to upgrade an existing Teleport cluster to single-port TLS routing mode --- -
- Support for TLS routing behind layer 7 (HTTP/HTTPS) load balancers and reverse - proxies is available starting from Teleport `13.0`. -
- In TLS routing mode, all Teleport client connections are wrapped in TLS and multiplexed on one Teleport Proxy Service port. @@ -31,22 +20,23 @@ Upgrading Teleport will not enable TLS routing by default and the cluster will keep working in backwards-compatibility mode. Follow this guide to migrate your Teleport installation to TLS routing. - - -Teleport Team manages the Proxy Service's networking configuration for you. -Get started with a [free trial](https://goteleport.com/signup?t_source=docs) of +Teleport Team manages the Proxy Service's networking configuration for you. Get +started with a [free trial](https://goteleport.com/signup?t_source=docs) of Teleport Team. -To see which ports and networking settings the Proxy Service is configured to -use in your Teleport Cloud tenant, run the following command, replacing -`mytenant.teleport.sh` with your tenant address: +## Prerequisites + +Support for TLS routing behind layer 7 (HTTP/HTTPS) load balancers and reverse +proxies is available starting from Teleport `13.0`. + +If you use Teleport Cloud, see which ports and networking settings the Proxy +Service is configured to use in your Teleport Cloud tenant. Run the following +command, replacing `mytenant.teleport.sh` with your tenant address: ```code $ curl https://mytenant.teleport.sh/webapi/ping | jq '.proxy' ``` - - ## Step 1/7. Upgrade Teleport Download Teleport from the [downloads page](https://goteleport.com/download) or diff --git a/docs/pages/reference/backends.mdx b/docs/pages/reference/backends.mdx index 4df305d16ae2c..31f7e7cbbf3a6 100644 --- a/docs/pages/reference/backends.mdx +++ b/docs/pages/reference/backends.mdx @@ -174,13 +174,8 @@ teleport: ## PostgreSQL -
- The PostgreSQL cluster state and audit log storage is available starting from Teleport `13.3`. -
+PostgreSQL cluster state and audit log storage is available starting from +Teleport `13.3`. - Azure Blob Storage for session storage is available starting from Teleport `13.3`. - +Azure Blob Storage for session storage is available starting from Teleport +`13.3`.