mirror of
https://github.com/gravitational/teleport.git
synced 2026-11-01 21:52:02 +08:00
Actual LimitNOFILE varies greatly between the systems as it depends on the systemd version and the go version used to build Teleport. The goal of this commit is to run Teleport in the same setup, regardless of the distro nor Teleport version. New systemd defaults are 1024:524288, and starting with go 1.19, go process can increase their soft limit up to the hard limmit dynamically. Old systemd versions don't suppoprt `soft:hard` notation and old go versions don't automatically increase up to the hard limit. For this reasons, the most compatible setting is to set softlimit=hardlimit=524288.
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