You need the port forward maybe because that services are not meant to be exposed through the internet or for whatever reason. Persistent SSH takes the complexity out of the process as it is already compiled and ready to monitor your tunnels and automatically reconnect them if needed. Many times during development on k8s you need to port-forward some of the pods services for local development and/or tests. While using Windows, the standard option for keeping SSH tunnels operable includes installing Linux tools (starting from SSH itself, Putty, Cygwin, autossh, etc.) and street magic with scripts. Example scenario: kubernetes service exporter Rospo tunnel are monitored and keeped up in the event of network issues. Rospo will generate server identity file on first run and uses standard authorized_keys and user known_hosts files. Add your public key to your list of authorized keys on the server. Tunnels are fully secured using standard ssh mechanisms. Copy your newly-created public key to the SSH server. open a socket on the remote machine listening on port 5000 that forwards all the traffic from remote machine to a local service (on the local machine) listening on port 5000īut these are just an examples.

open a socket on the local machine listening on port 9999 that forwards all the traffic to the service listening on port 9999 on the remote_server_address machine.open a socket on the local machine listening on port 8000 that forwards all the traffic to the service listening on port 8000 on the remote_server_address machine.What's happens here is that rospo will connect to remote_server_address through the jumphost_address server and will:

Persistent ssh tunnel windows