Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[v14] docs: remove old version references #46966

Merged
merged 4 commits into from
Sep 30, 2024
Merged

[v14] docs: remove old version references #46966

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
1e4114e
docs: remove old version references
Sep 26, 2024
e79b921
docs: revert config version
Sep 26, 2024
62706f2
docs: update verbiage
stevenGravy Sep 28, 2024
5473221
docs: remove version 13 reference on joining
stevenGravy Sep 28, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/pages/connect-your-client/tsh.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -646,8 +646,8 @@ scp"` and use the familiar syntax:
$ scp -P 61122 -r files root@node:/path/to/dest
```

Starting from Teleport 9 the SCP and SFTP protocols are both supported by Server
Access. OpenSSH `scp` or `sftp` commands can both be used in place of `tsh scp`
Teleport supports both the SCP and SFTP protocols.
OpenSSH `scp` or `sftp` commands can both be used in place of `tsh scp`
if desired.

## Sharing sessions
Expand Down
7 changes: 3 additions & 4 deletions docs/pages/enroll-resources/agents/join-services-to-your-cluster/azure.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,9 @@ This guide will explain how to use the **Azure join method** to configure
Teleport instances to join your Teleport cluster without sharing any secrets
when they are running in an Azure Virtual Machine.

The Azure join method is available in Teleport 12.1+. It is available to any
Teleport process running in an Azure Virtual Machine. Support for joining a
cluster with the Proxy Service behind a layer 7 load balancer or reverse proxy
is available in Teleport 13.0+.
The Azure join method is available to any Teleport process running in an
Azure Virtual Machine. Support for joining a cluster with the Proxy Service
behind a layer 7 load balancer or reverse proxy is available in Teleport 13.0+.

For other methods of joining a Teleport process to a cluster, see [Joining
Teleport Services to a Cluster](../join-services-to-your-cluster.mdx).
Expand Down
2 changes: 1 addition & 1 deletion docs/pages/enroll-resources/agents/join-services-to-your-cluster/kubernetes.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ joining service to run in the same Kubernetes cluster as the Auth Service.

</Notice>

The Kubernetes join method is available in self-hosted versions of Teleport 12+.
The Kubernetes join method is available in self-hosted versions of Teleport.
It supports joining any Teleport service running in the same Kubernetes cluster
as the Auth Service.

Expand Down
2 changes: 0 additions & 2 deletions docs/pages/enroll-resources/database-access/guides/mongodb-self-hosted.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -227,8 +227,6 @@ $ tsh db connect --db-user=alice --db-name dev example-mongo
<Admonition type="note" title="Supported MongoDB clients">
Either the `mongosh` or `mongo` command-line clients should be available in `PATH` in order to be
able to connect. The Database Service attempts to run `mongosh` first and, if `mongosh` is not in `PATH`, runs `mongo`.

Teleport 9.0 added support for `mongosh` and made it the default Mongo DB client.
</Admonition>

To log out of the database and remove credentials:
Expand Down
2 changes: 1 addition & 1 deletion docs/pages/enroll-resources/machine-id/faq.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@ runs.

## Can Machine ID be used with Trusted Clusters ?

From Teleport 12.2, you can use Machine ID for SSH Access in trusted leaf clusters.
You can use Machine ID for SSH access in trusted leaf clusters.

We currently do not support access to applications, databases, or Kubernetes
clusters in leaf clusters.
Expand Down
12 changes: 3 additions & 9 deletions docs/pages/reference/join-methods.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -262,8 +262,6 @@ The IAM join method is available to any Teleport process running anywhere with a
such as an EC2 instance with an attached IAM role. No specific permissions or IAM policy is required: an
IAM role with no attached policies is sufficient. No IAM credentials are required on the Teleport Auth Service.

Support for joining a cluster with the Proxy Service behind a layer 7 load balancer or reverse proxy is available in Teleport 13.0+.

This is the recommended method to join workload running on AWS.

(!docs/pages/includes/provision-token/iam-spec.mdx!)
Expand Down Expand Up @@ -299,10 +297,9 @@ method](#aws-iam-role-iam) or [ephemeral secret tokens](#ephemeral-tokens).

### Azure managed identity: `azure`

The Azure join method is available in Teleport 12.1+. It is available to any
Teleport process running in an Azure Virtual Machine. Support for joining a
cluster with the Proxy Service behind a layer 7 load balancer or reverse proxy
is available in Teleport 13.0+.
The Azure join method is available to any Teleport process running in an
Azure Virtual Machine. Support for joining a cluster with the Proxy Service
behind a layer 7 load balancer or reverse proxy is available in Teleport 13.0+.

(!docs/pages/includes/provision-token/azure-spec.mdx!)

Expand Down Expand Up @@ -383,9 +380,6 @@ clusters in Kubernetes.
This method should be preferred when available as tokens are revoked as soon as
the pod enters the `Terminated` state.

The Kubernetes in-cluster join method is available in self-hosted versions of
Teleport 12+.

(!docs/pages/includes/provision-token/kubernetes-in-cluster-spec.mdx!)

<Admonition type="note" title="See Also">
Expand Down
Loading