Update OpenSSH docs with agentless information#23359
Conversation
e143eaf to
ea38583
Compare
| We've outlined these reasons in [OpenSSH vs Teleport SSH for Servers?](https://goteleport.com/blog/openssh-vs-teleport/) | ||
| `teleport` SSH servers have support for multiple features that are incompatible with OpenSSH: | ||
|
|
||
| - [Dynamically updating node labels from the output of configured commands](../../management/admin/labels.mdx) |
There was a problem hiding this comment.
Labels are Teleport specific, so I'm not sure why this would be meaningful to an OpenSSH user. Is the expectation here that OpenSSH users would understand what Teleport labels are?
There was a problem hiding this comment.
My thoughts were having an explicit list of what is and isn't supported with agentless nodes would be useful to set user's expectations, what do you think, is that not necessary?
|
@capnspacehook Can you address remaining feedback here so we can re-review and get this merged? |
6ffab62 to
21b4a55
Compare
ptgott
left a comment
There was a problem hiding this comment.
Approved so you're not blocked. Added suggestions that I would recommend incorporating.
Going forward, agentless nodes are the preferred way to manage OpenSSH nodes, so update the documentation to describe how to add them to a cluster.
21b4a55 to
2f902af
Compare
|
I came across this PR while backporting updates that include this content, specifically this |
|
Only v13. |
Going forward, agentless nodes are the preferred way to manage OpenSSH nodes, so update the documentation to describe how to add them to a cluster.
SSH agents are not required to connect to agentless nodes, so remove them from this guide so users don't they they still need them.
Supporting RFD: https://github.com/gravitational/teleport/blob/master/rfd/0098-registered-openssh-nodes.md
Updates #21408.