Interesting, I will definitely try this out. If the Kubernetes ingress integration works well and it's stable, this could be really awesome. I'm a bit curious

Interesting, I will definitely try this out. If the Kubernetes ingress integration works well and it's stable, this could be really awesome. I'm a bit curious about the choice of websockets as a protocol over the tunnel, though. Why is "tunnelling plain (non-HTTP) traffic over TCP" a non-goal? What's the benefit over just tunneling the HTTP traffic over a reverse SSH tunnel or similar? EDIT: Maybe it's just a question of the author finding websockets "good enough" (despite performance overhead) and wanting to keep the scope small with a single implementation that isn't really going anywhere. Here a suggestion on using WebRTC instead of Websockets: https://github.com/alexellis/inlets/issues/49 https://github.com/alexellis/inlets/issues/49 > Thanks for the suggestion. I'll look into webrtc when I get time, but for the time-being I think web sockets are going to be the way inlets works.