self-hosted/teleport
self-hosted/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport synced 2024-10-19 16:53:57 +00:00
Code Issues Packages Projects Releases Wiki Activity
teleport/vagrant
History
Hugo Shaka 0d6adaa50a
Standardize systemd LimitNOFILE (#17893) 
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.
2022-10-31 16:56:02 +00:00
..
opt Introduce config v3, add auth_server and proxy_server, remove auth_addresses (#15761) 2022-09-28 15:30:15 +00:00
.gitignore Zero-config Vagrant environment with trusted clusters 2016-06-21 12:09:55 -07:00
docker.service User Manual 2016-03-18 12:56:59 -07:00
docker.socket User Manual 2016-03-18 12:56:59 -07:00
README.md Drop prerequisite from readme 2020-05-29 10:43:52 -04:00
teleport.service Standardize systemd LimitNOFILE (#17893) 2022-10-31 16:56:02 +00:00
Vagrantfile vagrant: Remove reference to non-existing VM in deprecated S3 bucket (#16383) 2022-09-13 15:35:38 -07:00

README.md

Vagrant

This directory contains scripts to create multiple Vagrant machines for experimenting with Teleport on multiple nodes.

There are two nearly identical Vagrantfiles: one for Virtualbox and another for KVM/Libvirt, they both share base.rb

Default Configuration

data/var contains pre-created contents of guest's /var/lib/teleport data/opt contains pre-created contents of guest's /opt/teleport (configuration)

Three machines are created, grouped in two clusters, cluster_a and cluster_b:

  • a-auth: CA+node+proxy for "cluster_a"
  • a-node: Standalone node for "cluster_a"
  • b-auth: CA+node+proxy for "cluster_b"

A reverse tunnels from cluster_a to cluster_b is created. This allows users of cluster_b to login into any machine of cluster_a.

How to use

Easy:

~: vagrant up

Then you need to vagrant ssh into a-auth and b-auth and on both CAs you need to create 'vagrant' user:

~: tctl users add