teleport/examples/chart/teleport-cluster
2021-04-08 08:02:29 -07:00
..
.lint helm: Improve linting and add log level override (#6330) 2021-04-08 08:02:29 -07:00
templates helm: Improve linting and add log level override (#6330) 2021-04-08 08:02:29 -07:00
Chart.yaml Update Helm charts to use Teleport 6 by default (#5983) 2021-03-12 13:40:17 -08:00
README.md Getting started with Kubernetes (#5981) 2021-03-13 09:39:15 -08:00
values.yaml helm: Improve linting and add log level override (#6330) 2021-04-08 08:02:29 -07:00

Teleport Cluster

This chart sets up a single node Teleport cluster. It uses a persistent volume claim for storage. Great for getting started with Teleport.

Getting Started

Install Teleport in a separate namespace and provision a web certificate using Let's Encrypt:

$ helm install teleport/teleport-cluster \
    --set acme=true \
    --set acmeEmail=alice@example.com \
    --set clusterName=teleport.example.com\
    --create-namespace \
    --namespace=teleport-cluster \
    ./teleport-cluster/

Uninstalling

helm uninstall teleport-cluster

Arguments Reference

To use The enterprise version, set --set=enterprise=true value and create a secret license in the chart namespace.

Check https://goteleport.com/teleport/docs for more details.

Name Description Default Required
clusterName Teleport cluster name (must be an FQDN) yes
teleportVersionOverride Teleport version Current stable version no
image OSS Docker image quay.io/gravitational/teleport no
enterpriseImage Enterprise Docker image quay.io/gravitational/teleport-ent no
acme Enable ACME support in Teleport (Letsencrypt.org) false no
acmeEmail Email to use for ACME certificates no
acmeURI ACME server to use for certificates https://acme-v02.api.letsencrypt.org/directory no
labels.[name] Key-value pairs, for example --labels.env=local --labels.region=us-west-1 no
enterprise Use Teleport Enterprise false no