mirror of
https://github.com/gravitational/teleport.git
synced 2026-10-16 16:39:53 +08:00
d2a656ef3f
* Allow for probe timeouts to be configurable When setting up a new Teleport enterprise cluster on GCP, I noticed that I needed to set the probe timeouts to get the cluster to be healthy. This seems to be a known issue (https://github.com/kubernetes/kubernetes/issues/89898). As a "stopgap", I've updated the helm chart to allow for end users to be able to configure these timeouts. * Update configuration option name and add documentation * Update docs/pages/kubernetes-access/helm/reference.mdx Co-authored-by: Gus Luxton <gus@goteleport.com> * Add tests for probeTimeoutSeconds * Add probeTimeoutSeconds to required values * Add probeTimeoutSeconds to teleport-kube-agent * Add tests for probeTimeoutSeconds to teleport-kube-agent * Add probeTimeoutSeconds to teleport-kube-agent reference Co-authored-by: Hunter Madison <hunter.madison@instana.com> Co-authored-by: Hunter Madison <hmadison@users.noreply.github.com>
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.
| Name | Description | Default | Required |
|---|---|---|---|
clusterName |
Teleport cluster name (must be an FQDN) | yes | |
authenticationType |
Type of authentication to use (local, github, ...) |
local |
no |
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 |
Guides
See https://goteleport.com/docs/kubernetes-access/helm/guides/ for guides on setting up HA Teleport clusters in EKS or GKE, plus a more comprehensive chart reference.
Contributing to the chart
Please read CONTRIBUTING.md before raising a pull request to this chart.