Zac Bergquist

https://github.com/gravitational/teleport/actions/runs/7115810275/job/19372821232

This is an issue again. Fresh hits on master: - https://github.com/gravitational/teleport/actions/runs/7628286356/job/20778980336?pr=36861 - https://github.com/gravitational/teleport/actions/runs/7628726029/job/20780483486 ``` === Failed === FAIL: integration TestIntegrations/Discovery (47.02s) trustedclusters.go:148: Error Trace: /__w/teleport/teleport/integration/helpers/trustedclusters.go:159 /opt/go/src/runtime/asm_amd64.s:1650 Error: Received unexpected error:...

Another on master, which is preventing us from getting an important build fix out. https://github.com/gravitational/teleport/actions/runs/7718393459/job/21039553375?pr=37568

grazie mille @espadolini 🙏

I wouldn't put this in the change log since docs go live immediately after merging the PR, they aren't "shipped" with the release.

@ibeckermayer can you backport this to branch/v15?

Closing due to inactivity.

Personally, I would just stick with the label approach. `tsh ssh user@alt=node2` will get you to the right node. Allowing a node to have multiple names has large implications (certificate...

@rcoxns re: > But it doesn't look like you can use the predicate language functions on the command line (or at least I couldn't figure out the syntax for it)....

> Ideally I think something like tsh ssh contains("node2") or the like. As of #40166, you can do exactly this. `contains(split(labels[alt_names], ","), "node2")`