Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
A proxy subcommand for exposing dev env processes as Skupper network services #11
(or developer-proxy, or proxy, or "portal", ...)
skupper local-proxy <secret> <service-name>:<service-port>:<local-port>...
In my developer environment (not in a cluster):
$ skupper local-proxy ~/secret.yaml hw-backend:8080:8081
Cool. I didn't know about kc port-forward.
So, in the case you're talking about, Skupper would take a locally running process, proxy it, and represent it as a service inside the cluster, right? Trying this out again:
skupper local-process-as-service <secret> <service-name> <local-port>:<remote-port>
# I have hw-frontend running in my cluster
A the moment this can be obtained through a number of manual steps. Suppose we have a simple echo service running locally on our machine on port 2000:
ncat -l 2000 --keep-open --exec "/bin/cat"
and we want to use that in our remote k8s cluster to which we are currently logged in with
the host can be obtained by:
after that, from a pod within the k8s cluster, should be possible to connecto to the echo server like: