What you’ll implement
The notes mirror the lesson flow so you can scan, copy, and revisit the important decisions quickly.
Getting Hands On
Time to get our hands on the keyboard and actually deploy our first Teleport cluster. By the end of this video, you will have a working Teleport cluster running on Kubernetes with TLS certificates and an admin user ready to log in.
Prerequisites
You’ll need Kind (Kubernetes in Docker), Helm, and kubectl. No cloud account required — everything runs locally. The only dependency is cert-manager, which is just one helm install away.
Deployment Steps
We walk through the demo scripts step by step:
- Check prerequisites — Verify Kind, Helm, and kubectl are installed
- Create a Kind cluster — A simple single control-plane configuration
- Deploy cert-manager — Add the Jetstack Helm repository, install cert-manager with CRDs, create a self-signed issuer and root certificate
- Configure Teleport values — Standalone chart mode, Multiplex proxy listener, and cert-manager integration
- Helm install — Use
envsubstfor values templating, thenhelm upgrade --install
Production Comparison
We also take a look at a real production deployment running on rawkode.cloud using Flux CD, with ACME-managed TLS certificates, Mayastor storage, and Gateway API via Cilium. The production setup isn’t that dissimilar from the local Kind deployment — just a few tweaks for your specific infrastructure.