sshportal VS rospo

sshportal (https://github.com/moul/sshportal) is in my mind, a ssh gateway. It's a little cumbersome to setup but it accomplishes routing ssh the way we'll want within a kubernetes cluster with replication.

Or use a jump host as an intermediary. Or use https://github.com/moul/sshportal

Adding this as a possible tool to use in a jump host scenario: https://github.com/moul/sshportal

I use SSHPortal as a jump server, mostly for the fact that I can have one entrypoint/key into my servers without needing to remember hostnames or IP addresses. It also allows me to federate access for others who need it either on a temporary or more permanent basis. For cloud hosts where external firewalls (not on the machine) are present, we can lock SSH down to only the jump host.

Just leave it here sshportal

Check out sshportal, it's a tool to multiplex access to lots of other little SSH servers (which could be running in containers on your machine): https://github.com/moul/sshportal This is commonly called a 'bastion host' if you're googling around for more related stuff. There's a lot of other interesting SSH-related stuff in this list too: https://github.com/moul/awesome-ssh

This, and if you want stable tunnels may I suggest my own tool? https://github.com/ferama/rospo I use it every day to tunnel rdp connections that are behind NAT. Is a setup and forget, it always keep the connection up

The build script is very very simple (https://github.com/ferama/rospo/blob/main/build.sh). Maybe you could contribute with a pull request with the architectures that you need?

Released this one https://github.com/ferama/rospo