In the Teleport web gui, when listing kubernetes clusters, the CONNECT button brings up a model that lists instructions that can be copy/pasted to generate a kubeconfig to connect to that particular config.
These instructions are incorrect if the currently logged-in user is an SSO user. It should include the corresponding --auth connector for the currently logged in user when wherever possible.
What problem does this solve?
It will reduce confusion for end-users who are less familiar with teleport and want to get started quickly to access their kubernetes cluster.
What would you like Teleport to do?
In the Teleport web gui, when listing kubernetes clusters, the CONNECT button brings up a model that lists instructions that can be copy/pasted to generate a kubeconfig to connect to that particular config.
These instructions are incorrect if the currently logged-in user is an SSO user. It should include the corresponding
--auth connector
for the currently logged in user when wherever possible.What problem does this solve?
It will reduce confusion for end-users who are less familiar with teleport and want to get started quickly to access their kubernetes cluster.
If a workaround exists, please include it.
no
gz#5547