mirror of
https://github.com/gravitational/teleport
synced 2024-10-21 01:34:01 +00:00
03064cfa96
The prefix fetching logic has a bug: it treats everything starting with `/teleport` as the legacy prefix data, even if it's `/teleport-foo/bar`. This is an issue if user specifies `/teleport-foo` as their custom prefix. Each restart will copy the data from `/teleport-foo/...` to `/teleport-foo-foo/...`. Set the legacy prefix const to `/teleport/` instead. This avoids excessive copying during startup. Prefixes can still be confused later on, with `Watch` and `GetRange`, but this is harder to migrate with backwards-compatibility. |
||
|---|---|---|
| .. | ||
| aws | ||
| chart | ||
| etcd | ||
| gke-auth | ||
| go-client | ||
| k8s-auth | ||
| launchd | ||
| local-cluster | ||
| resources | ||
| systemd | ||
| upstart | ||
| README.md | ||
Examples
Configuration Examples
- local-cluster : Sample configuration of a 3-node Teleport cluster using just a single machine
Daemon Configuration
AWS examples
- AWS: CloudFormation : CloudFormation templates as an example of how to setup HA Teleport in AWS using our AMIs.
- AWS: Terraform : Terraform specifies example provisioning script for Teleport auth, proxy and nodes in HA mode.
- AWS: EKS. External Link
Kubernetes - Helm Charts
- Helm Chart - Teleport Enterprise : For deploying into Kubernetes using Helm
- Helm Chart - Teleport Demo : An internal demo app showing Teleport components deployed into Kubernetes using Helm Charts.
SSO Connector Examples and Trusted Cluster Examples
SSO Resources
- Active Directory - YAML Resource
- OIDC Connector, like "keycloak". - YAML Resource
- SAML Connector, like "Okta". - YAML Resource