telepresence icon indicating copy to clipboard operation
telepresence copied to clipboard

telepresence intercept timed out [v2.17]

Open aleboulanger opened this issue 11 months ago • 3 comments

Describe the bug Unable to intercept traffic from macOS with telepresence 2.17

telepresence_logs.zip

To Reproduce I followed the steps from the website

  • telepresence helm install
  • telepresence connect
  • curl -ik https://kubernetes.default
  • telepresence list
  • kubectl get service data-processing-pipeline-launcher --output yaml
  • telepresence intercept data-processing-pipeline-launcher --port 8080:8080 --env-file ~/data-processing-pipeline-launcher-intercept.env

Expected behavior intercept the calls from the service

Versions (please complete the following information):

  • Output of telepresence version OSS Client : v2.17.0 OSS Root Daemon : v2.17.0 OSS User Daemon : v2.17.0 OSS Traffic Manager: v2.17.0
  • Operating system of workstation running telepresence commands MACOS 14.3.1
  • Kubernetes environment and Version [e.g. Minikube, bare metal, Google Kubernetes Engine]
  • VMWARE with Kubernetes 1.26.14

VPN-related bugs:

Additional context Add any other context about the problem here.

aleboulanger avatar Mar 14 '24 14:03 aleboulanger

Looking at the cli.log, I think it could be this problem (sshfs need to be installed for volume mounts ). Could you try following these instructions in the docs?

cindymullins-dw avatar Mar 18 '24 19:03 cindymullins-dw

You can probably disregard the advice on volume mounts. Instead, to follow up on this, the first thing to try would be to [increase the timeout], to allow more time for the agent to arrive.

cindymullins-dw avatar May 20 '24 16:05 cindymullins-dw

@aleboulanger, curious if you've tried increasing the timeout? We do think that would help.

cindymullins-dw avatar Jun 03 '24 18:06 cindymullins-dw

Closing due to lack of response.

thallgren avatar Jul 23 '24 12:07 thallgren