-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Improve the Kubernetes RBAC partial #38705
Conversation
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
🤖 Vercel preview here: https://docs-cgvz5bn9w-goteleport.vercel.app/docs/ver/preview |
The PR changelog entry failed validation: Changelog entry not found in the PR body. Please add a "no-changelog" label to the PR, or changelog lines starting with |
bd95175
to
cb174d6
Compare
🤖 Vercel preview here: https://docs-exb4yh354-goteleport.vercel.app/docs/ver/preview |
cb174d6
to
ed7344b
Compare
🤖 Vercel preview here: https://docs-nokyt56hd-goteleport.vercel.app/docs/ver/preview |
Closes #18495 Edit the partial at `docs/pages/includes/kubernetes-access/rbac.mdx` so it does not require enabling access to an awkwardly named Kubernetes user based on the current context. Instead, have the user check whether they can already access Kubernetes users/groups, and if not, assign their Teleport user a role that can access a view-only group.
ed7344b
to
f288aa4
Compare
🤖 Vercel preview here: https://docs-fsef0wb0c-goteleport.vercel.app/docs/ver/preview |
Closes #18495
Edit the partial at
docs/pages/includes/kubernetes-access/rbac.mdx
so it does not require enabling access to an awkwardly named Kubernetes user based on the current context. Instead, have the user check whether they can already access Kubernetes users/groups, and if not, assign their Teleport user a role that can access a view-only group.