Post

Replies

Boosts

Views

Activity

Network tunneling through Telepresence not working on MacOs Sonoma
Did Apple make changes in tunneling or something, I used to point my local Java code to my Kubernetes pod in MacOs Ventura it used to work fine I used to run these commands in my terminal: export KUBECONFIG=/Users/tusharraina/Downloads/qa-kubeconfig telepresence --also-proxy 10.0.0.0/16 --deployment telepresence-perm --run env -i bash --norc now im getting this error: T: Using a Pod instead of a Deployment for the Telepresence proxy. If you experience problems, please file an issue! T: Set the environment variable TELEPRESENCE_USE_DEPLOYMENT to any non-empty value to force the old behavior, e.g., T: env TELEPRESENCE_USE_DEPLOYMENT=1 telepresence --run curl hello T: How Telepresence uses sudo: https://www.telepresence.io/reference/install#dependencies T: Invoking sudo. Please enter your sudo password. Password: T: Starting proxy with method 'vpn-tcp', which has the following limitations: All processes are affected, only one telepresence can run per machine, and you can't use other VPNs. You may need to add cloud hosts and headless services with --also-proxy. T: For a full list of method limitations see https://telepresence.io/reference/methods.html T: Volumes are rooted at $TELEPRESENCE_ROOT. See https://telepresence.io/howto/volumes.html for details. T: Starting network proxy to cluster using the existing proxy Deployment telepresence-perm T: No traffic is being forwarded from the remote Deployment to your local machine. You can use the --expose option to specify which ports you want to forward. T: Connected. Flushing DNS cache. T: Setup complete. Launching your command. T: Your process exited with return code -9. T: Exit cleanup in progress
0
1
506
Oct ’23