Teleport Lab

The purpose of this repository is to provide the user with short lived Teleport deployment archetypes to test out various Teleport features.

This is achieved by utilizing libvirt/qemu together with Terraform to stand-up virtual machines, and ansible to provision them.

Ansible roles contained here could (potentially) be used like lego pieces if you are to create your own Teleport deployment playbook. For reference, see this readme and playbooks starting with main_*

Teleport deployments created with this repository are not meant for production use.

Prerequisites

• You know what Teleport is, and its many different ways of being deployed.
• Some terraform knowledge is required
• Some ansible knowledge is required
• General Linux system administrator knowledge

Requirements

• Teleport Enterprise, and license.pem in the root of this git repository
• Host must have libvirt and one of its virtualization drivers available, like KVM on Linux or hvf on MacOS
• Host must have teleport installed for tsh / tctl use on your workstation
• DNS and SSL
  • If this is a public lab (accessible from the internet)
    • Use the acme config in your teleport.yaml
    • Be on a public DNS that resolves to your public IP which has port 443 port-forwarded to 192.168.0.160 (assuming home lab behind an internet-facing router)
  • If this is a private lab (not accessible from the internet)
    • Use one of the lego supported DNS providers. CloudFlare example is in inventory/hosts.yml
      • DNS one of:
        • Privately hosted so it intercepts/rewrites *.yourdomain.com to 192.168.0.160
        • Publicly hosted where it resolves *.yourdomain.com and yourdomain.com to 192.168.0.160
        • Hosts file manipulation, but I don't like this approach
• Bridged network on the host with the bridge interface under the name br0
• Lots of RAM to facilitate virtual machines TODO: how much ram?

Usage instructions

One time setup

Download a Cloud image

First, check which distribution/versions are supported here

Then download a QEMU/UEFI cloud image. For example Ubuntu Focal (22.04 LTS) can be found as focal-server-cloudimg-amd64.img here

Generate an SSH key for Ansible

ssh-keygen -f ~/.ssh/teleport_lab -t rsa -b 4096

Sync the python (ansible) dependencies

pipenv sync

Set up Ansible variables

mkdir -p group_vars/all
touch group_vars/all/main.yml

Edit the group_vars/all/main.yml file. You can find the vars that should be overridden in the inventory/hosts.yml file.

Run the acme-lego playbook (once)

Skip this part if your Teleport environment will be reachable from the internet, and set up acme in your teleport.yaml.

This playbook will make the letsencrypt cert available on the workstation host. Reason behind having the cert on the host is that quick iteration of the guest virtual machines doesn't exhaust the letsencrypt rate limits which are pretty harsh.

Note: You will get a prompt BECOME password:. This is prompting you for your sudo password.

If your workstation sudo is passwordless

pipenv run ansible-playbook local_acme_cert.yml -vv

If your workstation sudo requires password

pipenv run ansible-playbook local_acme_cert.yml -vv --ask-become-pass

NOTE: Because this playbook stores your certs locally, you won't need to run it again unless you start using a different domain or token. Renewals are handled in the main playbook.

Iterate using Teleport deployment archetypes

This repo will provide some "archetypal" deployments. They can also be used as starting points so you can create your own. See playbooks starting with main_*.

Here are some of the archetypes:

Simple

Teleport cluster on a single VM and two SSH nodes

This provisions teleport and should be mostly idempotent to run

pipenv run ansible-playbook main_simple.yml -vv

This destroys the environment

pipenv run ansible-playbook main_simple.yml -vv -e terraform_destroy=true

Kubernetes dynamic

• Teleport cluster on a single VM,
• k3s VM:
  • The Teleport agent is not deployed onto the k3s cluster
  • The Teleport agent resides in parallel with the k3s cluster on the same VM
  • Joined to the Teleport cluster with type "kube"
• Follows (loosely) this teleport document: Dynamic Kubernetes Cluster Registration - TODO: make the playbook match the document closer

This provisions teleport and should be mostly idempotent to run

pipenv run ansible-playbook main_kubernetes_dynamic.yml -vv

This destroys the environment

pipenv run ansible-playbook main_kubernetes_dynamic.yml -vv -e terraform_destroy=true