Skip to content
Merged
Changes from all commits
Commits
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
20 changes: 14 additions & 6 deletions docs/pages/connect-your-client/teleport-connect.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -96,12 +96,20 @@ reflected in both the tab title and the status bar.
1. Select the Kubes section.
1. Look for the cluster you wish to connect to and click the Connect button to the right.

A new local terminal tab will open which is preconfigured with the `$KUBECONFIG` environment variable
pointing to a configuration for the specified cluster. Any tools that you have installed that respect
the `$KUBECONFIG` environment variable (`kubectl`, `helm`, etc.) will work without additional configuration.
To identify the path to this config for use in other tools, run `echo $KUBECONFIG`.

Alternatively, you can look for the cluster in the search bar and press `Enter` to connect to it.
Alternatively, you can look for the cluster in the search bar and press `Enter`
to connect to it.

A new local terminal tab will open which is preconfigured with the `KUBECONFIG`
environment variable pointing to a configuration for the specified cluster. Any
tools that respect the `KUBECONFIG` environment variable (`kubectl`, `helm`,
etc.) will work without additional configuration. To identify the path to this
config for use in other tools, inspect the value of the `KUBECONFIG`
environment variable.

The value of the `KUBECONFIG` environment variable will persist between app
restarts, but this configuration file will not be available or usable when the
Kubernetes cluster is removed from the connection list in the top left, or when
Teleport Connect is closed.

## Connecting to a database

Expand Down