Teleport: tsh --proxy=proxhost --cluster=clustername ssh clusternode no longer works as documented.

Created on 15 Oct 2018  路  4Comments  路  Source: gravitational/teleport

What happened:
$ tsh --cluster=od-server-00296 ssh od-server-00296 error: unknown long flag '--cluster'

What you expected to happen:
$ tsh --cluster=od-server-00296 ssh od-server-00296 od-server-00296$
As documented at: https://gravitational.com/teleport/docs/admin-guide/#trusted-clusters

Environment:

Most helpful comment

Can confirm, moving --cluster to after ssh works as expected. This ticket should probably be changed to a documentation bug then to update the linked section in the admin-guide to reflect this change

All 4 comments

I think we switched --cluster to be ssh specific flag, not a global one anymore, does tsh ssh --cluster work?

Can confirm, moving --cluster to after ssh works as expected. This ticket should probably be changed to a documentation bug then to update the linked section in the admin-guide to reflect this change

Looks like the usage of it is very strict and it is looking for it in a particular location:

$ tsh version
Teleport v3.2.4 git:v3.2.4-0-g339827c6 go1.11.5
tsh ls --cluster=teleport.example.com

tsh ssh --cluster=teleport.example.com root@teleport-5b6575c6c8-zplv5
Was this page helpful?
0 / 5 - 0 ratings