tsh kube ls -R fails to list any Kube Clusters if there are issues with any associated teleport cluster

[arsenetar]

Expected behavior: tsh kube ls -R returns the list of all Kubernetes clusters for any of the functional associated leaf teleport clusters.

Current behavior: If any teleport leaf cluster has issues (offline) then the command fails and does not provide any output aside from the error such as: ERROR: connection error: desc = "transport: authentication handshake failed: EOF". The error does not indicate which cluster it came from.

Bug details:

• Teleport version 14.3.4
• Recreation steps
  1. Connect to a teleport proxy that has multiple associated teleport leaf clusters
  2. Make one of the leaf clusters offline or in a non-functional state
  3. Run tsh kube ls -R
  4. Observe no output aside from error
• Debug logs

[zmb3]

Which version are you actually running? 1.14.3 seems like a typo..

[arsenetar]

Yeah it was, fixed in issue.

[jorpilo]

Seeing the same issue, if one of the clusters errors the command will just not output anything. Also it checks cluster by cluster sequentially which is very slow...