Use kubectl port-forward instead of SSH tunnel

The set-ssh-tunnel.sh script uses SSH for setting port forwards that could just as well be handled by Kubernetes. Handling them through Kubernetes could be easier, or could maybe solve compatibility problems we've had on Windows?

On the other hand you need kubectl access instead of SSH access to use it. So maybe it's not easier at all.