Files
teleport/examples/chart/index.html
T
Noah Stride ecb5d66c07 SPIFFE Daemon Set Helm Chart (#61424)
* Skeleton/README

* Update Makefile with new targets

* More makefile changes

* Add Chart.yaml

* Add _helpers.yaml

* Add supporting RBAC

* Add values file and tweak config

* Add ClusterRole/ClusterRoleBinding

* Fix docs on values

* Hack on daemonset definition

* templatize security contexts

* Fix up daemonset labels/matchers

* Add workload api listener to tbot config

* Fix bad service account name

* Support debug mode logs

* Add value for workloadIdentitySelector

* Update documentation

* Add snapshot testsAdd snapshot testsAdd snapshot testsAdd snapshot
testsAdd snapshot testsAdd snapshot testsAdd snapshot testsAdd snapshot
tests

* Add to the chart index

* Fix missing "?" in helm value

* Generate reference doucmentation

* Appease newline linting

* Add note regarding high level of privileges

* Update chart ref
2026-01-02 15:47:40 +00:00

99 lines
5.1 KiB
HTML

<html>
<head>
<title>Teleport Helm chart repo</title>
</head>
<body>
<h1>Teleport Helm chart repo</h1>
<h3>Add the repo</h3>
<pre>helm repo add teleport https://charts.releases.teleport.dev</pre>
<h3>Install a chart</h3>
<h4>See our <a href="https://goteleport.com/docs/reference/helm-reference/">Helm chart guides</a> for HA setups in EKS or GKE.</h4>
<pre><b><a href="https://github.com/gravitational/teleport/tree/master/examples/chart/teleport-cluster">teleport-cluster:</a></b>
# Install a single node Teleport cluster and provision a cert using ACME.
# Set clusterName to a unique hostname, for example teleport.example.com
# Set acmeEmail to receive correspondence from Letsencrypt certificate authority.
helm install ${RELEASE_NAME?} teleport/teleport-cluster \
--create-namespace \
--namespace ${NAMESPACE?} \
--set clusterName=${CLUSTER_NAME?} \
--set acme=true \
--set acmeEmail=${EMAIL?}</pre>
<br />
<pre><b><a href="https://github.com/gravitational/teleport/tree/master/examples/chart/teleport-kube-agent">teleport-kube-agent:</a></b>
# Install or upgrade the Teleport kube agent which can be used to provide remote access to
# a remote Kubernetes cluster. Can also be used to run Teleport database or app service agents.
# Click the link above to see the README.
helm install ${RELEASE_NAME?} teleport/teleport-kube-agent \
--create-namespace \
--namespace ${NAMESPACE?} \
--set roles="kube\,app\,discovery" \
--set proxyAddr=${PROXY_ENDPOINT?} \
--set authToken=${JOIN_TOKEN?} \
--set kubeClusterName=${KUBERNETES_CLUSTER_NAME?}</pre>
<pre><b><a href="https://github.com/gravitational/teleport/tree/master/examples/chart/teleport-cluster/charts/teleport-operator">teleport-operator:</a></b>
# Install the Teleport Kubernetes Operator to manage Teleport resources from Kubernetes.
# The operator can run against any remote Teleport cluster and reconcile its resources.
# Click the link above to see the README.
helm install ${RELEASE_NAME?} teleport/teleport-operator \
--create-namespace \
--namespace ${NAMESPACE?} \
--set authAddr="${TELEPORT_ADDR?}" \
--set token="${JOIN_TOKEN?}"</pre>
<br />
<pre><b><a href="https://github.com/gravitational/teleport/tree/master/examples/chart/access/slack">teleport-plugin-slack:</a></b>
# Install the Teleport Slack Plugin to send Slack notifications on Access Requests.
# Click the link above to see the README.
helm install ${RELEASE_NAME?} teleport/teleport-plugin-slack \
--create-namespace \
--namespace ${NAMESPACE?} \
--set teleport.address="${TELEPORT_ADDR?}" \
--set teleport.identitySecretName="${ID_SECRET}" \
--set roleToRecipients.\*[0]=admin-channel \
--set slack.token="${SLACK_TOKEN}"</pre>
<br />
<pre><b><a href="https://github.com/gravitational/teleport/tree/master/examples/chart/access/datadog">teleport-plugin-datadog:</a></b>
# Install the Teleport Datadog Incident Management Plugin to create Datadog incidents on Access Requests.
# Click the link above to see the README.
helm install ${RELEASE_NAME?} teleport/teleport-plugin-datadog \
--create-namespace \
--namespace ${NAMESPACE?} \
--set teleport.address="${TELEPORT_ADDR?}" \
--set teleport.identitySecretName="${ID_SECRET}" \
--set datadog.apiEndpoint="https://api.datadoghq.com" \
--set datadog.apiKey="${DATADOG_API_KEY}" \
--set datadog.applicationKey="${DATADOG_APPLICATION_KEY}" \
--set datadog.fallbackRecipient="${EMAIL?}"</pre>
<br />
<pre><b><a href="https://github.com/gravitational/teleport/tree/master/examples/chart/tbot">tbot:</a></b>
# Install the TBot chart to automatically configure a tbot agent to
# generate short-lived credentials for consumption by clients.
# Click the link above to see the README.
helm install ${RELEASE_NAME?} teleport/tbot \
--create-namespace \
--namespace ${NAMESPACE?} \
--set teleportProxyAddress="${TELEPORT_ADDR?}" \
--set token="${TELEPORT_TOKEN?}"</pre>
<br />
<pre><b><a href="https://github.com/gravitational/teleport/tree/master/examples/chart/tbot-spiffe-daemon-set">tbot-spiffe-daemon-set:</a></b>
# Install the tbot-spiffe-daemon-set chart to deploy tbot into your Kubernetes cluster and configure it for issuing SPIFFE SVIDs to other Kubernetes workloads.
# Click the link above to see the README.
helm install ${RELEASE_NAME?} teleport/tbot-spiffe-daemon-set \
--create-namespace \
--namespace ${NAMESPACE?} \
--set teleportProxyAddress="${TELEPORT_ADDR?}" \
--set clusterName="${CLUSTER_NAME?}" \
--set workloadIdentitySelector.name="${WORKLOAD_IDENTITY_NAME?}" \
--set token="${TELEPORT_TOKEN?}"</pre>
<br />
<h3>Changelog</h3>
<pre>See the <a href="https://goteleport.com/docs/changelog/">Teleport Changelog</a> for a list of important changes between Helm chart versions.</pre>
</body>
</html>