self-hosted/teleport
self-hosted/teleport
1
0
Fork 0
mirror of https://github.com/gravitational/teleport synced 2024-10-20 01:03:40 +00:00
Code Issues Packages Projects Releases Wiki Activity
teleport/vagrant
History
Ryan Clark 806a568ada
Introduce config v3, add auth_server and proxy_server, remove auth_addresses (#15761)
2022-09-28 15:30:15 +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 Use tighter permissions for /var/lib/teleport everywhere 2020-05-15 16:45:56 +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