You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After following the README instructions on my MacBook Pro (14-inch, 2021) with an M1 Pro chip, targeting a minikube cluster running locally with defaults configured, sshuttle is able to connect to the python containing pod (c : Connected to server.), but when trying to resolve host "echo-echo-server" (helm install echo ealenn/echo-server), I get curl: (6) Could not resolve host: echo-echo-server, and attempts to browse the public internet also fail. I suspect this issue may be related to this old telepresence issue affecting using sshuttle with minikube k8s clusters.
Issue Summary
After following the README instructions on my MacBook Pro (14-inch, 2021) with an M1 Pro chip, targeting a minikube cluster running locally with defaults configured, sshuttle is able to connect to the python containing pod (
c : Connected to server.
), but when trying to resolve host "echo-echo-server" (helm install echo ealenn/echo-server
), I getcurl: (6) Could not resolve host: echo-echo-server
, and attempts to browse the public internet also fail. I suspect this issue may be related to this old telepresence issue affecting using sshuttle with minikube k8s clusters.Commands run for reference
sshuttle
installbrew install sshuttle sshuttle --version # 1.1.1
echo server install
helm repo add ealenn https://ealenn.github.io/charts helm repo update helm install echo ealenn/echo-server
jumpbox
(kuttle pod) runkubectl run jumpbox --image=alpine:latest --restart=Never -- sh -c 'apk add python3 --update && exec tail -f /dev/null'
in-cluster test with curl
run
curl-client
podkubectl run curl-client --restart=Never --image=alpine:latest -- sh -c 'apk add curl --update && tail -f /dev/null'
exec test
curl
commandsshuttle
commandsshuttle --dns -r jumpboxx -e kuttle 0.0.0.0/0 # output: c : Connected to server.
NOTE: I also tried
-N
instead of0.0.0.0/0
to the same effectlocal
curl
testalso note that attempts to visit e.g. google.com in a local web browser failed
The text was updated successfully, but these errors were encountered: