Secure and Simplify Helm RBAC and Audit with Teleport

Teleport provides two main Helm charts for deploying and managing Teleport in Kubernetes environments:

• teleport-cluster: This is the primary Helm chart for deploying a full Teleport cluster. It sets up the following components 1:The teleport-cluster chart is designed to deploy a self-hosted, high-availability Teleport cluster 2.
  • Teleport Auth Service
  • Teleport Proxy Service
  • Kubernetes Access (kubernetes_service)
• teleport-kube-agent: This chart is used to configure a Teleport agent that runs in a remote Kubernetes cluster to provide access to resources in your infrastructure 3.

These charts allow you to deploy Teleport in various configurations and environments. The teleport-cluster chart, in particular, can be deployed in different modes such as standalone, AWS, GCP, Azure, and scratch, depending on your infrastructure and requirements 1.

It's worth noting that Teleport doesn't currently provide a Helm chart for deploying the Windows Desktop Service. This was confirmed in a GitHub discussion where a user asked about deploying this service using the teleport-cluster chart 4.

When using these Helm charts, you can customize the Teleport configuration by providing your own values file, allowing you to tailor the deployment to your specific needs 5.