Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Backport #10620 to branch/v9 #11542

Merged
merged 5 commits into from
Mar 30, 2022
Merged

Conversation

ptgott
Copy link
Contributor

@ptgott ptgott commented Mar 29, 2022

Backport #10620 to branch/v9

ptgott added 5 commits March 30, 2022 16:40
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
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.
@ptgott ptgott force-pushed the auto-backport/10620-to-branch/v9 branch from f882df0 to 5f306bf Compare March 30, 2022 20:40
@ptgott ptgott enabled auto-merge (squash) March 30, 2022 20:40
@ptgott ptgott merged commit 85c5fc6 into branch/v9 Mar 30, 2022
@ptgott ptgott deleted the auto-backport/10620-to-branch/v9 branch March 30, 2022 20:46
@webvictim webvictim mentioned this pull request Apr 19, 2022
@webvictim webvictim mentioned this pull request Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants