Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Add a local Getting Started guide for Kubernetes
Backports #10620 * Add a local Getting Started guide for Kubernetes Our current Getting Started guides for Teleport on Kubernetes assume that readers are deploying resources to the cloud. Some users may want to get started quickly without, say, asking another team for permission to deploy a DNS zone. These users can then read our cloud-focused guides when it comes time to develop a proof of concept or use Teleport in production. Hopefully, this guide will expand the range of security-minded engineers who can get early firsthand experience with Teleport. This guide sets up Teleport on minikube and uses the App Service to access Kubernetes Dashboard. Because Kubernetes Dashboard is not initially accessible outside the cluster, this guide shows you how you can access it securely via Teleport without using `kubectl proxy`. We can also consider expanding this guide later on to introduce the Teleport Kubernetes Service or more sophisticated RBAC rules. Also worth noting that while this change adds a new tile to /docs/pages/kubernetes-access/getting-started.mdx, it does not add a new tile image. We can consider creating a new one or using the current one. Fixes #9359 * Respond to PR feedback I've made it more explicit that the minikube Docker driver is required for the demo. I have also added a row to the required software table that includes Docker Desktop/Docker Engine. I've tested this on my Linux desktop, and modified commands to support Docker Engine as well as Docker Desktop (i.e., "minikube tunnel" exposes a private IP address beside 127.0.0.1 for the load balancer). Also made a couple of minor tweaks, and removed the mention of localhost in relation to the Web UI. * Add Details for troubleshooting minikube tunnel * Ignore the dead link checker for a localhost link
- Loading branch information