Skip to content

Clarify the relationship between Kubernetes docs #34412

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

Merged
ptgott merged 1 commit into from
Nov 15, 2023
Merged

Clarify the relationship between Kubernetes docs #34412

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
13 changes: 13 additions & 0 deletions docs/pages/deploy-a-cluster/helm-deployments.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,19 @@ description: How to install and configure Teleport in Kubernetes using Helm
layout: tocless-doc
---

The `teleport-cluster` Helm chart enables you deploy and manage a self-hosted,
high-availability Teleport cluster. This chart launches the Teleport Auth
Service, Teleport Proxy Service, and the Kubernetes infrastructure required to
support these services. The guides in this section show you how to use the
`teleport-cluster` Helm chart in your environment.

You do not need to deploy the Auth Service and Proxy Service on Kubernetes in
order to protect a Kubernetes cluster with Teleport, and it is possible to
enroll a Kubernetes cluster on Teleport Cloud or by running the Teleport
Kubernetes Service on a Linux server. For instructions on enrolling a Kubernetes
cluster with Teleport, read the [Kubernetes
Access](../kubernetes-access/introduction.mdx) documentation.

## Helm deployment guides

These guides show you how to set up a full self-hosted Teleport deployment using
Expand Down
3 changes: 2 additions & 1 deletion docs/pages/deploy-a-cluster/introduction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,7 +3,8 @@ title: "Running a Production Teleport Cluster"
description: "Guides to running Teleport in production."
---

These guides show you how to run a Teleport cluster in production.
These guides show you how to run a self-hosted Teleport Enterprise or Teleport
Community Edition cluster in production.

Read our [High Availability Guide](./high-availability.mdx) for the general
principles behind deploying a scalable, fault-tolerant Teleport cluster. Once
Expand Down
5 changes: 5 additions & 0 deletions docs/pages/kubernetes-access/introduction.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,6 +12,11 @@ Teleport provides secure access to Kubernetes clusters:
cluster.
- Organizations can achieve compliance by recording `kubectl` sessions.

The guides in this section show you how to protect Kubernetes clusters with
Teleport. For instructions on self-hosting Teleport Community Edition or
Teleport Enterprise on Kubernetes, see the [Kubernetes Deployment
Guides](../deploy-a-cluster/helm-deployments.mdx).

Here is an example of using Teleport to access a Kubernetes cluster, execute
commands, and view your `kubectl` activity in Teleport's audit log:

Expand Down