opensource/teleport
3
0
Fork 0
mirror of https://github.com/gravitational/teleport.git synced 2026-09-19 01:58:44 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: remove references to unsupported versions (#63741)

Browse Source
This commit is contained in:
Steven Martin
2026-02-12 00:57:38 +00:00
committed by GitHub
parent 565c665a04
commit 85cf5e8a27
6 changed files with 2 additions and 18 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/pages/connect-your-client/includes/connect-my-computer-prerequisites.mdx
+1 -1
View File
@@ -1,5 +1,5 @@
- A macOS or Linux device.
- Teleport Connect v14.1+, on the same major version or one version behind the Teleport Proxy
- Teleport Connect, on the same major version or one version behind the Teleport Proxy
Service version. See [version compatibility](../../upcoming-releases.mdx#teleport).
- A local Teleport user: you must authenticate using credentials or passwordless login, and not with
SSO.
docs/pages/enroll-resources/database-access/enrollment/aws/aws-cross-account.mdx
-2
View File
@@ -14,8 +14,6 @@ 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.
docs/pages/enroll-resources/database-access/enrollment/azure/azure-postgres-mysql.mdx
-3
View File
@@ -11,9 +11,6 @@ tags:
(!docs/pages/includes/database-access/db-introduction.mdx dbType="Azure PostgreSQL or MySQL" dbConfigure="with Microsoft Entra ID-based authentication"!)
Database auto-discovery for Azure PostgreSQL/MySQL flexible servers is available starting from
Teleport `12.0`.
## How it works
The Teleport Database Service proxies traffic between Teleport users and Azure
docs/pages/reference/architecture/tls-routing.mdx
-3
View File
@@ -18,9 +18,6 @@ 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:
docs/pages/reference/deployment/backends.mdx
-5
View File
@@ -302,9 +302,6 @@ tctl get <Var name="resource" /> --format=json | awk '{ total += length($0) } EN
## PostgreSQL
PostgreSQL cluster state and audit log storage is available starting from
Teleport `13.3`.
Teleport can use [PostgreSQL](https://www.postgresql.org/) as a storage backend
to achieve high availability. You must take steps to protect access to
PostgreSQL in this configuration because that is where Teleport secrets like
@@ -1080,8 +1077,6 @@ Config option priority is applied in the following order:
## Athena
The Athena audit log backend is available starting from Teleport v14.0.
If you are running Teleport on AWS, you can use an
[Athena](https://aws.amazon.com/athena/)-based audit log system that manages
[Parquet files](https://parquet.apache.org/) stored on
docs/pages/zero-trust-access/management/external-audit-storage.mdx
+1 -4
View File
@@ -23,10 +23,7 @@ audit events right where they are stored.
External Audit Storage is based on Teleport's
[Athena](../../reference/deployment/backends.mdx#athena) backend for audit events and the
[S3](../../reference/deployment/backends.mdx#s3-session-recordings) backend for session recordings. It is only
available on Teleport Enterprise Cloud clusters running Teleport v14.2.1 or
above.
[S3](../../reference/deployment/backends.mdx#s3-session-recordings) backend for session recordings.
## Prerequisites