If it worked as desire, then at that point, running ssh -p 22 localhost on the Mac would have given me a connection to the NUC’s SSH service. The simplest experiment I could think of was to forward SSH from my Intel NUC to my Apple MacBook Air M1 which didn’t have SSH running on it. Local forwarding brings a remote service back to localhost for accessing Trying it out before responding The developer that contacted me wanted to “bring back” a remote service to his local computer without exposing it on the internet.

Remote forwarding pushes a local endpoint to a remote host for access on another network inlets Pro customers tell me that they do this quite often for hybrid cloud use-cases and for continuous deployment to edge locations. The difference between inlets and Ngrok or Argo tunnels, is that inlets can forward a service and also keep it private on the remote network by binding it to loopback, or a non-public adapter.

A port is forwarded to a remote cluster for access via its network. This kind of forwarding is called remote port forwarding and is the use-case we’re used to seeing with Ngrok.

The traditional use-case for inlets Pro has always been exposing or tunneling a service from a private cluster to a public cluster. I asked why he wasn’t using kubectl port-forward and the answer surprised me. My understanding was that getting access to the message queue from his laptop meant that he could watch things happening “live” and fix a bug that was blocking his progress at work. The answer was yes inlets Pro could do that, but we hadn’t documented it very well yet. Learn how one user cleared his headache and got reliable local port-forwarding for Kubernetes IntroductionĪ developer working on an API for the UK Government reached out to me and asked if he could use inlets to access a NATS message queue from within a Google Kubernetes Engine (GKE) cluster on his laptop.

Port forwarding automatic